WO2017163735A1 - コアノード、基地局、無線端末、通信方法、無線リソース割当方法、基地局選択方法、及び、可読媒体 - Google Patents
コアノード、基地局、無線端末、通信方法、無線リソース割当方法、基地局選択方法、及び、可読媒体 Download PDFInfo
- Publication number
- WO2017163735A1 WO2017163735A1 PCT/JP2017/006644 JP2017006644W WO2017163735A1 WO 2017163735 A1 WO2017163735 A1 WO 2017163735A1 JP 2017006644 W JP2017006644 W JP 2017006644W WO 2017163735 A1 WO2017163735 A1 WO 2017163735A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- radio
- service
- resource
- base station
- identification information
- Prior art date
Links
- 238000004891 communication Methods 0.000 title claims abstract description 87
- 238000000034 method Methods 0.000 title claims description 170
- 238000013468 resource allocation Methods 0.000 title claims description 27
- 238000010187 selection method Methods 0.000 title claims description 8
- 238000007726 management method Methods 0.000 claims description 34
- 230000008569 process Effects 0.000 description 44
- 230000001960 triggered effect Effects 0.000 description 20
- 230000005540 biological transmission Effects 0.000 description 18
- 238000010586 diagram Methods 0.000 description 12
- 230000004913 activation Effects 0.000 description 11
- 230000004044 response Effects 0.000 description 7
- 238000004590 computer program Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 238000006243 chemical reaction Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000003321 amplification Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000013144 data compression Methods 0.000 description 1
- 238000000354 decomposition reaction Methods 0.000 description 1
- 230000006837 decompression Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000003199 nucleic acid amplification method Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000011218 segmentation Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
- H04W16/02—Resource partitioning among network components, e.g. reuse partitioning
-
- 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
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
- H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/06—Registration at serving network Location Register, VLR or user mobility server
-
- 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/14—Interfaces between hierarchically different network devices between access point controllers and backbone network device
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/50—Allocation or scheduling criteria for wireless resources
- H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
- H04W72/543—Allocation or scheduling criteria for wireless resources based on quality criteria based on requested quality, e.g. QoS
Definitions
- the present disclosure relates to a core node, a base station, a radio terminal, a communication method, a radio resource allocation method, a base station selection method, and a program, and in particular, a core node, a base station, a radio terminal, a communication method, and a radio resource allocation that perform radio resource allocation.
- the present invention relates to a method, a base station selection method, and a program.
- IoT terminals Internet Of Things terminals
- IoT terminals Many terminals (hereinafter referred to as IoT terminals) that perform communication autonomously without requiring user operation are used for the IoT service. Accordingly, in order to provide an IoT service using many IoT terminals, it is desired to efficiently accommodate many IoT terminals in a network managed by a communication carrier or the like.
- Page 11 of Non-Patent Document 1 describes a method for managing radio resources allocated to terminals. Specifically, it is described that a radio resource group having a plurality of radio resources is divided into a plurality of RAN (Radio Access Network) Slice, and each RAN Slice is assigned to a specific service. That is, a radio resource possessed by a predetermined RAN Slice is allocated to a radio terminal used for a specific service. In this way, by assigning RAN Slice for each service, it is possible to prevent wireless resources from being assigned to other services when the number of wireless terminals used for a specific service increases.
- RAN Radio Access Network
- Non-Patent Document 1 describes that a radio resource group is divided into a plurality of RAN Slices for management, but does not describe how to allocate radio resources to radio terminals. . That is, a radio resource allocation method has not been established for a radio terminal used for a specific service.
- the radio resource allocation technique is a technique for allocating radio resources of RAN Slice allocated for a specific service to radio terminals. Therefore, there is a problem in that the radio resources of RAN Slice managed by division cannot be allocated to appropriate radio terminals.
- An object of the present disclosure is to provide a core node, a base station, a radio terminal, a communication method, a radio resource allocation method, and a radio node of RAN Slice allocated for each service, which can be appropriately allocated to a radio terminal using the service,
- a base station selection method and program are provided.
- the core node includes a determination unit that determines a radio resource to be allocated according to a service provided to a radio terminal, and a base that manages a plurality of radio resources for each RAN Slice associated with the service And a communication unit that transmits resource identification information indicating the radio resource determined by the determination unit to a station.
- the base station includes a management unit that manages a plurality of radio resources for each RAN Slice associated with the service, and a service provided from the core node to the radio terminal.
- a communication unit that receives resource identification information indicating a radio resource to be allocated, and a resource allocation unit that allocates the radio resource indicated by the resource identification information to the radio terminal.
- a wireless terminal includes a receiving unit that receives broadcast information transmitted by a plurality of base stations, and a RAN that provides a service used by the terminal among the plurality of base stations.
- a decision unit that decides to connect to a base station that has transmitted broadcast information including RANliceSlice identification information indicating Slice.
- a radio resource to be allocated is determined according to a service provided to the radio terminal, and a plurality of radio resources are managed for each RAN Slice associated with the service. Resource identification information indicating the determined radio resource is transmitted.
- the radio resource allocation method manages a plurality of radio resources for each RAN Slice associated with a service, and allocates the radio resource according to a service provided from a core node to a radio terminal Resource identification information indicating radio resources is received, and radio resources indicated by the resource identification information are allocated to the radio terminals.
- the base station selection method receives broadcast information transmitted by a plurality of base stations, and indicates a RAN Slice that provides a service to be used from among the plurality of base stations. It is determined to connect to a base station that has transmitted broadcast information including Slice identification information.
- a program determines a radio resource to be allocated according to a service provided to a radio terminal, and manages a plurality of radio resources for each RAN Slice associated with the service, This causes the computer to execute transmission of resource identification information indicating the determined radio resource.
- a core node, a base station, a radio terminal, a communication method, a radio resource allocation method, and a base station that can appropriately allocate radio resources of RAN Slice allocated for each service to radio terminals using the service A selection method and a program can be provided.
- FIG. 1 is a configuration diagram of a communication system according to a first exemplary embodiment
- FIG. 3 is a configuration diagram of a communication system according to a second exemplary embodiment.
- It is a block diagram of UE concerning Embodiment 2.
- FIG. It is a block diagram of the radio
- FIG. It is a figure which shows the flow of Attach
- FIG. It is a figure which shows the flow of Attach
- FIG. It is a figure which shows the flow of UE
- FIG. 6 is a configuration diagram of a communication system according to a fourth exemplary embodiment. It is a figure which shows the flow of Combined
- FIG. It is a figure which shows the flow of PDP
- FIG. It is a figure which shows the flow of PDP
- FIG. It is a figure which shows the flow of MS * Initiated * Service * Request * Procedure * using * GN / Gp concerning Embodiment 4.
- FIG. It is a figure which shows the flow of MS * Initiated * Service * Request * Procedure * using * GN / Gp concerning Embodiment 4.
- FIG. It is a figure which shows the flow of PDP
- FIG. It is a figure which shows the flow of MS * Initiated * Service * Request * Procedure * using * GN / Gp concerning Embodiment 5.
- FIG. It is a block diagram of the base station concerning each embodiment. It is a block diagram of the radio
- FIG. 1 includes a core node 10, a base station 20, and a wireless terminal 30.
- the core node 10, the base station 20, and the wireless terminal 30 may be a computer device that operates when a processor executes a program stored in a memory.
- the core node 10 may be MME (Mobility Management Entity) or SGSN (Serving General Packet Radio Service Support Node) defined as a node that performs session management and mobility management in 3GPP (3rd Generation Partnership Project).
- the base station 20 may be an eNodeB (evolved Node B) defined in 3GPP.
- the eNodeB is a base station that supports LTE (Long Term Term Evolution) as a wireless communication method.
- the base station 20 may be replaced with an RNC (Radio Network Controller) and Node B defined as a device for controlling the base station in 3GPP.
- RNC Radio Network Controller
- the wireless terminal 30 may be a mobile phone terminal, a smart phone terminal, a tablet terminal, or the like.
- the wireless terminal 30 may be an IoT terminal, an MTC (Machine Type Communication) terminal, an M2M (Machine type Machine) terminal, or the like.
- the core node 10 includes a communication unit 12 and a determination unit 14.
- the components constituting the core node 10 such as the communication unit 12 and the determination unit 14 may be software or modules that are processed by a processor executing a program stored in a memory. Or the component which comprises the core node 10 may be hardware, such as a circuit or a chip
- the communication unit 12 includes a transmission unit (Transmitter) and a reception unit (Receiver).
- the determination unit 14 determines a radio resource to be allocated to the wireless terminal 30 using service information indicating a service provided to the wireless terminal 30.
- the radio resource may be a resource managed by the base station 20, for example.
- the radio resource may be a resource determined using at least one of frequency and time.
- the service provided to the wireless terminal 30 may be, for example, a voice service that provides a voice call, a data service that transmits image data or text data, or a broadcast distribution service that distributes data all at once. Good.
- the service provided to the wireless terminal 30 may be an IoT service.
- the IoT service may be, for example, a service using a smart meter or an automatic driving service. Services shown as services provided to the wireless terminal 30 are not limited to the services described above, and various services may be provided to the wireless terminal 30.
- the service information is information that identifies a service provided to the wireless terminal 30.
- the communication unit 12 transmits resource identification information indicating the radio resource determined by the determination unit 14 to the base station 20 that manages a radio resource group having a plurality of radio resources by dividing the group into a plurality of RAN Slices.
- Each RAN Slice has some radio resources included in the radio resource group.
- Each RAN Slice has at least one radio resource.
- One radio resource may be a resource specified using a specific frequency band and a specific period, for example. In other words, the RAN Slice may have an area where a plurality of radio resources are combined.
- the RAN Slice may be paraphrased as having a part of the radio resource group among the radio resource groups managed by the base station 20.
- RAN Slice is associated with a service provided to the wireless terminal. That is, RAN Slice has at least one radio resource assigned to a radio terminal that uses a specific service.
- Resource identification information is information for identifying radio resources managed by the base station 20, and is information for identifying at least one radio resource.
- the communication unit 12 transmits resource identification information indicating the radio resource included in the RAN Slice associated with the service provided to the radio terminal 30 to the base station 20.
- the base station 20 includes a communication unit 22, a management unit 24, and a resource allocation unit 26.
- the components constituting the base station 20 such as the communication unit 22, the management unit 24, and the resource allocation unit 26 are software or modules that are processed by a processor executing a program stored in a memory. Also good. Or the component which comprises the base station 20 may be hardware, such as a circuit or a chip
- the communication unit 22 includes a transmission unit (Transmitter) and a reception unit (Receiver).
- the management unit 24 divides and manages a radio resource group having a plurality of radio resources into a plurality of RAN Slices.
- the communication unit 22 receives resource identification information indicating the radio resource to be allocated to the radio terminal 30 transmitted from the core node 10.
- the resource identification information indicates a radio resource included in the RAN Slice associated with the service provided to the radio terminal 30.
- the resource allocation unit 26 allocates the radio resource indicated by the resource identification information to the radio terminal 30.
- the core node 10 allocates radio resources to be allocated to the radio terminal 30 to the base station 20 that manages the radio resource group by dividing the radio resource group into a plurality of RAN Slices. Resource identification information can be transmitted. Thereby, the base station 20 can allocate the radio resource designated by the core node 10 to the radio terminal 30. The core node 10 can determine the radio resource to be allocated to the radio terminal 30 based on the service used by the radio terminal 30. Therefore, the base station 20 can appropriately allocate the radio resources possessed by the RAN Slice associated with the service used by the radio terminal 30 to the radio terminal 30.
- FIG. 2 is a communication system that supports LTE as a wireless communication system, and is a communication system defined as an Evolved Packet System (EPS) in 3GPP.
- EPS Evolved Packet System
- FIG. 2 is based on the figure of TS 23.401 V 13.5.0 Figure 4.2.1-1.
- the communication system of FIG. 2 includes 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 Rules) entity 47 (hereinafter referred to as PCRF 47), UTRAN 48, GERAN (GSM (registered trademark) (Global System Mobile for communications)) EDGE (Enhanced Data Data Rates for Global Evolution) Radio Access Network) 49 and Operator's IP Services50.
- PCRF 47 Policy and Charging Rules Rules Rules
- the UE40 is a term used as a generic term for wireless terminals in 3GPP.
- the UE may be replaced with, for example, an MS (Mobile Station).
- the E-UTRAN 41 is a RAN (Radio Access Network) that uses LTE as a radio access system.
- the UTRAN 48 is a RAN that uses a 3G wireless system as a wireless access system.
- GERAN 49 is a RAN that uses a 2G wireless system as a wireless access system.
- the MME 42 and the SGSN 44 are nodes that execute mobility management, session management, and the like regarding the UE 40.
- the HSS 43 is a node that manages subscriber information regarding the UE 40.
- the subscriber information includes information regarding services used by the UE 40.
- the SGW 45 and the PGW 46 are nodes that relay data transmitted between the UE 40 and the Operator's IP Services 50.
- Services 50 may be a server device or a server device group managed by a business provider that provides services to the UE 40, for example.
- the PCRF 47 is a node that manages policies, charging rules, and the like.
- LTE-Uu reference point is defined between UE40 and E-UTRAN41.
- An S1-MME reference point is defined between the E-UTRAN 41 and the MME 42.
- An S6 reference point is defined between the MME 42 and the HSS 43.
- An S3 reference point is defined between the MME 42 and the SGSN 44.
- An S1-U reference point is defined between the MME 42 and the SGW 45.
- An S11 reference point is defined between the MME 42 and the SGW 45.
- An S4 reference point is defined between the SGSN 44 and the SGW 45.
- An S12 reference point is defined between the SGW 45 and the UTRAN 48.
- An S5 / S8 reference point is defined between the SGW 45 and the PGW 46.
- a Gx reference point is defined between the PGW 46 and the PCRF 47.
- An SGi reference point is defined between the PGW 46 and the Operator's IP service 50.
- An Rx reference point is defined between the PCRF 47 and the Operator's IP Services 50.
- An S1-10 reference point is defined between the MME 42 and another MME.
- the UE 40 includes a communication unit 71, a RAN Slice availability determination unit 72, and a connection destination RANliceSlice selection unit 73.
- the component which comprises UE40 may be the software or module with which a process is performed when a processor runs the program stored in memory. Or the component which comprises UE40 may be hardware, such as a circuit or a chip
- the communication unit 71 performs radio communication using eNodeB and LTE included in the E-UTRAN 41. Further, the communication unit 71 receives broadcast information transmitted from the eNodeB. The communication unit 71 may receive broadcast information from a plurality of eNodeBs. The broadcast information is transmitted using, for example, BCCH (Broadcast Control Channel). The broadcast information includes at least one RAN Slice ID. The RAN Slice ID is information for identifying the RAN Slice managed by the eNodeB. Further, RAN Slice is a radio resource used for providing a specific service. That is, UE40 can recognize the service which eNodeB can provide by receiving alerting
- BCCH Broadcast Control Channel
- the RAN Slice availability determination unit 72 determines whether the RAN Slice output from the communication unit 71 includes a RAN Slice associated with the service used by the UE 40. Assume that the RAN Slice availability determination unit 72 holds in advance at least one RAN Slice ID indicating the RAN Slice associated with the service used by the UE 40. The RAN Slice availability determination unit 72 determines whether or not the RAN Slice ID held in advance is included in the RAN Slice ID output from the communication unit 71. The RAN Slice availability determination unit 72 outputs the RAN Slice ID that matches the RAN Slice ID held in advance from the RAN Slice ID output from the communication unit 71 to the connection destination RAN Slice selection unit 73.
- the connection destination RAN Slice selection unit 73 selects a RAN Slice to be used based on a predetermined policy. For example, the connection destination RAN Slice selection unit 73 may select the RAN Slice ID transmitted from the eNodeB having the highest radio field intensity. Alternatively, the connection destination RAN Slice selection unit 73 may determine a priority for each RAN Slice ID and select a RAN Slice ID having a high priority. The connection destination RAN Slice selection unit 73 outputs the selected RAN Slice ID to the communication unit 71. Alternatively, the connection destination RAN Slice selection unit 73 may select a RAN Slice ID relating to a specific service to be used preferentially. The specific service is, for example, an IoT service or an automatic driving service.
- the communication unit 71 executes a connection process with the eNodeB having the RAN Slice ID output from the connection destination RAN Slice selection unit 73.
- the eNodeB indicates that a radio resource group including a plurality of radio resources is managed. Further, FIG. 4 shows that the eNodeB manages the radio resource group by dividing it into RAN Slice #A and RAN Slice #B. Further, FIG. 4 shows that RAN Slice #A is composed of a plurality of radio resource groups assigned to a specific group.
- the specific group may be, for example, a group that uses a service associated with RAN Slice #A.
- the specific group may include a plurality of UEs that use the service associated with RAN Slice #A.
- RAN Slice #A may be RAN Slice for automatic driving.
- the specific group may be an automatic driving service provided by each company.
- the UE is assigned radio resources included in the radio resource group assigned to the group to which the UE belongs.
- the radio resource allocated to the UE is identified by, for example, Resource ID.
- the information management apparatus is an apparatus that is different from the HSS 43 and manages subscriber information.
- the HSS 43 and the information management device are shown as different devices, but the HSS 43 and the information management device may be the same device. In other words, the HSS 43 may have the function of an information management device.
- IMSI Internal Mobile Subscriber Identity
- RAN Slice ID is information indicating the RAN Slice associated with the service used by the UE 40.
- the ENodeB manages RAN Slice ID and Resource ID in association with each other.
- the RAN Slice ID is information for identifying the RAN Slice managed by the eNodeB.
- Resource ID is information for identifying a radio resource to be allocated to the UE 40.
- Resource ID is information uniquely identified in the eNodeB.
- One RAN Slice ID is associated with multiple Resource IDs. Further, when managing a plurality of RAN Slices, the eNodeB has a plurality of RAN Slice IDs.
- the HSS 43 manages the IMSI and the UE Usage ⁇ ⁇ ⁇ ⁇ type in association with each other.
- UE Usage type is information for identifying a service used by a UE identified by IMSI or a group to which the UE belongs.
- the HSS 43 manages IMSI and UE Usage type related to a plurality of UEs.
- the information management device manages the Service ID and the UE Usage type in association with each other.
- Service ID is information for identifying a service used by the UE and a group to which the UE belongs.
- the Service ID is information uniquely identified in the communication system.
- the information management apparatus manages Service ID and UE ID type for a plurality of UEs. When the HSS 43 and the information management device are the same device, the HSS 43 manages the IMSI, the UE ⁇ Usage type, and the Service ID in association with each other.
- the service used by the UE is specified using Service ID. Also, the Service ID is specified by using UE Usage Type.
- the Service ID may be specified using subscriber information other than the UE ID type.
- MME 42 manages Service ID and Resource ID in association with each other. In other words, the MME 42 can identify the Resource ID assigned to the UE in the eNodeB using the Service ID.
- the eNodeB manages the radio resource by using the Resource ID that is uniquely identified in the eNodeB, but manages the radio resource by using the Service ID that is uniquely identified in the communication system. Also good.
- the MME 42 does not need to manage Service ID and Resource ID, and can use the Service ID to instruct radio resources to be allocated to the UE to the eNodeB.
- FIG. 6 shows the flow of processing when the Attach procedure is completed normally in the communication system shown in FIG.
- the Attach procedure shown in FIG. 6 is based on TS23.401 V13.5.0 (2015-12) Figure 5.3.2.1-1: Attach procedure.
- TS23.401 V13.5.0 (2015-12) Figure 5.3.2.1-1 Detailed description of the same processing as that of Attach procedure is omitted.
- the Old MME / SGSN in FIG. 6 is the MME / SGSN assigned by the UE 40 at the previous Attach.
- the Serving GW in FIG. 6 corresponds to the SGW 45 in FIG. 6 corresponds to the PGW 46 in FIG.
- EIR Equipment Identity Register in FIG. 6 is not shown in FIG. 2, it is a node that manages UE identification information (for example, ME (Mobile Equipment) Identity).
- the Update Location Request message contains the IMSI of the UE.
- 9 in FIG. 6 and 10 in FIG. 6 are the same as the processing shown in TS23.401 V13.5.0 (2015-12) Figure 5.3.2.1-1: Attach procedure, and detailed description thereof will be omitted.
- MME / SGSN is performed.
- the HSS When the HSS acquires the UE's IMSI in 8 of FIG. 6, the HSS specifies the UE ⁇ Usage type associated with the acquired IMSI. Further, the HSS obtains a Service ID associated with the identified UE Usage type from the information management device. When the HSS and the information management device are the same device, the HSS further specifies the Service ID associated with the specified UE Usage type using the specified UE Usage type.
- HSS sends Update Location Ack message to new MME (11 in FIG. 6).
- the Update Location Ack message includes the Service ID.
- FIG. 6 through 16 in FIG. 6 are the same as those shown in TS23.401 V13.5.0 (2015-12) Figure 5.3.2.1-1: Attach procedure, and detailed description thereof will be omitted.
- a process of establishing a session or bearer used by the UE is mainly performed between the Serving GW and the PDN GW.
- the new MME obtains the Service ID that identifies the service used by the UE and the group to which the UE belongs, and specifies the Resource ID that identifies the radio resource allocated to the UE in the eNodeB. Resource ID is associated with Service ID.
- the new MME specifies the Resource ID, it sends an Initial Context Setup message to the eNodeB (17 in FIG. 6).
- the Initial Context Setup Request message includes a Resource ID.
- the eNodeB determines whether or not the radio resource indicated by the Resource ID transmitted from the new MME can be allocated to the UE. For example, the eNodeB may determine that the radio resource indicated by the Resource ID transmitted from the new MME can be assigned when the radio resource indicated by the Resource ID is not assigned to another UE.
- the eNodeB transmits an RRC Connection Reconfiguration message to the UE (18 in FIG. 6).
- the RRC Connection Reconfiguration message includes information for specifying the radio resource indicated by the Resource ID transmitted from the new MME.
- the information for specifying the radio resource may be, for example, frequency and time slot identification information indicating the radio resource. Thereby, the UE is notified that the radio resource included in the RAN Slice related to the service to be used can be allocated.
- FIG. 6 through 19 in FIG. 6 are the same as those shown in TS23.401 V13.5.0 (2015-12) Figure 5.3.2.1-1: Attach procedure, and detailed description thereof will be omitted.
- 19 of FIG. 6 to 26 of FIG. 6 a process for notifying the Serving GW of information related to the radio bearer established between the UE and the eNodeB is mainly executed.
- FIG. 7 shows the flow of processing when the Attach procedure is not completed normally in the communication system shown in FIG. 7 to 17 in FIG. 7 are the same as those in FIG.
- the eNodeB determines whether or not the radio resource indicated by the Resource ID can be allocated to the UE.
- the eNodeB when the eNodeB determines that the radio resource indicated by the Resource ID transmitted from the new MME cannot be allocated to the UE, the eNodeB sends an Initial Context Setup Response message to the UE without transmitting an RRC Connection Reconfiguration message to the UE. It transmits to MME (18 of FIG. 7).
- This Initial Context Setup Response message includes information indicating that radio resources cannot be allocated to the UE.
- the new MME transmits an Attach Reject message to the UE via the eNodeB (19 in FIG. 7).
- the new MME notifies the UE that the Attach procedure did not complete normally by sending an Attach Reject message to the UE. Thereby, the UE is notified that the radio resource included in the RAN Slice related to the service to be used can be allocated.
- FIG. 8 shows the flow of processing when UE triggered Service Request procedure is normally completed in the communication system shown in FIG.
- UE triggered Service Request procedure is a process executed when the UE starts data transmission or starts transmission, for example. Assuming that UE triggered Service Request procedure is executed, it is assumed that Attach procedure is normally completed and the MME manages subscriber information regarding the UE.
- the UE triggered Service Request procedure shown in FIG. 8 is based on TS23.401 V13.5.0 (2015-12)
- Figure 5.3.4.1-1 UE triggered Service Request request.
- UE triggered Service Request procedure in FIG. 8 detailed description of the same processing as in TS 23.401 V13.5.0 (2015-12)
- Figure 5.3.4.1-1 UE triggered Service Request procedure is omitted.
- the UE sends a NAS Service Request message to the MME via the eNodeB (1 in FIG. 8 and 2 in FIG. 8).
- the MME specifies the Service ID associated with the UE using the subscriber information regarding the UE.
- an authentication process for the UE is performed between the UE and the MME, and further between the MME and the HSS (3 in FIG. 8).
- the MME transmits an S1-AP: Initial Context Setup Request message including the Resource ID associated with the identified Service ID to the eNodeB (4 in FIG. 8).
- the eNodeB determines whether or not the radio resource indicated by the Resource ID transmitted from the MME can be allocated to the UE.
- the eNodeB performs the Radio Bearer Establishment process in order to allocate the radio resource indicated by the Resource ID to the UE (see FIG. 8). 5).
- the processing after 6 in FIG. 8 is the same as TS23.401 V13.5.0 (2015-12) Figure 5.3.4.1-1: UE triggered Service Request procedure, and detailed description thereof will be omitted.
- a process for notifying the Serving GW and the PDN GW of information related to the radio bearer established between the UE and the eNodeB is mainly executed.
- FIG. 9 shows a flow of processing when UE triggered Service Request procedure is not normally completed in the communication system shown in FIG. 9 to 4 in FIG. 9 are the same as those in FIG.
- the eNodeB determines whether or not the radio resource indicated by the Resource ID can be allocated to the UE.
- the eNodeB determines that the radio resource indicated by the Resource ID transmitted from the MME cannot be allocated to the UE, the eNodeB sends an S1-AP: Initial Context Setup Response message without executing the Radio Bearer Establishment process. It transmits to MME (5 of FIG. 9).
- the S1-AP: Initial Context Setup Response message includes information indicating that radio resources cannot be allocated to the UE.
- the MME transmits a NAS: Service Reject message to the UE via the eNodeB (6 in FIG. 9).
- the MME notifies the UE that the UE triggered Service Request procedure did not complete normally by sending a NAS: Service Reject message to the UE.
- the MME can specify the radio resource allocated to the UE based on the service used by the UE and the group to which the MME belongs. Specifically, the MME can specify a radio resource included in the RAN Slice associated with the service used by the UE. As a result, the eNodeB can allocate the radio resource included in the RAN ⁇ Slice to the UE that uses the service associated with the RAN Slice. As a result, the eNodeB can prevent the radio resource included in the RAN Slice associated with a service different from the service used by the UE from being allocated to the UE.
- the MME can specify a radio resource to be allocated to the UE using a Service ID that identifies a group to which the UE belongs.
- the eNodeB can determine whether or not the radio resource included in the Resource ID specified by the MME can be allocated to the UE. Accordingly, when the UE is notified that the radio resource cannot be allocated from the eNodeB, the UE reselects another eNodeB that provides the service used by the UE and has available radio resources. be able to.
- Embodiment 3 a process flow when the Attach procedure according to the third embodiment of the present disclosure is normally completed will be described.
- processing different from the processing flow in FIG. 6 will be mainly described.
- the eNodeB determines whether or not the radio resource indicated by the Resource ID can be allocated to the UE.
- the MME determines whether or not the radio resource indicated by the Resource ID can be allocated to the UE.
- the eNodeB periodically transmits the radio resource allocation status to the MME. That is, it is assumed that the MME holds the radio resource allocation status of the eNodeB.
- the new M M determines whether the Resource ID associated with the Service ID can be allocated to the UE.
- the new MME executes the processes after 12 in FIG. 6.
- the eNodeB does not execute the process of determining whether or not the radio resource can be allocated to the UE when the Initial Context Setup Request message is received in 17 of FIG. 6.
- the new MME Upon receiving the Update Location Ack message including the Service ID in 11 of FIG. 10, the new MME determines whether the Resource ID associated with the Service ID can be assigned to the UE. When it is determined that the radio resource cannot be allocated to the UE, the new MME transmits an Attach Reject message to the UE via the eNodeB without executing the processes after 12 in FIG. 6 (12 in FIG. 10). . The new MME notifies the UE that the Attach procedure did not complete normally by sending an Attach Reject message to the UE.
- Embodiment 2 determines whether or not the radio resource indicated by Resource ID can be allocated to the UE.
- the MME determines whether or not the radio resource indicated by Resource ID can be allocated to the UE.
- the eNodeB periodically transmits the radio resource allocation status to the MME. That is, it is assumed that the MME holds the radio resource allocation status of the eNodeB.
- the MME when the MME receives the NAS: Service Request message in 2 of FIG. 8, the MME specifies the Service ID using the subscriber information related to the UE, and further specifies the Resource ID associated with the Service ID. The MME determines whether or not the radio resource indicated by Resource ID can be allocated to the UE. When the MME determines that the radio resource can be allocated to the UE, the MME performs the processes after 4 in FIG. However, unlike the second embodiment, when the eNodeB receives the S1-AP: Initial Context Setup Request message in 4 of FIG. 8, the eNodeB performs a process of determining whether or not radio resources can be allocated to the UE. Do not execute.
- FIG. 11 in FIG. 11 through 3 in FIG. 11 are the same as 1 in FIG. 8 through 3 in FIG.
- the MME When the MME receives the NAS: Service Request message in 2 of FIG. 11, the MME specifies the Service ID using the subscriber information regarding the UE, and further specifies the Resource ID associated with the Service ID. The MME determines whether or not the radio resource indicated by Resource ID can be allocated to the UE. When the MME determines that the radio resource cannot be allocated to the UE, the MME transmits a NAS: Service Reject message to the UE via the eNodeB without performing the processes after 4 in FIG. 8 (4 and FIG. 11). FIG. 11-5). The MME notifies the UE that the UE triggered Service Request procedure did not complete normally by sending a NAS: Service Reject message to the UE.
- the MME can determine whether or not the radio resource indicated by the identified Resource ID can be allocated to the UE. . Accordingly, when the MME determines that radio resources cannot be allocated, the Attach procedure and UE triggered Service Request procedure are performed without performing a plurality of processes including a radio bearer setting process between the eNodeB and the UE. Can be canceled. Therefore, when the MME determines that radio resources cannot be allocated, the number of messages of Attach procedure and UE triggered Service Request ⁇ procedure can be reduced compared to the number of messages in the second embodiment.
- the communication system of FIG. 12 is a communication system that supports a 3G wireless communication system as a wireless communication system, and is a communication system defined as GPRS in 3GPP.
- the communication system shown in FIG. 12 includes MS 60, UTRAN 61, SGSN 62, GGSN 63 (Gateway GPRS Support Node), HLR (Home Location Register) 64, PDN (Packet Data Network) 65, MSC (Mobile Switching Center) / VLR (Visited Location Register). 66 and EIR67.
- the MS60 is a term used as a generic term for wireless terminals in 3GPP.
- the MS may be replaced with a UE, for example.
- the MS 60 has the same configuration as the UE 40 shown in FIG.
- the UTRAN 61 is a RAN that uses a 3G wireless system as a wireless access system.
- the UTRAN 61 has an RNC.
- the SGSN 62 is a node that executes mobility management and session management related to MS 60.
- the HLR 64 is a node that manages subscriber information regarding the MS 60.
- the subscriber information includes information regarding services used by the MS 60.
- the GGSN 63 is a node that relays data transmitted between the MS 60 and the PDN 65.
- the PDN 65 may be, for example, a server device managed by a provider that provides services to the MS 60, or a network including a server device group.
- the MSC / VLR 66 is a node that has a circuit switching function and manages MS subscriber information.
- the EIR 67 is a node that manages MS identification information (for example, IMEI: International Mobile Equipment Identity).
- a Uu reference point is defined between the MS 60 and the UTRAN 61.
- An Iu reference point is defined between the UTRAN 61 and the SGSN 62.
- a Gn reference point is defined between the SGSN 62 and the GGSN 63.
- a Gr reference point is defined between the SGSN 62 and the HLR 64.
- a Gc reference point is defined between the GGSN 63 and the HLR 64.
- a Gi reference point is defined between the GGSN 63 and the PDN 65.
- An Iu reference point is defined between the UTRAN 61 and the MSC / VLR 66.
- a Gs reference point is defined between the SGSN 62 and the MSC / VLR 66.
- a D reference point is defined between the HLR 64 and the MSC / VLR 66.
- a Gp reference point is defined between the SGSN 62 and the EIR 67.
- the configuration of radio resources managed in the RNC included in the UTRAN 61 is the same as in FIG. That is, the radio resource group managed by the eNodeB in FIG. 4 is replaced with the radio resource group managed by the RNC.
- MS 60, RNC, SGSN 62, HLR 64, and information held by the information management device are the same as in FIG. That is, UE 40 in FIG. 5 is replaced with MS 60, eNodeB in FIG. 5 is replaced with RNC, MME 42 in FIG. 5 is replaced with SGSN 62, and HSS 43 in FIG. 5 is replaced with HLR 64.
- FIG. 13 shows the flow of processing when Combined GPRS / IMSI Attach Procedure is normally completed in the communication system shown in FIG.
- the Combined GPRS / IMSI Attach Procedure shown in FIG. 13 is based on TS23.060 V13.5.0 (2015-12)
- Figure 22 Combined GPRS / IMSI Attach Procedure.
- Combined GPRS / IMSI Attach Procedure is omitted.
- the MS in FIG. 13 corresponds to the MS 60 in FIG.
- the RAN in FIG. 13 corresponds to the UTRAN 61 in FIG.
- the new SGSN in FIG. 13 corresponds to the SGSN 62 in FIG. 12.
- the old SGSN in FIG. 13 is the SGSN assigned by the MS 60 in the previous Combined GPRS / IMSI Attach Procedure.
- Combined GPRS / IMSI Attach Procedure shown in FIG. 13 for example, the MS 60 has moved, so that an SGSN (new SGSN) different from the SGSN (Old SGSN) assigned in the previous Combined GPRS / IMSI Attach Procedure was assigned. The operation in this case will be described.
- GGSN in FIG. 13 corresponds to GGSN 63 in FIG.
- the HLR in FIG. 13 corresponds to the HLR 64 in FIG. 13 corresponds to the MSC / VLR 66 in FIG.
- the oldolMSC / VLR in FIG. 13 is the MSC / VLR assigned by the MS 60 in the previous Combined GPRS / IMSI Attach Procedure.
- the EIR in FIG. 13 corresponds to the EIR 67 in FIG.
- the new SGSN transmits an Update Location Request message to the HLR (7a in FIG. 13).
- the Update-Location-Request message contains the IMSI of the MS. 13b to 7e in FIG. 13 are the same as the processes shown in TS23.06013V13.5.0 (2015-12)
- Figure 22 Combined GPRS / IMSI Attach Procedure, and detailed description thereof will be omitted.
- the processing for deleting the information on the MS managed in the Old SGSN is mainly executed.
- the HLR When the HLR acquires the IMS's IMSI in 7a of FIG. 13, the HLR identifies the UE Usage type associated with the acquired IMSI. Further, the HLR obtains a Service ID associated with the identified UE Usage type from the information management device. When the HLR and the information management device are the same device, the HLR further specifies the Service ID associated with the specified UE Usage type using the specified UE Usage type.
- the HLR transmits an Insert Subscriber Data message to the new SGSN (7f in FIG. 13).
- the Insert Subscriber Data message includes the Service ID.
- FIG. 13g to 8h in FIG. 13 are the same as the processes shown in TS23.060 V13.5.0 (2015-12)
- Figure 22 Combined GPRS / IMSI Attach Procedure, and detailed description thereof will be omitted.
- the process of registering the SGSN and MSC / VLR assigned in the current Attach Procedure is mainly performed in the HLR.
- the Service ID is included in the Insert Subscriber Data message in 7f of FIG. 13, the Service ID may be included in the Update Location Ack message in 7h of FIG.
- FIG. 13 through 12 in FIG. 13 are the same as the processes shown in TS23.060 V13.5.0 (2015-12)
- Figure 22 Combined GPRS / IMSI Attach Procedure, and detailed description thereof will be omitted.
- processing accompanying the completion of Attach Procedure is mainly executed.
- the PDP Context Activation Procedure Procedure Iu mode is a process executed when the MS starts data transmission or transmission, for example. Assuming that PDP Context Activation Procedure for Iu mode is executed, it is assumed that Attach ⁇ procedure has been completed normally and the SGSN is managing subscriber information regarding the MS.
- the MS transmits an Activate PDP Context Request message to the SGSN via the RAN (1 in FIG. 14).
- the SGSN specifies the Service ID associated with the MS using the subscriber information of the MS. 14 in FIG. 14 is the same processing as TS23.060 V13.5.0 (2015-12)
- Figure 64 PDP Context Procedure for Iu mode, and thus detailed description is omitted.
- the process which mainly establishes the session or bearer which MS uses between SGSN and GGSN is performed.
- the SGSN notifies the RAN of the Resource ID associated with the specified Service ID in the Radio Access Bearer process (5 in FIG. 14). Further, the RAN determines whether the radio resource indicated by the Resource ID transmitted from the SGSN can be allocated to the MS. If the RAN determines that the radio resource indicated by the Resource ID transmitted from the SGSN can be allocated to the MS, the RAN allocates the radio resource indicated by the Resource ID to the MS in the Radio Access Bearer Setup process 5 in FIG. 14 and subsequent processes are the same as TS23.060 V13.5.0 (2015-12)
- Figure 64 PDP Context Activation Procedure for Iu ⁇ ⁇ mode, and detailed description thereof will be omitted. In the processes after 6 in FIG. 8, a process for notifying the GGSN of information related to the radio bearer established between the MS and the RAN is mainly performed.
- FIG. 15 shows the flow of processing when PDP Context Activation Procedure for Iu mode does not complete normally in the communication system shown in FIG. 15 and 4 in FIG. 15 are the same as those in FIG.
- the SGSN sends RAB Assignment Request message including Resource ID to RAN (7 in FIG. 15).
- the RAN receives the RAB Assignment Request message including the Resource ID in 7 of FIG. 15, the RAN determines whether or not the radio resource indicated by the Resource ID can be allocated to the MS.
- the RAN determines that the radio resource indicated by the Resource ID transmitted from the SGSN cannot be allocated to the MS, the RAN transmits an RAB Assignment Response message to the SGSN without establishing a radio bearer with the MS (see FIG. 15-7).
- the SGSN sends / receives a Delete PDP Context Request / Response message to / from the GGSN in order to delete the PDP Context with the GGSN set in 4 of Fig.15 (8 in Fig.15).
- the SGSN sends an Activate PDP Context Reject message to the MS via the RAN (9 in FIG. 15).
- the SGSN notifies the MS that PDP Context Activation Procedure for Iu mode has not been successfully completed by sending an Activate PDP Context Reject message to the MS.
- MS Initiated Service Request Procedure using GN / Gp shown in FIG. 16 is based on TS23.060 V13.5.0 (2015-12)
- Figure 50 MS Initiated Service Request Procedure using GN / Gp.
- Figure 50 Detailed explanation of processing similar to MS Initiated Service Request Procedure using GN / Gp is omitted. .
- FIG. 16 shows the flow of processing when the MS Initiated Service Request Procedure GN / Gp is normally completed in the communication system of FIG.
- MS Initiated Service Procedure using GN / Gp is a process executed when the MS starts data transmission or starts transmission, for example. Assuming that MS Initiated Service Procedure using GN / Gp is executed, it is assumed that Attach procedure has been completed normally and the SGSN manages subscriber information related to the MS.
- FIG. 16 the RAN in FIGS. 13 to 15 will be described as an RNC that the UTRAN 61 has.
- 16 in FIG. 16 is the same as the processing shown in TS23.060 V13.5.0 (2015-12)
- Figure 50 MS Initiated Service Request Procedure using GN / Gp, and detailed description thereof will be omitted.
- the MS transmits a Service request message to the SGSN via the RNC (2 in FIG. 16).
- the SGSN specifies the Service ID associated with the MS using the subscriber information regarding the MS.
- authentication processing related to the MS is executed between the MS and the RNC, between the RNC and the SGSN, and further between the SGSN and the HLR (3 in FIG. 16).
- the SGSN transmits a Radio Access Bearer Assignment Request message including the Resource ID associated with the identified Service ID to the RNC (4 in FIG. 16).
- the RNC determines whether or not the radio resource indicated by the Resource ID transmitted from the SGSN can be allocated to the MS.
- the RNC transmits a Radio Bearer Setup message in order to allocate the radio resource indicated by the Resource ID to the MS (FIG. 16). 5).
- the processing after 6 in FIG. 16 is the same as TS23.060 V13.5.0 (2015-12)
- Figure 50 MS Initiated Service Request Procedure using GN / Gp, and detailed description thereof will be omitted.
- FIG. 17 shows the flow of processing when MS ⁇ ⁇ ⁇ ⁇ ⁇ Initiated Service Request Procedure using GN / Gp does not complete normally in the communication system of FIG.
- the RNC determines whether or not the radio resource indicated by the Resource ID transmitted from the SGSN in 4 of FIG. 17 can be allocated to the MS. If the RNC determines that the radio resource indicated by the Resource ID transmitted from the SGSN cannot be allocated to the MS, the RNC transmits a Radio Access Bearer Assignment Response message to the MS without sending a Radio Bearer Setup message to the MS (see FIG. 17-5). Next, the SGSN transmits a Service-Reject message to the MS via the RNC (6 in FIG. 17). The SGSN notifies the MS that MS / Initiated / Service / Request / Procedure / using / GN / Gp did not complete normally by sending a Service / Reject message to the MS.
- the RAN or the RNC is associated with a service different from the service used by the MS. It is possible to prevent radio resources included in Slice from being assigned to the MS.
- the SGSN can specify a radio resource assigned to the MS using a Service ID that identifies a group to which the MS belongs.
- the RAN or RNC can determine whether or not the radio resource included in the Resource ID specified from the SGSN can be allocated to the MS. Accordingly, when the MS is notified that the radio resource cannot be allocated from the RAN, the MS reselects another RAN that provides the service used by the MS and that has the available radio resource. be able to.
- the RAN determines whether or not the radio resource indicated by the Resource ID can be allocated to the MS.
- the SGSN determines whether or not the radio resource indicated by the Resource ID can be allocated to the MS.
- the RAN periodically transmits the radio resource allocation status to the SGSN. That is, the SGSN holds the RAN radio resource allocation status.
- the SGSN when receiving the Activate PDP Context Request message in 1 of FIG. 14, the SGSN specifies the Service ID using the subscriber information regarding the MS, and further specifies the Resource ID associated with the Service ID. The SGSN determines whether or not the radio resource indicated by the Resource ID can be allocated to the MS. When the SGSN determines that the radio resource can be allocated to the MS, the SGSN executes the processes after 4 in FIG. However, the RAN does not execute the process of determining whether or not radio resources can be allocated to the MS in 5 of FIG.
- the SGSN When the SGSN receives the Activate PDP Context Request message in 1 of FIG. 18, the SGSN specifies the Service ID using the subscriber information regarding the MS, and further specifies the Resource ID associated with the Service ID. The SGSN determines whether or not the radio resource indicated by the Resource ID can be allocated to the MS. When the SGSN determines that the radio resource cannot be allocated to the MS, the SGSN transmits an Activate PDP Context Reject message to the MS via the RAN without executing the processes of 4 and after in FIG. 14 (2 in FIG. 18). . The SGSN notifies the UE that PDP Context Activation Procedure for Iu mode has not been successfully completed by sending an Activate PDP Context Reject message to the MS.
- the RAN determines whether or not the radio resource indicated by the Resource ID can be allocated to the MS.
- the SGSN determines whether or not the radio resource indicated by the Resource ID can be allocated to the MS.
- the RAN periodically transmits the radio resource allocation status to the SGSN. That is, the SGSN holds the RAN radio resource allocation status.
- the SGSN when receiving the Service request message in 2 of FIG. 16, the SGSN specifies the Service ID using the subscriber information related to the MS, and further specifies the Resource ID associated with the Service ID. The SGSN determines whether or not the radio resource indicated by the Resource ID can be allocated to the MS. When the SGSN determines that the radio resource can be allocated to the MS, the SGSN executes the processes after 3 in FIG. However, the RAN does not execute the process of determining whether or not radio resources can be allocated to the MS in 4 of FIG.
- the SGSN When the SGSN receives the Service Request message in 2 of FIG. 19, the SGSN specifies the Service ID using the subscriber information regarding the MS, and further specifies the Resource ID associated with the Service ID. The SGSN determines whether or not the radio resource indicated by the Resource ID can be allocated to the MS. If the SGSN determines that the radio resource cannot be allocated to the MS, the SGSN transmits a Service Reject message to the MS via the RNC without executing the processing of 4 and subsequent steps in FIG. 16 (4 in FIG. 19). The SGSN notifies the UE that the MS Initiated Service Request Procedure using GN / Gp did not complete normally by sending a Service Reject message to the MS.
- the SGSN can determine whether or not the radio resource indicated by the identified Resource ID can be allocated to the UE. . Accordingly, when the SGSN determines that radio resources cannot be allocated, the Attach procedure, PDP Context can be performed without performing a plurality of processes including a radio bearer setting process between the RAN (RNC) and the MS. Activation Procedure for Iu mode and MS Initiated Service Request Procedure using GN / Gp can be canceled. Therefore, when the SGSN determines that radio resources cannot be allocated, the number of messages of Attach procedure, PDP Context Activation Procedure for Iu mode, and MS Initiated Service Request Procedure using GN / Gp can be reduced.
- FIG. 20 is a block diagram illustrating a configuration example of the base station 20.
- the base station 20 includes an RF transceiver 1001, a network interface 1003, a processor 1004, and a memory 1005.
- the RF transceiver 1001 performs analog RF signal processing to communicate with UEs.
- the RF transceiver 1001 may include multiple transceivers.
- RF transceiver 1001 is coupled to antenna 1002 and processor 1004.
- the RF transceiver 1001 receives modulation symbol data (or OFDM symbol data) from the processor 1004, generates a transmission RF signal, and supplies the transmission RF signal to the antenna 1002. Further, the RF transceiver 1001 generates a baseband received signal based on the received RF signal received by the antenna 1002, and supplies this to the processor 1004.
- the network interface 1003 is used to communicate with a network node (e.g., core node 10).
- the network interface 1003 may include, for example, a network interface card (NIC) compliant with IEEE 802.3 series.
- NIC network interface card
- the processor 1004 performs data plane processing including digital baseband signal processing for wireless communication and control plane processing.
- the digital baseband signal processing by the processor 1004 may include MAC layer and PHY layer signal processing.
- the processor 1004 may include a plurality of processors.
- the processor 1004 may include a modem processor (e.g., DSP) that performs digital baseband signal processing, and a protocol stack processor (e.g., CPU or MPU) that performs control plane processing.
- DSP digital baseband signal processing
- protocol stack processor e.g., CPU or MPU
- the memory 1005 is configured by a combination of a volatile memory and a nonvolatile memory.
- the memory 1005 may include a plurality of physically independent memory devices.
- the volatile memory is, for example, Static Random Access Memory (SRAM), Dynamic RAM (DRAM), or a combination thereof.
- the non-volatile memory is a mask Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, hard disk drive, or any combination thereof.
- Memory 1005 may include storage located remotely from processor 1004. In this case, the processor 1004 may access the memory 1005 via the network interface 1003 or an I / O interface not shown.
- the memory 1005 may store a software module (computer program) including an instruction group and data for performing processing by the base station 20 described in the above embodiments.
- the processor 1004 may be configured to perform the processing of the remote node 10 described in the above-described embodiment by reading the software module from the memory 1005 and executing the software module.
- FIG. 21 is a block diagram illustrating a configuration example of the wireless terminal 30.
- the radio frequency (RF) transceiver 1101 performs analog RF signal processing to communicate with the base station 20. Analog RF signal processing performed by the RF transceiver 1101 includes frequency up-conversion, frequency down-conversion, and amplification.
- RF transceiver 1101 is coupled with antenna 1102 and baseband processor 1103. That is, the RF transceiver 1101 receives modulation symbol data (or OFDM symbol data) from the baseband processor 1103, generates a transmission RF signal, and supplies the transmission RF signal to the antenna 1102. Further, the RF transceiver 1101 generates a baseband received signal based on the received RF signal received by the antenna 1102 and supplies this to the baseband processor 1103.
- modulation symbol data or OFDM symbol data
- the baseband processor 1103 performs digital baseband signal processing (data plane processing) and control plane processing for wireless communication.
- Digital baseband signal processing consists of (a) data compression / decompression, (b) data segmentation / concatenation, (c) ⁇ transmission format (transmission frame) generation / decomposition, and (d) transmission path encoding / decoding.
- E modulation (symbol mapping) / demodulation
- IFFT Inverse Fast Fourier Transform
- control plane processing includes layer 1 (eg, transmission power control), layer 2 (eg, radio resource management, hybrid automatic repeat request (HARQ) processing), and layer 3 (eg, attach, mobility, and call management). Communication management).
- the digital baseband signal processing by the baseband processor 1103 includes signal processing of Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, MAC layer, and PHY layer. But you can. Further, the control plane processing by the baseband processor 1103 may include Non-Access Stratum (NAS) protocol, RRC protocol, and MAC ⁇ CE processing.
- PDCP Packet Data Convergence Protocol
- RLC Radio Link Control
- MAC Medium Access Stratum
- PHY Packet Data Convergence Protocol
- the control plane processing by the baseband processor 1103 may include Non-Access Stratum (NAS) protocol, RRC protocol, and MAC ⁇ CE processing.
- NAS Non-Access Stratum
- the baseband processor 1103 includes a modem processor (eg, Digital Signal Processor (DSP)) that performs digital baseband signal processing and a protocol stack processor (eg, Central Processing Unit (CPU) that performs control plane processing, or Micro Processing Unit. (MPU)).
- DSP Digital Signal Processor
- protocol stack processor eg, Central Processing Unit (CPU) that performs control plane processing, or Micro Processing Unit. (MPU)
- CPU Central Processing Unit
- MPU Micro Processing Unit.
- a protocol stack processor that performs control plane processing may be shared with an application processor 1104 described later.
- the application processor 1104 is also called a CPU, MPU, microprocessor, or processor core.
- the application processor 1104 may include a plurality of processors (a plurality of processor cores).
- the application processor 1104 is a system software program (Operating System (OS)) read from the memory 1106 or a memory (not shown) and various application programs (for example, a call application, a web browser, a mailer, a camera operation application, music playback)
- OS Operating System
- the baseband processor 1103 and application processor 1104 may be integrated on a single chip, as indicated by the dashed line (1105) in FIG.
- the baseband processor 1103 and the application processor 1104 may be implemented as one System on Chip (SoC) device 1105.
- SoC System on Chip
- An SoC device is sometimes called a system Large Scale Integration (LSI) or chipset.
- the memory 1106 is a volatile memory, a nonvolatile memory, or a combination thereof.
- the memory 1106 may include a plurality of physically independent memory devices.
- the volatile memory is, for example, Static Random Access Memory (SRAM), Dynamic RAM (DRAM), or a combination thereof.
- the non-volatile memory is a mask Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, hard disk drive, or any combination thereof.
- the memory 1106 may include an external memory device accessible from the baseband processor 1103, the application processor 1104, and the SoC 1105.
- Memory 1106 may include an embedded memory device integrated within baseband processor 1103, application processor 1104, or SoC 1105.
- the memory 1106 may include a memory in a Universal Integrated Circuit Card (UICC).
- UICC Universal Integrated Circuit Card
- the memory 1106 may store a software module (computer program) including an instruction group and data for performing processing by the wireless terminal 30 described in the above-described embodiments.
- the baseband processor 1103 or the application processor 1104 may be configured to perform the processing of the wireless terminal 30 described in the above-described embodiment by reading the software module from the memory 1106 and executing the software module. Good.
- FIG. 22 is a block diagram illustrating a configuration example of the core node 10.
- the center node 20 includes a network interface 1201, a processor 1202, and a memory 1203.
- the network interface 1201 is used to communicate with a network node (e.g., base station 20).
- the network interface 1201 may include, for example, a network interface card (NIC) compliant with IEEE 802.3 series.
- NIC network interface card
- the processor 1202 reads the software (computer program) from the memory 1203 and executes it, thereby performing the processing of the core node 10 described using the sequence diagram and the flowchart in the above-described embodiment.
- the processor 1202 may be, for example, a microprocessor, MPU, or CPU.
- the processor 1202 may include a plurality of processors.
- the processor 1202 performs data plane processing and control plane processing including digital baseband signal processing for wireless communication.
- the digital baseband signal processing by the processor 1004 may include PDCP layer, RLC layer, and MAC layer signal processing.
- the signal processing by the processor 1202 may include GTP-U • UDP / IP layer signal processing at the X2-U interface and the S1-U interface.
- the control plane processing by the processor 1004 may include processing of the X2AP protocol, the S1-MME protocol, and the RRC protocol.
- the processor 1202 may include a plurality of processors.
- the processor 1004 includes a modem processor (eg, DSP) that performs digital baseband signal processing, a processor that performs signal processing of the GTP-U / UDP / IP layer in the X2-U interface and the S1-U interface (eg, DSP) and a protocol stack processor (eg, CPU or MPU) that performs control plane processing may be included.
- DSP modem processor
- a processor that performs signal processing of the GTP-U / UDP / IP layer in the X2-U interface and the S1-U interface eg, DSP
- a protocol stack processor eg, CPU or MPU
- the memory 1203 is configured by a combination of a volatile memory and a nonvolatile memory.
- Memory 1203 may include storage located remotely from processor 1202. In this case, the processor 1202 may access the memory 1203 via an I / O interface not shown.
- the memory 1203 is used for storing software module groups.
- the processor 1202 can perform the processing of the core node 10 described in the above-described embodiment by reading these software module groups from the memory 1203 and executing them.
- each of the processors included in the base station 20, the wireless terminal 30, and the core node 10 in the above-described embodiment causes the computer to execute the algorithm described with reference to the drawings.
- One or more programs including a group of instructions are executed.
- Non-transitory computer readable media include various types of tangible storage media (tangible storage medium).
- Examples of non-transitory computer-readable media include magnetic recording media (eg flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (eg magneto-optical discs), CD-ROMs (Read Only Memory), CD-Rs, CD-R / W, semiconductor memory (for example, mask ROM, PROM (Programmable ROM), EPROM (Erasable ROM), flash ROM, RAM (Random Access Memory)) are included.
- the program may also be supplied to the computer by various types of temporary computer-readable media. Examples of transitory computer readable media include electrical signals, optical signals, and electromagnetic waves.
- the temporary computer-readable medium can supply the program to the computer via a wired communication path such as an electric wire and an optical fiber, or a wireless communication path.
- a determination unit that determines a radio resource to be allocated according to a service provided to the radio terminal;
- a core node comprising: a communication unit that transmits resource identification information indicating the radio resource determined by the determination unit to a base station that manages a plurality of radio resources for each RAN Slice associated with the service.
- the determination unit Indicates a service used by the wireless terminal, manages service identification information uniquely identified in a mobile core network and the resource identification information in association with each other, and associates the terminal identification information of the wireless terminal with the service identification information
- the determination unit Any one of appendices 1 to 3, wherein it is determined whether or not there is a radio resource to be allocated to the radio terminal in a RAN Slice that provides a service used by the radio terminal based on a radio resource utilization state in the base station.
- the core node according to item 1.
- the communication unit is Item 5.
- the appendix 4 wherein when the determining unit determines that there is no radio resource to be allocated to the radio terminal, a rejection message indicating that radio resource cannot be allocated to the radio terminal via the base station is transmitted. Core node.
- Appendix 6 A management unit that manages a plurality of radio resources for each RAN Slice associated with the service; A communication unit that receives resource identification information that is transmitted from the core node and indicates radio resources to be allocated according to a service provided to a radio terminal; A resource allocation unit that allocates the radio resource indicated by the resource identification information to the radio terminal, base station. (Appendix 7) The resource allocation unit The base station according to appendix 6, wherein it is determined whether or not the radio resource indicated by the resource identification information is allocated to the radio terminal according to a usage state of the radio resource.
- the communication unit that further transmits a rejection message indicating that a radio resource cannot be allocated to the radio terminal when the resource allocation unit determines that there is no radio resource to be allocated to the radio terminal.
- Base station (Appendix 9) A receiving unit for receiving broadcast information transmitted by a plurality of base stations; A determination unit that determines to connect to a base station that has transmitted broadcast information including RAN Slice identification information indicating RAN Slice indicating a RAN Slice that provides a service used by the terminal among the plurality of base stations; Terminal.
- the determination unit When there are a plurality of base stations that have transmitted broadcast information including RAN Slice identification information indicating the RAN Slice providing the service to be used, the base station to be connected based on the radio wave intensity of the radio wave output from each base station is selected. The wireless terminal according to attachment 9, wherein the wireless terminal is determined. (Appendix 11) The determination unit When receiving a rejection message indicating that radio resources cannot be allocated from the base station, from among a plurality of base stations that have transmitted broadcast information including RAN Slice identification information indicating a RAN Slice that provides a service to be used The wireless terminal according to appendix 9 or 10, wherein the wireless terminal determines to connect to a base station different from the determined base station.
- (Appendix 12) Determine the radio resource to be allocated according to the service provided to the radio terminal, A communication method for transmitting resource identification information indicating a determined radio resource to a base station that manages a plurality of radio resources for each RAN Slice associated with a service.
- (Appendix 13) Manage multiple radio resources for each RAN Slice associated with the service, Receiving resource identification information transmitted from the core node and indicating the radio resource to be allocated according to the service provided to the radio terminal; A radio resource assignment method for assigning a radio resource indicated by the resource identification information to the radio terminal.
- (Appendix 14) Receiving each broadcast information transmitted by a plurality of base stations, A base station selection method for determining to connect to a base station that has transmitted broadcast information including RAN Slice identification information indicating a RAN Slice that provides a service to be used from among the plurality of base stations. (Appendix 15) Determine the radio resource to be allocated according to the service provided to the radio terminal, A program that causes a computer to execute transmission of resource identification information indicating a determined radio resource to a base station that manages a plurality of radio resources for each RAN Slice associated with a service.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Quality & Reliability (AREA)
- Databases & Information Systems (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
以下、図面を参照して本開示の実施の形態について説明する。図1を用いて本開示の実施の形態1にかかる通信システムの構成例について説明する。図1は、コアノード10、基地局20、及び、無線端末30を有している。コアノード10、基地局20、及び、無線端末30は、プロセッサがメモリに格納されたプログラムを実行することによって動作するコンピュータ装置であってもよい。
続いて、図2を用いて本開示の実施の形態2にかかる通信システムの構成例について説明する。図2の通信システムは、無線通信方式としてLTEをサポートする通信システムであり、3GPPにおいてEPS(Evolved Packet System)として規定された通信システムである。なお、図2は、TS 23.401 V 13.5.0 Figure 4.2.1-1の図に基づいている。
続いて、本開示の実施の形態3にかかるAttach procedureが正常に完了する場合の処理の流れについて説明する。ここでは、図6における処理の流れと異なる処理について主に説明する。実施の形態2においては、eNodeBが、Resource IDが示す無線リソースをUEへ割り当てることができるか否かを判定する。一方、実施の形態3においては、MMEが、Resource IDが示す無線リソースをUEへ割り当てることができるか否かを判定する。
続いて、図12を用いて本開示の実施の形態4にかかる通信システムの構成例について説明する。図12の通信システムは、無線通信方式として3G無線通信方式をサポートする通信システムであり、3GPPにおいてGPRSとして規定された通信システムである。
続いて本開示の実施の形態5にかかる、PDP Context Activation Procedure for Iu modeが正常に完了する場合の処理の流れについて説明する。ここでは、図14における処理の流れと異なる処理について主に説明する。実施の形態4においては、RANが、Resource IDが示す無線リソースをMSへ割り当てることができるか否かを判定する。一方、実施の形態5においては、SGSNが、Resource IDが示す無線リソースをMSへ割り当てることができるか否かを判定する。
(付記1)
無線端末へ提供されるサービスに応じて割り当てる無線リソースを決定する決定部と、
複数の無線リソースを、サービスに関連付けられたRAN Sliceごとに管理する基地局へ、前記決定部において決定された無線リソースを示すリソース識別情報を送信する通信部と、を備える
コアノード。
(付記2)
前記決定部は、
前記無線端末が利用するサービスを示し、モバイルコアネットワークにおいて一意に識別されるサービス識別情報と、前記リソース識別情報とを関連付けて管理し、前記無線端末の端末識別情報と前記サービス識別情報とを関連付けて管理している管理装置から、前記サービス識別情報を取得する、付記1に記載のコアノード。
(付記3)
前記リソース識別情報として、モバイルコアネットワークにおいて一意に識別される前記サービス識別情報が用いられる、付記2に記載のコアノード。
(付記4)
前記決定部は、
前記基地局における無線リソースの利用状況に基づいて、前記無線端末が利用するサービスを提供するRAN Sliceにおいて前記無線端末に割り当てる無線リソースが存在するか否かを判定する、付記1乃至3のいずれか1項に記載のコアノード。
(付記5)
前記通信部は、
前記決定部において前記無線端末に割り当てる無線リソースが存在しないと判定された場合、前記基地局を介して前記無線端末へ無線リソースを割り当てることができないことを示す拒否メッセージを送信する、付記4に記載のコアノード。
(付記6)
複数の無線リソースを、サービスに関連づけられたRAN Sliceごとに管理する管理部と、
コアノードから送信された、無線端末へ提供されるサービスに応じて割り当てる無線リソースを示すリソース識別情報を受信する通信部と、
前記リソース識別情報に示される無線リソースを前記無線端末へ割り当てるリソース割当部と、を備える、
基地局。
(付記7)
前記リソース割当部は、
無線リソースの利用状況に応じて、前記リソース識別情報に示される無線リソースを前記無線端末へ割り当てるか否かを判定する、付記6に記載の基地局。
(付記8)
前記リソース割当部において前記無線端末へ割り当てる無線リソースが存在しないと判定された場合、前記無線端末へ無線リソースを割り当てることができないことを示す拒否メッセージを送信する通信部をさらに備える、付記7に記載の基地局。
(付記9)
複数の基地局が送信するそれぞれの報知情報を受信する受信部と、
前記複数の基地局の中から、自端末が利用するサービスを提供するRAN Sliceを示すRAN Slice識別情報を含む報知情報を送信してきた基地局と接続することを決定する決定部と、を備える無線端末。
(付記10)
前記決定部は、
利用するサービスを提供するRAN Sliceを示すRAN Slice識別情報を含む報知情報を送信してきた基地局が複数存在する場合、それぞれの基地局から出力される電波の電波強度に基づいて接続する基地局を決定する、付記9に記載の無線端末。
(付記11)
前記決定部は、
前記基地局から無線リソースを割り当てることができないことを示す拒否メッセージを受信した場合、利用するサービスを提供するRAN Sliceを示すRAN Slice識別情報を含む報知情報を送信してきた複数の基地局の中から、決定した前記基地局と異なる基地局と接続することを決定する、付記9又は10に記載の無線端末。
(付記12)
無線端末へ提供されるサービスに応じて割り当てる無線リソースを決定し、
複数の無線リソースを、サービスに関連付けられたRAN Sliceごとに管理する基地局へ、決定された無線リソースを示すリソース識別情報を送信する、通信方法。
(付記13)
複数の無線リソースを、サービスに関連づけられたRAN Sliceごとに管理し、
コアノードから送信された、無線端末へ提供されるサービスに応じて割り当てる無線リソースを示すリソース識別情報を受信し、
前記リソース識別情報に示される無線リソースを前記無線端末へ割り当てる、無線リソース割当方法。
(付記14)
複数の基地局が送信するそれぞれの報知情報を受信し、
前記複数の基地局の中から、利用するサービスを提供するRAN Sliceを示すRAN Slice識別情報を含む報知情報を送信してきた基地局と接続することを決定する、基地局選択方法。
(付記15)
無線端末へ提供されるサービスに応じて割り当てる無線リソースを決定し、
複数の無線リソースを、サービスに関連付けられたRAN Sliceごとに管理する基地局へ、決定された無線リソースを示すリソース識別情報を送信することをコンピュータに実行させるプログラム。
12 通信部
14 決定部
20 基地局
22 通信部
24 管理部
26 リソース割当部
30 無線端末
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
60 MS
61 UTRAN
62 SGSN
63 GGSN
64 HLR
65 PDN
66 MSC/VLR
67 EIR
71 通信部
72 RAN Slice利用可否判定部
73 接続先RAN Slice選択部
81 制御部
82 通信部
Claims (15)
- 無線端末へ提供されるサービスに応じて割り当てる無線リソースを決定する決定手段と、
複数の無線リソースを、サービスに関連付けられたRAN Sliceごとに管理する基地局へ、前記決定手段において決定された無線リソースを示すリソース識別情報を送信する通信手段と、を備える
コアノード。 - 前記決定手段は、
前記無線端末が利用するサービスを示し、モバイルコアネットワークにおいて一意に識別されるサービス識別情報と、前記リソース識別情報とを関連付けて管理し、前記無線端末の端末識別情報と前記サービス識別情報とを関連付けて管理している管理装置から、前記サービス識別情報を取得する、請求項1に記載のコアノード。 - 前記リソース識別情報として、モバイルコアネットワークにおいて一意に識別される前記サービス識別情報が用いられる、請求項2に記載のコアノード。
- 前記決定手段は、
前記基地局における無線リソースの利用状況に基づいて、前記無線端末が利用するサービスを提供するRAN Sliceにおいて前記無線端末に割り当てる無線リソースが存在するか否かを判定する、請求項1乃至3のいずれか1項に記載のコアノード。 - 前記通信手段は、
前記決定手段において前記無線端末に割り当てる無線リソースが存在しないと判定された場合、前記基地局を介して前記無線端末へ無線リソースを割り当てることができないことを示す拒否メッセージを送信する、請求項4に記載のコアノード。 - 複数の無線リソースを、サービスに関連づけられたRAN Sliceごとに管理する管理部と、
コアノードから送信された、無線端末へ提供されるサービスに応じて割り当てる無線リソースを示すリソース識別情報を受信する通信手段と、
前記リソース識別情報に示される無線リソースを前記無線端末へ割り当てるリソース割当手段と、を備える、
基地局。 - 前記リソース割当手段は、
無線リソースの利用状況に応じて、前記リソース識別情報に示される無線リソースを前記無線端末へ割り当てるか否かを判定する、請求項6に記載の基地局。 - 前記リソース割当手段において前記無線端末へ割り当てる無線リソースが存在しないと判定された場合、前記無線端末へ無線リソースを割り当てることができないことを示す拒否メッセージを送信する通信手段をさらに備える、請求項7に記載の基地局。
- 複数の基地局が送信するそれぞれの報知情報を受信する受信手段と、
前記複数の基地局の中から、自端末が利用するサービスを提供するRAN Sliceを示すRAN Slice識別情報を含む報知情報を送信してきた基地局と接続することを決定する決定手段と、を備える無線端末。 - 前記決定手段は、
利用するサービスを提供するRAN Sliceを示すRAN Slice識別情報を含む報知情報を送信してきた基地局が複数存在する場合、それぞれの基地局から出力される電波の電波強度に基づいて接続する基地局を決定する、請求項9に記載の無線端末。 - 前記決定手段は、
前記基地局から無線リソースを割り当てることができないことを示す拒否メッセージを受信した場合、利用するサービスを提供するRAN Sliceを示すRAN Slice識別情報を含む報知情報を送信してきた複数の基地局の中から、決定した前記基地局と異なる基地局と接続することを決定する、請求項9又は10に記載の無線端末。 - 無線端末へ提供されるサービスに応じて割り当てる無線リソースを決定し、
複数の無線リソースを、サービスに関連付けられたRAN Sliceごとに管理する基地局へ、決定された無線リソースを示すリソース識別情報を送信する、通信方法。 - 複数の無線リソースを、サービスに関連づけられたRAN Sliceごとに管理し、
コアノードから送信された、無線端末へ提供されるサービスに応じて割り当てる無線リソースを示すリソース識別情報を受信し、
前記リソース識別情報に示される無線リソースを前記無線端末へ割り当てる、無線リソース割当方法。 - 複数の基地局が送信するそれぞれの報知情報を受信し、
前記複数の基地局の中から、利用するサービスを提供するRAN Sliceを示すRAN Slice識別情報を含む報知情報を送信してきた基地局と接続することを決定する、基地局選択方法。 - 無線端末へ提供されるサービスに応じて割り当てる無線リソースを決定し、
複数の無線リソースを、サービスに関連付けられたRAN Sliceごとに管理する基地局へ、決定された無線リソースを示すリソース識別情報を送信することをコンピュータに実行させるプログラムが格納された非一時的なコンピュータ可読媒体。
Priority Applications (9)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2018507150A JP6806137B2 (ja) | 2016-03-23 | 2017-02-22 | 基地局及び方法 |
US16/083,577 US10405239B2 (en) | 2016-03-23 | 2017-02-22 | Core node, base station, radio terminal, communication method, radio resource allocation method, base station selection method, and readable medium |
EP17769781.0A EP3435713A4 (en) | 2016-03-23 | 2017-02-22 | CENTER NODE, BASE STATION, WIRELESS TERMINAL, COMMUNICATION METHOD, WIRELESS RESOURCE ALLOCATION METHOD, BASE STATION SELECTION METHOD, AND READABLE MEDIUM |
BR112018068361A BR112018068361A2 (pt) | 2016-03-23 | 2017-02-22 | nó núcleo, estação base, terminal de rádio, método de comunicação, método de alocação de recursos de rádio, método de seleção de estação base e meio legível |
CN201780018335.8A CN108781447B (zh) | 2016-03-23 | 2017-02-22 | 基站、用户设备和其中的方法 |
US16/520,448 US10791482B2 (en) | 2016-03-23 | 2019-07-24 | Core node, base station, radio terminal, communication method, radio resource allocation method, base station selection method, and readable medium |
US16/922,875 US11006321B2 (en) | 2016-03-23 | 2020-07-07 | Core node, base station, radio terminal, communication method, radio resource allocation method, base station selection method, and readable medium |
US17/315,140 US20210266793A1 (en) | 2016-03-23 | 2021-05-07 | Core node, base station, radio terminal, communication method, radio resource allocation method, base station selection method, and readable medium |
US17/470,974 US11310697B2 (en) | 2016-03-23 | 2021-09-09 | Core node, base station, radio terminal, communication method, radio resource allocation method, base station selection method, and readable medium |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2016-058260 | 2016-03-23 | ||
JP2016058260 | 2016-03-23 |
Related Child Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/083,577 A-371-Of-International US10405239B2 (en) | 2016-03-23 | 2017-02-22 | Core node, base station, radio terminal, communication method, radio resource allocation method, base station selection method, and readable medium |
US16/520,448 Continuation US10791482B2 (en) | 2016-03-23 | 2019-07-24 | Core node, base station, radio terminal, communication method, radio resource allocation method, base station selection method, and readable medium |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2017163735A1 true WO2017163735A1 (ja) | 2017-09-28 |
Family
ID=59899993
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2017/006644 WO2017163735A1 (ja) | 2016-03-23 | 2017-02-22 | コアノード、基地局、無線端末、通信方法、無線リソース割当方法、基地局選択方法、及び、可読媒体 |
Country Status (6)
Country | Link |
---|---|
US (5) | US10405239B2 (ja) |
EP (1) | EP3435713A4 (ja) |
JP (3) | JP6806137B2 (ja) |
CN (1) | CN108781447B (ja) |
BR (1) | BR112018068361A2 (ja) |
WO (1) | WO2017163735A1 (ja) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2019134476A (ja) * | 2016-05-26 | 2019-08-08 | 京セラ株式会社 | 基地局 |
WO2020048541A1 (en) * | 2018-09-07 | 2020-03-12 | Huawei Technologies Co., Ltd. | Shared radio bearer and management of ue radio id and ran path |
WO2020255490A1 (ja) * | 2019-06-19 | 2020-12-24 | 日本電気株式会社 | コアネットワーク装置、通信制御方法、非一時的なコンピュータ可読媒体、及び無線通信システム |
CN113330773A (zh) * | 2019-01-18 | 2021-08-31 | 上海诺基亚贝尔股份有限公司 | 用于终端设备的移动性的切片分组 |
US11533627B2 (en) | 2018-05-28 | 2022-12-20 | Mitsubishi Electric Corporation | Management device for managing a radio access network |
Families Citing this family (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3435713A4 (en) * | 2016-03-23 | 2019-10-16 | Nec Corporation | CENTER NODE, BASE STATION, WIRELESS TERMINAL, COMMUNICATION METHOD, WIRELESS RESOURCE ALLOCATION METHOD, BASE STATION SELECTION METHOD, AND READABLE MEDIUM |
CN107659419B (zh) * | 2016-07-25 | 2021-01-01 | 华为技术有限公司 | 网络切片方法和系统 |
US10749796B2 (en) | 2017-04-27 | 2020-08-18 | At&T Intellectual Property I, L.P. | Method and apparatus for selecting processing paths in a software defined network |
US10673751B2 (en) | 2017-04-27 | 2020-06-02 | At&T Intellectual Property I, L.P. | Method and apparatus for enhancing services in a software defined network |
US10819606B2 (en) | 2017-04-27 | 2020-10-27 | At&T Intellectual Property I, L.P. | Method and apparatus for selecting processing paths in a converged network |
US10257668B2 (en) | 2017-05-09 | 2019-04-09 | At&T Intellectual Property I, L.P. | Dynamic network slice-switching and handover system and method |
US10382903B2 (en) | 2017-05-09 | 2019-08-13 | At&T Intellectual Property I, L.P. | Multi-slicing orchestration system and method for service and/or content delivery |
EP3641424B1 (en) * | 2017-06-17 | 2022-05-04 | LG Electronics Inc. | Method for registering a user equipment with a network slice in a wireless communication system and user equipment therefor |
US10070344B1 (en) * | 2017-07-25 | 2018-09-04 | At&T Intellectual Property I, L.P. | Method and system for managing utilization of slices in a virtual network function environment |
US10104548B1 (en) | 2017-12-18 | 2018-10-16 | At&T Intellectual Property I, L.P. | Method and apparatus for dynamic instantiation of virtual service slices for autonomous machines |
JP2021514126A (ja) * | 2018-02-15 | 2021-06-03 | テレフオンアクチーボラゲット エルエム エリクソン(パブル) | フル構成で接続を再開するための方法、ネットワークノード、無線デバイス、およびコンピュータプログラム製品 |
WO2020114587A1 (en) * | 2018-12-05 | 2020-06-11 | Nokia Technologies Oy | Apparatus, method, and computer program |
CN114126010A (zh) * | 2020-09-01 | 2022-03-01 | 中国电信股份有限公司 | 接入网络切片的控制方法、装置和系统 |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2014045390A (ja) * | 2012-08-27 | 2014-03-13 | National Institute Of Information & Communication Technology | モバイルネットワーク |
WO2015002087A1 (ja) * | 2013-07-02 | 2015-01-08 | 株式会社Nttドコモ | 基地局、ユーザ装置、リソース割り当て方法、及びリソース決定方法 |
Family Cites Families (32)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102207875B (zh) * | 2010-03-30 | 2014-11-12 | 鸿富锦精密工业(深圳)有限公司 | 媒体数据播放装置及其重新启动方法 |
US10368340B2 (en) * | 2010-04-01 | 2019-07-30 | Hon Hai Precision Industry Co., Ltd. | Network service exposure method and apparatus utilizing the same |
US9949189B2 (en) * | 2011-07-11 | 2018-04-17 | Interdigital Patent Holdings, Inc. | Systems and methods for establishing and maintaining multiple cellular connections and/or interfaces |
CN104025652A (zh) * | 2011-11-04 | 2014-09-03 | 高通股份有限公司 | 用于在e-utran中更新ue能力的方法和装置 |
US20150043532A1 (en) * | 2012-03-16 | 2015-02-12 | Kyocera Corporation | Communication control method, base station, home base station, and gateway device |
CN103293780B (zh) | 2012-08-10 | 2016-12-21 | 上海天马微电子有限公司 | 触控液晶显示装置 |
KR101944099B1 (ko) | 2012-12-06 | 2019-04-17 | 한국전자통신연구원 | 셀룰러 이동통신 시스템에서 디바이스간 직접통신을 위한 디스커버리 방법 및 장치 |
GB2510345A (en) * | 2013-01-30 | 2014-08-06 | Nec Corp | Sharing base station resources among plural network operators |
GB2512900A (en) * | 2013-04-10 | 2014-10-15 | Nec Corp | Communication system |
WO2014205786A1 (zh) * | 2013-06-28 | 2014-12-31 | 华为技术有限公司 | 任播服务注册、实现方法及装置、交换设备和系统 |
EP3078236A1 (en) * | 2013-12-06 | 2016-10-12 | Interdigital Patent Holdings, Inc. | Layered connectivity in wireless systems |
EP3141047B1 (en) * | 2014-05-08 | 2020-09-02 | Intel IP Corporation | User equipment and methods to indicate power saving mode configuration to ran nodes |
CN104639653B (zh) * | 2015-03-05 | 2019-04-09 | 北京掌中经纬技术有限公司 | 基于云架构的自适应方法及系统 |
US9775045B2 (en) * | 2015-09-11 | 2017-09-26 | Intel IP Corporation | Slicing architecture for wireless communication |
EP3367730B1 (en) * | 2015-11-10 | 2021-08-25 | Huawei Technologies Co., Ltd. | Method of selecting service network, network equipment and management equipment |
EP3378270B1 (en) * | 2015-11-18 | 2020-06-03 | Telefonaktiebolaget LM Ericsson (PUBL) | Radio network node, network node and methods performed therein |
WO2017086847A1 (en) * | 2015-11-18 | 2017-05-26 | Telefonaktiebolaget Lm Ericsson (Publ) | First network node, receiving network node and methods performed therein |
WO2017086846A1 (en) * | 2015-11-18 | 2017-05-26 | Telefonaktiebolaget Lm Ericsson (Publ) | Network node, radio network node and methods performed therein |
US10772101B2 (en) * | 2015-12-08 | 2020-09-08 | Huawei Technologies Co., Ltd. | Systems and methods for determining air interface configuration |
US10536946B2 (en) * | 2015-12-08 | 2020-01-14 | Huawei Technologies Co., Ltd. | Method and system for performing network slicing in a radio access network |
CN108432323B (zh) * | 2016-01-08 | 2023-04-18 | 瑞典爱立信有限公司 | 无线电网络节点和其中执行的方法 |
US10512109B2 (en) * | 2016-01-15 | 2019-12-17 | Telefonaktiebolaget Lm Ericsson (Publ) | Transmitting communication device, receiving communication device and methods performed thereby |
WO2017140340A1 (en) * | 2016-02-15 | 2017-08-24 | Telefonaktiebolaget Lm Ericsson (Publ) | Network nodes and methods performed therein for enabling communication in a communication network |
EP3417656B1 (en) * | 2016-02-15 | 2020-11-04 | Telefonaktiebolaget LM Ericsson (PUBL) | Network nodes and methods performed therein for enabling communication in a communication network |
WO2017140375A1 (en) * | 2016-02-19 | 2017-08-24 | Huawei Technologies Co., Ltd. | Function selection in mobile networks |
EP3416425B1 (en) * | 2016-02-29 | 2021-07-14 | Huawei Technologies Co., Ltd. | Method, apparatus and wireless communication system for determining control plane node |
WO2017161484A1 (zh) * | 2016-03-21 | 2017-09-28 | 华为技术有限公司 | 一种消息交互的方法、设备和系统 |
EP3435713A4 (en) | 2016-03-23 | 2019-10-16 | Nec Corporation | CENTER NODE, BASE STATION, WIRELESS TERMINAL, COMMUNICATION METHOD, WIRELESS RESOURCE ALLOCATION METHOD, BASE STATION SELECTION METHOD, AND READABLE MEDIUM |
EP3490299B1 (en) * | 2016-08-02 | 2021-04-28 | LG Electronics Inc. | Connection try method and user equipment, and connection control method and base station |
US20180288676A1 (en) * | 2017-04-02 | 2018-10-04 | Chia-Hung Wei | Access control in new radio |
JP7303740B2 (ja) * | 2017-06-23 | 2023-07-05 | エルジー エレクトロニクス インコーポレイティド | アクセス禁止チェックを実行する方法及び装置 |
US11076344B1 (en) * | 2020-01-20 | 2021-07-27 | PanPsy Technologies, LLC | Wireless device and wireless network processes for access control |
-
2017
- 2017-02-22 EP EP17769781.0A patent/EP3435713A4/en active Pending
- 2017-02-22 US US16/083,577 patent/US10405239B2/en active Active
- 2017-02-22 JP JP2018507150A patent/JP6806137B2/ja active Active
- 2017-02-22 CN CN201780018335.8A patent/CN108781447B/zh active Active
- 2017-02-22 WO PCT/JP2017/006644 patent/WO2017163735A1/ja active Application Filing
- 2017-02-22 BR BR112018068361A patent/BR112018068361A2/pt not_active Application Discontinuation
-
2019
- 2019-07-24 US US16/520,448 patent/US10791482B2/en active Active
-
2020
- 2020-07-07 US US16/922,875 patent/US11006321B2/en active Active
- 2020-11-27 JP JP2020196741A patent/JP7180663B2/ja active Active
-
2021
- 2021-05-07 US US17/315,140 patent/US20210266793A1/en active Pending
- 2021-09-09 US US17/470,974 patent/US11310697B2/en active Active
-
2022
- 2022-11-15 JP JP2022182199A patent/JP2023012554A/ja active Pending
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2014045390A (ja) * | 2012-08-27 | 2014-03-13 | National Institute Of Information & Communication Technology | モバイルネットワーク |
WO2015002087A1 (ja) * | 2013-07-02 | 2015-01-08 | 株式会社Nttドコモ | 基地局、ユーザ装置、リソース割り当て方法、及びリソース決定方法 |
Non-Patent Citations (3)
Title |
---|
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on New Radio Access Technology; Radio Access Architecture and Interfaces (Release 14)", 3GPP TR 38.801, 8 December 2016 (2016-12-08), pages 1 - 12, XP051229946, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Specs/archive/38_series/38.801/38801-100.zip> [retrieved on 20170421] * |
"Use Case on SMARTER Device Profile", 3GPP TSG-SA WG1 MEETING #71 S1-152399, 24 August 2015 (2015-08-24), XP050994521, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG1_Serv/TSGS1_71_Belgrade/Docs/S1-152399.zip> [retrieved on 20170420] * |
NGMN ALLIANCE: "NGMN Alliance , Liaison on NGMN 5G White Paper", 3GPP TSG RAN MEETING #68 RP-150542, 5 May 2015 (2015-05-05), pages 46 - 48, XP050967115, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/TSG_RAN/TSGR_68/Docs/RP-150542.zip> [retrieved on 20170421] * |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2019134476A (ja) * | 2016-05-26 | 2019-08-08 | 京セラ株式会社 | 基地局 |
US11533627B2 (en) | 2018-05-28 | 2022-12-20 | Mitsubishi Electric Corporation | Management device for managing a radio access network |
WO2020048541A1 (en) * | 2018-09-07 | 2020-03-12 | Huawei Technologies Co., Ltd. | Shared radio bearer and management of ue radio id and ran path |
US11758408B2 (en) | 2018-09-07 | 2023-09-12 | Huawei Technologies Co., Ltd. | Shared radio bearer and management of UE radio ID and ran path |
CN113330773A (zh) * | 2019-01-18 | 2021-08-31 | 上海诺基亚贝尔股份有限公司 | 用于终端设备的移动性的切片分组 |
CN113330773B (zh) * | 2019-01-18 | 2024-06-11 | 上海诺基亚贝尔股份有限公司 | 用于终端设备的移动性的切片分组 |
WO2020255490A1 (ja) * | 2019-06-19 | 2020-12-24 | 日本電気株式会社 | コアネットワーク装置、通信制御方法、非一時的なコンピュータ可読媒体、及び無線通信システム |
JPWO2020255490A1 (ja) * | 2019-06-19 | 2020-12-24 |
Also Published As
Publication number | Publication date |
---|---|
US20210410012A1 (en) | 2021-12-30 |
US20190053102A1 (en) | 2019-02-14 |
JP2021044836A (ja) | 2021-03-18 |
JP6806137B2 (ja) | 2021-01-06 |
CN108781447A (zh) | 2018-11-09 |
US10405239B2 (en) | 2019-09-03 |
US20210266793A1 (en) | 2021-08-26 |
US11006321B2 (en) | 2021-05-11 |
EP3435713A1 (en) | 2019-01-30 |
JP7180663B2 (ja) | 2022-11-30 |
US20190349814A1 (en) | 2019-11-14 |
JP2023012554A (ja) | 2023-01-25 |
JPWO2017163735A1 (ja) | 2019-02-07 |
EP3435713A4 (en) | 2019-10-16 |
US11310697B2 (en) | 2022-04-19 |
US20200336943A1 (en) | 2020-10-22 |
US10791482B2 (en) | 2020-09-29 |
BR112018068361A2 (pt) | 2019-01-15 |
CN108781447B (zh) | 2022-09-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP7180663B2 (ja) | 基地局及び基地局の通信方法 | |
US11606825B2 (en) | Radio base station, edge server, and methods therein | |
JP6610656B2 (ja) | 近接サービス通信のための装置及び方法 | |
US10897784B2 (en) | Apparatus and method for wireless communication, and non-transitory computer readable medium storing program | |
US11115886B2 (en) | Method for obtaining radio capability information of terminal, core network entity, base station, and terminal | |
US20180049259A1 (en) | Apparatus and method for proximity-based service communication | |
US20150359026A1 (en) | Radio communication system, radio access network node, communication device, and core network node | |
US11071119B2 (en) | Apparatus for controlling device-to-device communication, base station, radio terminal, and method therefor | |
US20220353659A1 (en) | Mobile communication system, mme, terminals and method for communication | |
EP3525532B1 (en) | Control device, paging method, and non-transitory computer-readable medium | |
JPWO2016142973A1 (ja) | 近接サービス通信のための装置及び方法 | |
EP3167669B1 (en) | Apparatuses and methods to introduce flexible support for services | |
JP6973540B2 (ja) | 通信方法、通信システム、及び移動管理装置 | |
US20180098340A1 (en) | Base station, wireless terminal, and control method of base station | |
WO2017149574A1 (ja) | コアノード、無線端末、通信方法、及び、非一時的なコンピュータ可読媒体 | |
JPWO2016152096A1 (ja) | ネットワーク装置、基地局、通信方法、無線リソース制御方法及びプログラム |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 2018507150 Country of ref document: JP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112018068361 Country of ref document: BR |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2017769781 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2017769781 Country of ref document: EP Effective date: 20181023 |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 17769781 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 112018068361 Country of ref document: BR Kind code of ref document: A2 Effective date: 20180911 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 518400072 Country of ref document: SA |