COMMUNICATION CONTROL METHOD, USER EQUIPMENT, CHIP SET, PROGRAM, NETWORK DEVICE, AND MOBILE COMMUNICATION SYSTEM

Abstract

This user device has a step in which network slice limit information relating to a network slice provided with a limit condition is received from a base station or a core network device. The limit condition is a condition limiting the use of the network slice. The network slice limit information includes an identifier which identifies the network slice and information indicating the limit condition.

Description

[Technical field]

[0001] The present disclosure relates to a communication control method and a user device for use in a mobile communication system. [Background technology]

[0002] Network slicing is defined in the standards of the Third Generation Partnership Project (3GPP), which is a standardization project for mobile communication systems (see, for example, Non-Patent Document 1).

[0003] For example, a network slice can be constructed for each service type such as eMBB (enhanced Mobile Broadband: high speed and large capacity). This enables the network to provide users with a network slice that matches each service, for example. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS 38.300 V16.1.0 Summary of the Invention

[0005] A communication control method according to an embodiment includes a step in which a user equipment receives, from a base station or a core network device, network slice restriction information relating to a network slice on which a restriction condition is set. The restriction condition is a condition for restricting use of the network slice. The network slice restriction information includes an identifier for identifying the network slice and information indicating the restriction condition. [Brief description of the drawings]

[0006] [Figure 1] 1 is a diagram showing a configuration of a mobile communication system according to an embodiment; [Diagram 2] FIG. 1 is a diagram illustrating a configuration of a UE (user equipment) according to an embodiment. [Diagram 3] A diagram showing the configuration of a gNB (base station) according to one embodiment. [Figure 4] A diagram showing the configuration of an AMF (core network device) according to one embodiment. [Diagram 5] A diagram showing the configuration of a protocol stack of a wireless interface of a user plane that handles data. [Figure 6] FIG. 2 is a diagram showing the configuration of a protocol stack of a radio interface of a control plane that handles signaling (control signals). [Figure 7] FIG. 1 illustrates network slicing according to one embodiment. [Figure 8] FIG. 13 is a diagram illustrating a registration procedure according to one embodiment. [Figure 9] A diagram showing a PDU session establishment procedure according to one embodiment. [Figure 10] A diagram showing a de-registration procedure according to one embodiment. [Figure 11] FIG. 13 illustrates an NG Setup procedure according to one embodiment. [Figure 12] FIG. 1 illustrates a RAN Configuration Update procedure according to an embodiment. [Figure 13] A diagram showing an AMF Configuration Update procedure according to one embodiment. [Figure 14] FIG. 1 illustrates an Initial Context Setup procedure according to one embodiment. [Figure 15] A diagram showing a PDU Session Resource Setup procedure according to one embodiment. [Figure 16] A diagram showing a PDU Session Resource Modify procedure according to one embodiment. [Figure 17] A diagram showing a PDU Session Resource Release procedure according to one embodiment. [Figure 18] FIG. 1 is a diagram illustrating an operation example 1 according to an embodiment. [Figure 19] FIG. 11 is a diagram illustrating an operation example 2 according to an embodiment. [Figure 20] FIG. 11 is a diagram illustrating an operation example 3 according to an embodiment. [Figure 21] FIG. 11 is a diagram illustrating an operation example 4 according to an embodiment. [Figure 22] FIG. 11 is a diagram illustrating an operation example 5 according to an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0007] A base station or a core network device may determine restrictive conditions for a network slice, which may prevent a user equipment from using such a network slice.

[0008] Therefore, the present disclosure aims to appropriately use network slices for which restriction conditions are determined.

[0009] A mobile communication system according to an embodiment will be described with reference to the drawings. In the description of the drawings, the same or similar parts are denoted by the same or similar reference numerals.

[0010] (Configuration of a mobile communication system) First, a configuration of a mobile communication system according to an embodiment will be described with reference to Fig. 1 to Fig. 6. Fig. 1 is a diagram showing a configuration of a mobile communication system according to an embodiment. A mobile communication system 1 complies with the 3GPP standard 5th Generation System (5GS). In the following description, 5GS is taken as an example, but a Long Term Evolution (LTE) system may be applied at least in part to the mobile communication system. Also, a sixth generation (6G) system may be applied at least in part to the mobile communication system.

[0011] The mobile communication system 1 includes a user equipment (UE) 100, a 5G radio access network (NG-RAN) 10, and a 5G core network (5GC) 20.

[0012] The UE 100 is a mobile wireless communication device. The UE 100 may be any device that is used by a user. For example, the UE 100 is a mobile phone terminal (including a smartphone), a tablet terminal, a notebook PC, a communication module (including a communication card or a chipset), a sensor or a device provided in a sensor, a vehicle or a device provided in a vehicle (Vehicle UE), or an aircraft or a device provided in an aircraft (Aerial UE).

[0013] The NG-RAN 10 includes a base station (called "gNB" in the 5G system) 200. The gNBs 200 are connected to each other via an Xn interface, which is an interface between base stations. The gNBs 200 manage one or more cells. The gNBs 200 perform wireless communication with the UEs 100 that have established a connection with their own cell. The gNBs 200 have a radio resource management (RRM) function, a routing function for user data (hereinafter simply referred to as "data"), a measurement control function for mobility control and scheduling, and the like. A "cell" is used as a term indicating the smallest unit of a wireless communication area. A "cell" is also used as a term indicating a function or resource for performing wireless communication with the UEs 100. One cell belongs to one carrier frequency. An XnAP (Application Protocol) message is transmitted and received between the gNBs 200 over the Xn interface.

[0014] In addition, the gNB can also be connected to the EPC (Evolved Packet Core), which is the core network of LTE. The LTE base station (i.e., "eNB") can also be connected to the 5GC. The LTE base station and the gNB can also be connected via an inter-base station interface. The LTE base station connected to the 5GC 20 is sometimes called an ng-eNB. In the following, "gNB" may be read as "ng-eNB" or "eNB".

[0015] The 5GC20 includes an Access and Mobility Management Function (AMF) 300 and a User Plane Function (UPF) 400. The AMF 300 performs various mobility controls for the UE 100. The AMF 300 manages the mobility of the UE 100 by communicating with the UE 100 using Non-Access Stratum (NAS) signaling. The UPF 400 performs data forwarding control. The AMF 300 and the UPF 400 are connected to the gNB 200 via an NG interface, which is an interface between a base station and a core network. Specifically, the gNB 200 is connected to the AMF 300 via an NG-C interface, and is connected to the UPF 400 via an NG-U interface. An NGAP (Application Protocol) message is transmitted and received between the gNB 200 and the AMF 300 on the NG-C interface.

[0016] 2 is a diagram showing a configuration of a UE 100 (user equipment) according to an embodiment. The UE 100 includes a receiving unit 110, a transmitting unit 120, and a control unit .

[0017] The receiving unit 110 performs various receptions under the control of the control unit 130. The receiving unit 110 includes an antenna and a receiver. The receiver converts a radio signal received by the antenna into a baseband signal (received signal) and outputs the baseband signal to the control unit 130.

[0018] The transmission unit 120 performs various transmissions under the control of the control unit 130. The transmission unit 120 includes an antenna and a transmitter. The transmitter converts a baseband signal (transmission signal) output by the control unit 130 into a radio signal and transmits it from the antenna.

[0019] The control unit 130 performs various controls and processes in the UE 100. Such processes include processes of each layer described below. The control unit 130 includes at least one processor and at least one memory. The memory stores programs executed by the processor and information used in the processes by the processor. The processor may include a baseband processor and a CPU (Central Processing Unit). The baseband processor performs modulation / demodulation and encoding / decoding of baseband signals. The CPU executes programs stored in the memory to perform various processes.

[0020] 3 is a diagram showing a configuration of a gNB 200 (base station) according to an embodiment. The gNB 200 includes a transmitter 210, a receiver 220, a controller 230, and a backhaul communication unit 240.

[0021] The transmission unit 210 performs various transmissions under the control of the control unit 230. The transmission unit 210 includes an antenna and a transmitter. The transmitter converts a baseband signal (transmission signal) output by the control unit 230 into a radio signal and transmits it from the antenna.

[0022] The receiving unit 220 performs various receptions under the control of the control unit 230. The receiving unit 220 includes an antenna and a receiver. The receiver converts a radio signal received by the antenna into a baseband signal (received signal) and outputs the baseband signal to the control unit 230.

[0023] The control unit 230 performs various controls and processes in the gNB 200. Such processes include processes of each layer described below. The control unit 230 includes at least one processor and at least one memory. The memory stores programs executed by the processor and information used in the processes by the processor. The processor may include a baseband processor and a CPU. The baseband processor performs modulation / demodulation and encoding / decoding of baseband signals. The CPU executes programs stored in the memory to perform various processes.

[0024] The backhaul communication unit 240 is connected to adjacent base stations via an inter-base station interface. The backhaul communication unit 240 is connected to the AMF / UPF 300 via a base station-core network interface. Note that the gNB is composed of a CU (Central Unit) and a DU (Distributed Unit) (i.e., the functions are divided), and both units may be connected to each other via an F1 interface.

[0025] 4 is a diagram showing a configuration of an AMF 300 (core network device) according to an embodiment. The AMF 300 includes a backhaul communication unit 310 and a control unit 320. Note that while the AMF 300 is an example of a core network device, the core network device may be the UPF 400.

[0026] The backhaul communication unit 310 is connected to the base station via a base station-core network interface.

[0027] The control unit 320 performs various controls and processes in the AMF 300. Such processes include the processes of each layer described below. The AMF 300 includes at least one processor and at least one memory. The memory stores programs executed by the processor and information used in the processes by the processor. The processor may include a CPU. The CPU executes the programs stored in the memory to perform various processes.

[0028] FIG. 5 is a diagram showing the configuration of a protocol stack of a radio interface of a user plane that handles data.

[0029] The user plane radio interface protocol includes a physical (PHY) layer, a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, and a service data adaptation protocol (SDAP) layer.

[0030] The PHY layer performs encoding / decoding, modulation / demodulation, antenna mapping / demapping, and resource mapping / demapping. Data and control information are transmitted between the PHY layer of the UE 100 and the PHY layer of the gNB 200 via a physical channel.

[0031] The MAC layer performs data priority control, retransmission processing using Hybrid Automatic Repeat reQuest (HARQ), random access procedures, etc. Data and control information are transmitted between the MAC layer of UE100 and the MAC layer of gNB200 via a transport channel. The MAC layer of gNB200 includes a scheduler. The scheduler determines the uplink and downlink transport format (transport block size, modulation and coding scheme (MCS)) and the resource blocks to be assigned to UE100.

[0032] The RLC layer transmits data to the RLC layer on the receiving side by using the functions of the MAC layer and the PHY layer. Data and control information are transmitted between the RLC layer of the UE 100 and the RLC layer of the gNB 200 via a logical channel.

[0033] The PDCP layer performs header compression / decompression, encryption / decryption, etc.

[0034] The SDAP layer maps IP flows, which are units for QoS (Quality of Service) control by the core network, to radio bearers, which are units for QoS control by the AS (Access Stratum). Note that if the RAN is connected to the EPC, the SDAP is not necessary.

[0035] FIG. 6 is a diagram showing the configuration of a protocol stack of a radio interface of a control plane that handles signaling (control signals).

[0036] The protocol stack of the radio interface of the control plane has a Radio Resource Control (RRC) layer and a Non-Access Stratum (NAS) layer instead of the SDAP layer shown in FIG.

[0037] Between the RRC layer of the UE 100 and the RRC layer of the gNB 200, RRC signaling for various settings is transmitted. The RRC layer controls logical channels, transport channels, and physical channels according to the establishment, re-establishment, and release of radio bearers. When there is a connection (RRC connection) between the RRC of the UE 100 and the RRC of the gNB 200, the UE 100 is in an RRC connected state. When there is no connection (RRC connection) between the RRC of the UE 100 and the RRC of the gNB 200, the UE 100 is in an RRC idle state. When the connection between the RRC of the UE 100 and the RRC of the gNB 200 is suspended, the UE 100 is in an RRC inactive state.

[0038] The NAS layer, which is located above the RRC layer, performs session management, mobility management, and the like. NAS signaling (NAS messages) are transmitted between the NAS layer of the UE 100 and the NAS layer of the AMF 300. Note that NAS messages related to session management may be transferred to a Session Management Function (SMF) via the AMF 300. That is, the UE 100 and the SMF transmit and receive NAS messages related to session management via the AMF 300. The SMF is a core network device that performs session management, and is connected to the AMF 300.

[0039] In addition, the UE 100 has an application layer and the like in addition to the protocol of the radio interface.

[0040] (Network Slicing Overview) Next, we will provide an overview of network slicing. Network slicing introduces a technology that creates multiple virtual networks by virtually dividing a physical network built by a carrier (for example, a network consisting of NG-RAN10 and 5GC20). Each virtual network is called a network slice. In what follows, a "network slice" may be simply called a "slice."

[0041] Network slicing allows telecommunications operators to create virtual network slices according to the service requirements of different service types, such as eMBB, URLLC (Ultra-Reliable and Low Latency Communications), and mMTC (massive Machine Type Communications), thereby optimizing network resources.

[0042] A slice is defined in a PLMN (Public Land Mobile Network). One slice includes a RAN part and a CN (Core Network) part. One slice corresponds to one PDU session.

[0043] 7 is a diagram showing network slicing according to an embodiment. As shown in the figure, three slices (slice #1 to slice #3) are created on a network 50 including an NG-RAN 10 and a 5GC 20. Slice #1 is associated with a service type called eMBB, slice #2 is associated with a service type called URLLC, and slice #3 is associated with a service type called mMTC. Note that three or more slices may be created on the network 50. One service type may be associated with multiple slices.

[0044] Each slice is provided with a slice identifier for identifying the slice. An example of a slice identifier is S-NSSAI (Single Network Slicing Selection Assistance Information). S-NSSAI includes 8-bit SST (slice / service type). S-NSSAI may further include 24-bit SD (slice differentiator). SST is information indicating a service type to which a slice is associated. SD is information for differentiating multiple slices associated with the same service type. Information including multiple S-NSSAI is called NSSAI (Network Slice Selection Assistance Information).

[0045] Also, a slice group may be created by grouping a plurality of slices. Each slice group may be provided with a slice group identifier for identifying the slice group. Note that a slice group is different from an NSSAI. The slice group identifier does not include the slice identifier of each slice belonging to the slice group.

[0046] Each gNB 200 belonging to NG-RAN 10 can support multiple slices. The gNB 200 may notify the UE 100 of the slice identifier of each slice it supports by a broadcast RRC message (e.g., SIB (System Information Block) 1) or an individual RRC message (e.g., RRCRelease message). The gNB 200 may notify the AMF 300 of the slice identifier of each slice it supports by an NGAP message. The gNB 200 may notify neighboring gNBs 200 of the slice identifier of each slice it supports by an XnAP message.

[0047] Each gNB 200 can support multiple slice groups. The gNB 200 may notify the UE 100 of the slice group identifier of each slice group that it supports by a broadcast RRC message (e.g., SIB1) or an individual RRC message (e.g., RRCRelease message). The gNB 200 may notify the AMF 300 of the slice group identifier of each slice group that it supports by an NGAP message. The gNB 200 may notify neighboring gNBs 200 of the slice group identifier of each slice group that it supports by an XnAP message.

[0048] Each AMF 300 belonging to 5GC 20 can support multiple slices. The AMF 300 may notify the gNB 200 of the slice identifier of each slice that it supports in an NGAP message.

[0049] Each AMF 300 can support multiple slice groups. The AMF 300 allocates slices for each slice group that it supports. group The identifier may be notified to gNB200 in an NGAP message.

[0050] Next, the NAS procedures for communication using slices will be described.

[0051] (1)Registration Procedure The Registration procedure is a procedure for the UE 100 to perform initial registration with the network 50. For example, a Tracking Area (TA) and a Registration Area (RA) are set in the UE 100 from the AMF 300 in this procedure. Fig. 8 is a diagram showing the Registration procedure.

[0052] As shown in FIG. 8, in step Sa1, UE 100 transmits a NAS message called a REGISTRATION REQUEST message to AMF 300. In step Sa2, AMF 300 transmits a NAS message called a REGISTRATION ACCEPT message to UE 100. Here, the REGISTRATION REQUEST message may include an information element (IE) called "Requested NSSAI". The "Requested NSSAI" is an NSSAI (i.e., one or more slices) that UE 100 wishes to register. The REGISTRATION ACCEPT message may include an IE called "allowed NSSAI" and an IE called "Configured NSSAI". The "Configured NSSAI" is an NSSAI configured in UE 100 by each PLMN. Note that the "allowed NSSAI" and "Configured NSSAI" may be updated by a NAS message called a CONFIGURATION UPDATE COMMAND message transmitted from AMF 300 to UE 100.

[0053] (2) PDU session establishment procedure The PDU session establishment procedure is a procedure for establishing a PDU session. FIG. 9 is a diagram showing the PDU session establishment procedure. As shown in FIG. 9, in step Sb1, the UE 100 transmits a NAS message called PDU SESSION ESTABLISHMENT REQUEST to the AMF 300. In step Sb2, the AMF 300 transmits a NAS message called a PDU SESSION ESTABLISHMENT ACCEPT message to the UE 100. Here, the PDU SESSION ESTABLISHMENT REQUEST message includes an identifier of a PDU session that the UE 100 wants to establish. The PDU SESSION ESTABLISHMENT REQUEST message may include a slice (S-NSSAI) that the UE 100 desires for the PDU session. The PDU SESSION ESTABLISHMENT ACCEPT message may include a slice (a slice determined by the AMF 300) associated with the PDU session requested by the UE 100.

[0054] (3) Deregistration Procedure The de-registration procedure is a procedure for AMF 300 to notify UE 100 that registration with network 50 has been cancelled. Fig. 10 is a diagram showing the de-registration procedure. As shown in Fig. 10, in step Sc1, AMF 300 transmits a NAS message called a DEREGISTRATION REQUEST message to UE 100. In step Sc2, UE 100 transmits a NAS message called a DEREGISTRATION ACCEPT message to AMF 300.

[0055] (NGAP Procedures for Slice-Based Communications) Next, the NGAP procedure for communications using slices is described.

[0056] (1) NG Setup Procedure The NG Setup procedure is a procedure for exchanging application level configuration data necessary to enable the gNB200 and AMF300 to interoperate correctly over the NG-C interface.

[0057] FIG. 11 is a diagram showing an NG Setup procedure. As shown in FIG. 11, in step Sd1, the gNB 200 transmits an NGAP message called an NG SETUP REQUEST message including application level configuration data determined by the gNB 200 to the AMF 300. In step Sd2, the AMF 300 transmits an NGAP message called an NG SETUP RESPONSE message including application level configuration data determined by the gNB 200. Here, the NG SETUP REQUEST message may include a list of slices (List of supported S-NSSAI(s)) supported by the gNB 200. This list may be a list for each TA. Also, this list may be a list for each PLMN. The NG SETUP RESPONSE message may include a list of slices (List of supported S-NSSAI(s)) supported by the AFM 300. This list may be a list for each TA. Also, this list may be a list for each PLMN.

[0058] (2) RAN Configuration Update Procedure The RAN Configuration Update procedure is a procedure for updating application-level configuration data by the gNB200.

[0059] Figure 12 is a diagram showing a RAN Configuration Update procedure. As shown in Figure 12, in step Se1, the gNB 200 transmits an NGAP message called a RAN CONFIGURATION UPDATE message to the AMF 300, the NGAP message including application-level configuration data updated by the gNB 200. In step Se2, the AMF 300 transmits an NGAP message called a RAN CONFIGURATION UPDATE ACKNOWLEDGE message to the gNB 200, the NGAP message confirming that the configuration data has been successfully updated. Here, the RAN CONFIGURATION UPDATE message may include a list of slices (List of supported S-NSSAI(s)) supported by the gNB 200.

[0060] (3) AMF Configuration Update Procedure The AMF Configuration Update procedure is a procedure for updating application-level configuration data by the AMF 300.

[0061] Figure 13 is a diagram showing the AMF Configuration Update procedure. As shown in Figure 13, in step Sf1, AMF300 transmits an NGAP message called an AMF CONFIGURATION UPDATE message to gNB200, which includes application-level configuration data updated by AMF300. In step Sf2, gNB200 transmits an NGAP message called an AMF CONFIGURATION UPDATE ACKNOWLEDGE message to AMF300, which confirms that the configuration data has been successfully updated. Here, the AMF CONFIGURATION UPDATE message may include a list of slices supported by AMF300 (List of supported S-NSSAI(s)).

[0062] (4) Initial Context Setup Procedure The Initial Context Setup procedure is a procedure for establishing an initial UE context for a particular UE 100 in the gNB 200. Such an initial UE context includes, for example, a PDU session context, a security key, a mobility restriction list, UE radio capabilities, and UE security capabilities.

[0063] FIG. 14 is a diagram showing the Initial Context Setup procedure. As shown in FIG. 14, in step Sg1, the AFM 300 transmits an NGAP message called an INITIAL CONTEXT SETUP REQUEST message to the gNB 200. In step Sg2, the gNB 200 transmits an NGAP message called an INITIAL CONTEXT SETUP RESPONSE message to the AMF 300. Here, the INITIAL CONTEXT SETUP REQUEST message may include "Allowed NSSAI". The "Allowed NSSAI" indicates one or more slices that the UE 100 can use in the serving PLMN for the current RA (Registration Area). The INITIAL CONTEXT SETU P The REQUEST message may include a set of a PDU session identifier and a slice identifier of a slice associated with the PDU session.

[0064] (5) PDU Session Resource Setup Procedure The PDU Session Resource Setup procedure is a procedure for allocating resources (PDU Session Resources) on the Uu and NG-U interfaces for one or more PDU sessions for a specific UE 100. The PDU Session Resource Setup procedure may be initiated in response to the aforementioned PDU Session Establish procedure.

[0065] Figure 15 is a diagram showing a PDU Session Resource Setup procedure. As shown in Figure 15, in step Sh1, the AMF 300 transmits an NGAP message called a PDU SESSION RESOURCE SETUP REQUEST message to the gNB 200. In step Sh2, the gNB 200 transmits an NGAP message called a PDU SESSION RESOURCE SETUP RESPONSE message to the AMF 300. Here, the PDU SESSION RESOURCE SETUP REQUEST message includes a set of a PDU session identifier and a slice identifier of a slice associated with the PDU session.

[0066] (6) PDU Session Resource Modify Procedure The PDU Session Resource Modify procedure is a procedure that allows for configuration modification of one or more already established PDU sessions for a particular UE 100.

[0067] Figure 16 is a diagram showing a PDU Session Resource Modify procedure. As shown in Figure 16, in step Si1, the AMF 300 transmits an NGAP message called a PDU SESSION RESOURCE MODIFY REQUEST message to the gNB 200. In step Si2, the gNB 200 transmits an NGAP message called a PDU SESSION RESOURCE MODIFY RESPONSE message to the AMF 300. Here, the PDU SESSION RESOURCE MODIFY REQUEST message includes a set of a PDU session identifier and a slice identifier of a slice associated with the PDU session.

[0068] (7) PDU Session Resource Release Procedure The PDU Session Resource Release procedure is a procedure for releasing resources of an already established PDU session for a particular UE 100.

[0069] FIG. 17 is a diagram showing a PDU Session Resource Release procedure. As shown in FIG. 17, in step Sj1, the AMF 300 transmits an NGAP message called a PDU SESSION RESOURCE RELEASE COMMAND message to the gNB 200. In step Sj2, the AMF 300 transmits a PDU SESSION RESOURCE RELEASE COMMAND message to the gNB 200. S An NGAP message called a PONSE message is sent to AMF300.

[0070] (About slice restrictions) Next, slice restrictions will be described.

[0071] In one embodiment, the AMF 300 or the gNB 200 may restrict at least one slice among slices that it supports. Restricting a slice means determining a restriction condition that is a condition for restricting the use of the slice. Hereinafter, a slice for which a restriction condition is determined may be referred to as a "restricted slice."

[0072] The restriction condition includes at least one of (1) a time condition, (2) a UE location condition, (3) a UE group condition, and (4) a RAN condition.

[0073] The restriction condition determined for one slice may be one of the above-mentioned conditions (1) to (4). The restriction condition may also be a combination of two or more of the conditions (1) to (4). The combined conditions may be a condition combined with "AND". The combined conditions may also be a condition combined with "OR". A condition combining two or more conditions with "AND" is a condition that all of the two or more conditions should be satisfied. A condition combining two or more conditions with "OR" is a condition that any one of the two or more conditions should be satisfied.

[0074] Next, the above-mentioned (1) time condition, (2) UE location condition, (3) UE group condition, and (4) RAN condition will be described in detail.

[0075] (1) Time conditions The time condition is a condition that specifies a time period or period during which the use of a slice is restricted. As an example, when the resources of a certain slice are exhausted, the AMF 300 (or the gNB 200) determines a certain period (e.g., 3 hours) as the time condition for the slice. As another example, the AMF 300 (or the gNB 200) predicts a time period during which resources are likely to be exhausted for a certain slice based on the history of the traffic situation of the slice, and determines the predicted time period (e.g., 18:00 to 22:00) as the time condition.

[0076] (2)UE location conditions The UE location condition is a condition that specifies a geographical location of the UE 100 that restricts the use of slices. The use of slices is restricted for the UE 100 that is located in the geographical location specified by the UE location condition. The UE location condition specifies at least one of a longitude range, a latitude range, and an altitude range as the geographical location.

[0077] For example, gNB200 determines the UE location condition based on the geographic coverage range of the cell managed by the gNB200.

[0078] (3) UE group conditions The UE group condition specifies a UE group for which the use of slices is restricted. The use of slices is restricted for UEs 100 that belong to a UE group specified by the UE group condition. Here, the UE group is specified by an RNA (Ran Notification Area), a TA (Tracking Area), an RA (Registration Area), a group identifier, or multiple UE identifiers. The UE group specified by an RNA is a group consisting of all UEs 100 for which the RNA is set. 。T The UE group specified by A is a group consisting of all UEs 100 for which the TA is set. The UE group specified by RA is a group consisting of all UEs 100 for which the RA is set. Note that the UE group may be configured with only one UE 100. The UE group condition may specify a single UE 100 (UE identifier of UE 100) for which the use of a slice is restricted.

[0079] The RNA is an area for the gNB 200 to page the UE 100 in the RRC inactive state. The RNA is composed of one or more cells. The RNA is part of the TA. The RNA is set from the gNB 200 to the UE 100.

[0080] The TA is an area for the AMF 300 to page the UE 100 in the RRC idle state. The TA is configured with a plurality of cells. The TA is set to the UE 100 by the AMF 300.

[0081] The RA is an area managed for each access type (3GPP access or non-3GPP access). The RA is composed of multiple TAs. The RA is set in the UE 100 by the AMF 300.

[0082] The group identifier is an identifier for identifying a group made up of a plurality of UEs 100. The group identifier is, for example, a Temporary Mobile Group Identity (TMGI) for identifying a group made up of UEs 100 that perform group communication such as a Multicast Broadcast Service (MBS).

[0083] (4)RAN conditions The RAN condition is a condition that specifies a carrier frequency or a radio access technology (RAT) that restricts the use of the slice. For example, if a certain carrier frequency is congested, the gNB 200 restricts the use of the slice via the carrier frequency.

[0084] In one embodiment, the AMF 300 determines a restriction condition, which is a condition for restricting the use of a network slice. The AMF 300 transmits network slice restriction information regarding the network slice to the UE 100 or the gNB 200. The network slice restriction information includes a network slice identifier that identifies the network slice and condition information that indicates the restriction condition. This allows the UE 100 or the gNB 200 to grasp the restriction condition regarding the network slice. Therefore, the UE 100 can appropriately determine whether or not to use the network slice, and can suppress unnecessary access to an unavailable network slice. In addition, the gNB 200 can notify the UE 100 of the restriction condition.

[0085] In one embodiment, the gNB 200 determines a restriction condition, which is a condition for restricting the use of the network slice. The gNB 200 transmits restriction information regarding the restricted network slice to the AMF 300, another gNB 200, or the UE 100. This allows the AMF 300, another gNB 200, or the UE 100 to know the restriction condition regarding the network slice.

[0086] In one embodiment, the UE 100 receives network slice restriction information regarding a network slice in which a restriction condition is set from the gNB 200 or the AMF 300. The network slice restriction information includes an identifier for identifying the network slice and information indicating the restriction condition. This allows the UE 100 to appropriately determine whether to avoid using the network slice.

[0087] (Example 1) Next, a first operational example according to an embodiment will be described.

[0088] Fig. 18 is a diagram showing an operation example 1. As shown in Fig. 18, in step S101, the AMF 300 determines a restriction condition for at least one slice supported by the AMF 300. In the following, the slice for which the restriction condition is determined may be referred to as a "restriction slice."

[0089] In step S102, the AMF 300 transmits the network slice restriction information to the gNB 200. The gNB 200 receives the network slice restriction information from the AMF 300. Note that, hereinafter, the network slice restriction information may be simply referred to as slice restriction information.

[0090] The slice restriction information includes a set of a slice identifier for identifying a restricted slice and condition information indicating a restriction condition corresponding to the restricted slice. When the AMF 300 determines the restriction condition for a plurality of slices, the slice restriction information may include a set of a slice identifier and condition information for each of the plurality of slices.

[0091] The AMF 300 may transmit slice restriction information using an NGAP message, such as the above-mentioned NG SETUP RESPONSE message, the AMF CONFIGURATION UPDATE message, etc. Such an NGAP message may also be another NGAP message defined in the 3GPP specifications (e.g., 3GPP TS 38.413 V16.1.0).

[0092] When using the NG SETUP RESPONSE message, AMF300 may send slice restriction information corresponding to the slices indicated in the List of supported S-NSSAI(s) notified from gNB200.

[0093] In step S103, the gNB 200 transmits the slice restriction information received from the AMF 300 to the UE 100. The UE 100 receives the slice restriction information from the gNB 200.

[0094] The gNB 200 transmits the slice restriction information in an RRC message. The RRC message may be a broadcast RRC message. The RRC message may also be an individual RRC message. The broadcast RRC message is, for example, an SIB (SIB1 or other SIB), a MIB (Master Information Block), etc. The individual RRC message is, for example, an RRC Reconfiguration message, an RRCRelease message, etc. The RRC Reconfiguration message is a message for modifying the RRC connection of the UE 100 in the RRC connected state. The RRCRelease message is a message for transitioning the UE 100 in the RRC connected state to an RRC idle state or an RRC inactive state.

[0095] In addition, the RRC layer of UE100 may provide the slice restriction information received from gNB200 to the NAS layer and / or application layer of UE100.

[0096] In step S104, UE 100 determines whether to avoid using a slice based on the slice restriction information received in step S103. Specifically, when a restriction condition indicated by the condition information is satisfied, UE 100 determines to avoid using a slice corresponding to the condition information. For example, when the condition information indicates a time condition as a restriction condition, UE 100 determines to avoid using a slice during a time period or period specified by the time condition. When the condition information indicates a UE location condition as a restriction condition, UE 100 determines to avoid using a slice during a time period or period specified by the UE location condition. To When the UE 100 is located, the UE 100 determines to avoid using a slice. When the condition information indicates a UE group condition as a restriction condition, the UE 100 determines to avoid using a slice when the UE 100 belongs to a UE group specified by the UE group condition. When the condition information indicates a RAN condition as a restriction condition, the UE 100 determines to avoid using a slice when the UE 100 uses a carrier frequency and / or a RAT specified by the RAN condition.

[0097] In addition, the determination of whether to avoid using a slice may be made in the RRC layer of the UE 100. In addition, the determination may be made in the NAS layer of the UE 100. For example, the NAS layer of the UE 100 may make the determination based on slice restriction information shared by the RRC layer. In this case, the determination result may be shared between the RRC layer and the NAS layer. The determination may be made in the application layer of the UE 100 or the user of the UE 100. In this case, the determination result may be shared between the RRC layer, the NAS layer, the application layer, and the user. In addition, the determination may be made in an AS (Access Stratum) layer including the RRC layer. The AS layer includes, for example, a PHY layer, a MAC layer, an RLC layer, a PDCP layer, and an RRC layer.

[0098] When the UE 100 determines to avoid using the slice (step S104: YES), the UE 100 performs control to avoid using the slice in step S105.

[0099] Next, a specific example of control in which UE 100 avoids using slice #1 will be described, taking slice #1 as an example.

[0100] First example: When UE 100 (in RRC idle / inactive state) performs cell selection or cell reselection, it lowers the priority of a cell that supports slice #1 or controls to exclude the cell from the selection candidate cells. This reduces the possibility that UE 100 selects a cell that supports slice #1, and can reduce unnecessary access to a cell for slice #1.

[0101] Second example: UE 100 (RRC connected state) does not request slice #1 when performing a registration procedure. This can reduce unnecessary signaling caused by a slice #1 request (for example, signaling in which AMF 300 rejects a registration request caused by a slice #1 request).

[0102] Third Example: When performing a PDU Session Establishment procedure, UE 100 (RRC connected state) does not request establishment of a PDU session associated with slice #1. This can reduce unnecessary signaling caused by a request for slice #1 (for example, signaling in which AMF 300 rejects a PDU establishment request caused by a request for slice #1).

[0103] In the operation example 1, when UE 100 performs control to avoid using a slice, if the restriction condition indicated by the condition information received in step S103 is no longer satisfied, UE 100 may start using the slice. For example, when UE 100 receives a time condition indicating a period of "3 hours" for slice #1 as a restriction condition, UE 100 starts a timer (timer value = 3 hours) that measures the period and performs control to avoid using slice #1. When the timer expires, UE 100 determines that the restriction condition is no longer satisfied, and starts using slice #1.

[0104] Next, a specific example in which UE 100 starts using slice #1 will be described using slice #1 as an example.

[0105] First example: UE 100 (RRC idle / inactive state) increases the priority of a cell that supports slice #1 when performing cell selection or cell reselection.

[0106] Second example: UE 100 (RRC connected state) requests slice #1 when performing a registration procedure.

[0107] Third Example: When UE 100 (RRC Connected state) performs a PDU Session Establishment procedure, it requests the establishment of a PDU session associated with slice #1.

[0108] In the first operation example, when performing control to avoid using a slice, the UE 100 may receive a notification that a restriction condition corresponding to the restricted slice is released from the gNB 200 or the AMF 300. In response to receiving such a notification, the UE 100 may start using the slice.

[0109] In operation example 1, in step S102, gNB200 may transmit slice restriction information including restriction conditions determined by gNB200 to UE100, instead of slice restriction information received from AMF300.

[0110] (Example 2) Next, an operation example 2 according to an embodiment will be described. Differences from the above operation example will be mainly described.

[0111] Fig. 19 is a diagram showing operation example 2. As shown in Fig. 19, the operations in steps S201 and S202 are similar to the operations in steps S101 and S102.

[0112] In step S203, the gNB 200 transmits shortened slice restriction information to the UE 100. Here, the "shortened slice restriction information" has a smaller amount of information than the "slice restriction information" transmitted in step S103. For example, when an upper limit is set on the amount of data that can be transmitted in the SIB1 and it is difficult to include a large amount of information in the SIB1, the gNB 200 broadcasts the SIB1 including the shortened slice restriction information instead of the slice restriction information.

[0113] The shortened slice restriction information may be a flag indicating that a restriction condition is set on at least one slice among slices supported by the gNB 200. The UE 100 that receives such shortened information can understand that a restriction condition is set on a slice supported by the gNB 200, but cannot understand what restriction condition is set on which slice. Note that "a restriction condition is set on a slice" means that the AMF 300 or the gNB 200 has determined a restriction condition for the slice.

[0114] The shortened slice restriction information may include a slice identifier of a slice on which a restriction condition is set and a flag indicating that the restriction condition is set on the slice. The UE 100 that receives such shortened information can grasp the slice on which the restriction condition is set, but cannot grasp what kind of restriction condition is set on the slice.

[0115] The reduced slice restriction information may include a slice group identifier for identifying a slice group to which a restriction condition is set, and a flag indicating that the restriction condition is set to the slice group. The UE 100 that has received such reduced slice restriction information can know the slice group to which the restriction condition is set, but cannot know what restriction condition is set to the slice group.

[0116] When UE100 receives shortened slice restriction information and finds a slice that UE100 desires among the slices supported by gNB200, UE100 must send an inquiry to gNB200 or AMF300 to obtain the restriction conditions in order to appropriately determine whether to avoid using the slice.

[0117] In step S204, the UE 100 transmits an inquiry to the gNB 200 to obtain a restriction condition. The inquiry includes information for identifying a slice that is a target of the inquiry. The number of target slices may be one, or may be two or more. The target slice may be a slice group. In step S205, the gNB 200 transmits slice restriction information to the UE 100 as a response to the inquiry. The UE 100 receives the slice restriction information from the gNB 200. The slice restriction information includes a set of a slice identifier of the slice that is a target of the inquiry and condition information indicating a restriction condition.

[0118] For the UE 100 in the RRC idle state or the RRC inactive state, the inquiry and the transmission of the response may be performed using a message during the random access procedure. This allows the UE 100 to receive the response (slice restriction information) from the gNB 200 without transitioning to the RRC connected state, and reduces power consumption due to transitioning to the RRC connected state.

[0119] For the UE 100 in the RRC idle state or the RRC inactive state, the message used to send the inquiry may be MSG1 (Message 1) or MSG3 (Message 3) in a 4-step random access procedure. Also, the message used to send the inquiry may be MSGA (Message A) in a 2-step random access procedure. Also, the message used to send the response may be MSG4 (Message 4) in a 4-step random access procedure. Also, the message used to send the response may be MSGB (Message B) in a 2-step random access procedure. MSGA is a message that combines MSG1 and MSG3. MSGB is a message that combines MSG2 and MSG4.

[0120] MSG1 is a random access preamble transmitted from UE 100 to gNB 200. MSG2 is a response to the random access preamble, and includes transmission resources of MSG3 scheduled by gNB 200. MSG3 is the first scheduled transmission in the random access procedure. MSG3 is, for example, an RRCSetupRequest message for establishing an RRC connection, an RRCResumeRequest message for recovering an RRC connection, an RRCReestablishmentRequest message for reestablishing an RRC connection, or the like. MSG3 may be a message dedicated to an inquiry for obtaining a restriction condition. MSG4 is a response to MSG3, and is, for example, an RRCSetup message for establishing an RRC connection, an RRCResume message for recovering an RRC connection, an RRCReestablishment message for reestablishing an RRC connection, or the like. MSG4 may be a message dedicated to a response to an inquiry for obtaining a restriction condition.

[0121] The transmission of the inquiry using MSG1 means that the UE 100 transmits a random access preamble associated with the slice targeted by the inquiry. Note that the association between the random access preamble and the slice may be notified to the UE 100 from the gNB 200 by the SIB1.

[0122] To transmit an inquiry using MSG3, UE 100 transmits the slice identifier of the slice that is the subject of the inquiry in MSG3.

[0123] Sending a response (slice restriction information) using MSG4 means that gNB200 sends MSG4 including the response.

[0124] For the UE 100 in the RRC connected state, the inquiry is transmitted using, for example, a UEAssistanceInformation message, and the response is transmitted using, for example, an RRCReconfiguration message.

[0125] The operations in steps S206 and S207 are similar to those in steps S104 and S105.

[0126] In the second operation example, the UE 100 in the RRC connected state may transmit an inquiry to the AMF 300 using a NAS message. The UE 100 may receive a response to the inquiry transmitted by the NAS message from the AMF 300. Here, the NAS message used to transmit the inquiry is, for example, a REGISTRATION REQUEST message, a PDU SESSION ESTABLISHMENT REQUEST message, etc. The NAS message used to transmit a response to the inquiry is, for example, a REGISTRATION ACCEPT message, a PDU SESSION ESTABLISHMENT RESPONSE message, etc.

[0127] In the second operation example, the gNB 200 may transmit the shortened slice restriction information to the UE 100 by using a unified access control (UAC) defined in the existing specifications. In the existing specifications (e.g., 3GPP TS 38.300 V16.1.0 and 3GPP TS 38.331 V16.1.0), the gNB 200 broadcasts a barring parameter associated with each access category (AC) in the SIB1 as a UAC. Here, in the existing specifications, 64 ACs, #0 to #63, are defined. Of these, #0 to #10 are defined as standard ACs, and #32 to #63 are defined as operator-defined ACs. The gNB 200 may transmit the shortened slice restriction information (e.g., a slice identifier of a restricted slice) by using the operator-defined ACs. This allows the gNB 200 to notify the UE 100 of the shortened slice restriction information without changing the existing specifications. In addition, gNB200 may transmit shortened slice restriction information using a standard AC.

[0128] (Example 3) Next, a third operation example according to an embodiment will be described. Differences from the above-mentioned operation examples will be mainly described.

[0129] Fig. 20 is a diagram showing operation example 3. As shown in Fig. 20, the operation in step S301 is similar to the operation in step S101.

[0130] In step S302, the AMF 300 transmits slice restriction information to the UE 100. The UE 100 receives the slice restriction information from the AMF 300.

[0131] The AMF 300 may transmit the slice restriction information using a NAS message, such as the above-mentioned REGISTRATION ACCEPT message, CONFIGURATION UPDATE COMMAND message, DE-REGISTRATION REQUEST message, etc. Such a NAS message may also be any other NAS message defined in the 3GPP specifications (e.g., 3GPP TS 24.501 V16.1.0).

[0132] When using a REGISTRATION ACCEPT message, AMF300 may send slice restriction information corresponding to the slice requested by UE100 (Requested NSSAI).

[0133] When using the REGISTRATION ACCEPT message, AMF300 may send slice restriction information corresponding to the slices included in the "allowed NSSAI" and / or "Configured NSSAI".

[0134] The operations in steps S303 and S304 are similar to the operations in steps S104 and S105.

[0135] (Example 4) Next, a fourth operation example according to an embodiment will be described. Differences from the above-mentioned operation examples will be mainly described.

[0136] Fig. 21 is a diagram showing an operation example 4. As shown in Fig. 21, in step S401, the gNB 200 determines a restriction condition for at least one of the slices that the gNB 200 supports. Note that the gNB 200 may determine the restriction condition according to slice restriction information received from the AMF 300.

[0137] In step S402, the gNB 200 transmits slice restriction information to the AMF 300. The AMF 300 receives the slice restriction information from the gNB 200. The slice restriction information includes a set of a slice identifier that identifies a restricted slice and condition information that indicates a restriction condition corresponding to the restricted slice. When the gNB 200 determines a restriction condition for a plurality of slices, the slice restriction information may include a set of a slice identifier and condition information for each of the plurality of slices.

[0138] Here, the gNB 200 may transmit slice restriction information using an NGAP message. Such an NGAP message may be, for example, the above-mentioned NG SETUP REQUEST message, RAN CONFIGURATION UPDATE message, PDU SESSION RESOURCE SETUP RESPONSE message, PDU SESSION RESOURCE MODIFY message, etc. Y RE S PONSE message, PDU SESSION RESOURCE RELEASE RE S PONSE messages, etc.

[0139] PDU SESSION RESOURCE SETUP RESPONSE message, PDU SESSION RESOURCE MODIF Y RE S PONSE message or PDU SESSION RESOURCE RELEASE RE S When using a PONSE message, the gNB200 may send slice restriction information for the slice associated with the PDU session.

[0140] In step S403, the AMF 300 performs control to avoid using a slice based on the slice restriction information. For example, when the AMF 300 receives a NAS message (e.g., a REGISTRATION REQUEST message, a PDU SESSION ESTABLISHMENT REQUEST) including a request for a restricted slice (a slice for which a restriction condition is set) from the UE 100, if the AMF 300 determines that the use of the slice by the UE 100 should be restricted based on the restriction condition, the AMF 300 rejects the request. The AMF 300 may reject the request and handover the UE 100 to another gNB 200. For example, the AMF 300 determines a gNB 200 that supports another slice associated with the same service type as the slice requested by the UE 100 as the target gNB 200 of the handover.

[0141] (Example 5) Next, a fifth operation example according to an embodiment will be described. Differences from the above-mentioned operation examples will be mainly described.

[0142] Fig. 22 is a diagram showing operation example 5. As shown in Fig. 22, in step S501, the gNB 200-1 determines restriction conditions for slices that it supports.

[0143] In step S502, the gNB 200-1 transmits slice restriction information to the neighboring gNB 200-2. vinegar The gNB 200-1 receives slice restriction information from the gNB 200-1. The slice restriction information includes a set of a slice identifier that identifies a restricted slice and condition information that indicates a restriction condition corresponding to the restricted slice. When the gNB 200-1 determines a restriction condition for a plurality of slices, the slice restriction information may include a set of a slice identifier and condition information for each of the plurality of slices.

[0144] In step S503, the gNB 200-2 (or the gNB 200-1) performs handover control of the UE 100 based on the slice restriction information. For example, when the gNB 200-2 hands over the UE 100 that transmits and receives data on a restricted slice indicated by the slice restriction information, the gNB 200-2 does not select the gNB 200-1 as the target gNB 200.

[0145] If gNB200-1 determines that UE100 having an RRC connection with gNB200-1 transmits and receives data on a restricted slice and that gNB200-2 supports the slice, it may hand over the UE100 to gNB200-2.

[0146] (Other embodiments) In the above embodiment, the restriction of slices has been described, but it is also possible to permit slices as opposed to "restriction". In the above embodiment, "restriction" may be read as "permission". That is, the gNB 200 or the AMF 300 may permit the use of only a portion of the slices that it supports. In this case, slices other than the slices permitted for use are not available.

[0147] The above-mentioned operational flows are not limited to being implemented separately and independently, but can be implemented by combining two or more operational flows. For example, some steps of one operational flow may be added to another operational flow, or some steps of one operational flow may be replaced with some steps of another operational flow.

[0148] In the above-mentioned embodiment and example, an example in which the base station is an NR base station (gNB) has been described, but the base station may be an LTE base station (eNB) or a 6G base station. The base station may be a relay node such as an IAB (Integrated Access and Backhaul) node. The base station may be a DU (Distributed Unit) of the IAB node. The user equipment may be an MT (Mobile Termination) of the IAB node.

[0149] A program may be provided that causes a computer to execute each process performed by UE100 or gNB200. The program may be recorded in a computer-readable medium. Using the computer-readable medium, it is possible to install the program in a computer. Here, the computer-readable medium on which the program is recorded may be a non-transient recording medium. The non-transient recording medium is not particularly limited, and may be, for example, a recording medium such as a CD-ROM or a DVD-ROM. In addition, a circuit that executes each process performed by UE100 or gNB200 may be integrated, and at least a part of UE100 or gNB200 may be configured as a semiconductor integrated circuit (chip set, SoC: System on a chip).

[0150] As used in this disclosure, the terms "based on" and "depending on" do not mean "based only on" or "depending only on," unless otherwise specified. The term "based on" means both "based only on" and "based at least in part on." Similarly, the term "depending on" means both "based only on" and "based at least in part on." Additionally, "obtain / acquire" may mean obtaining information from stored information, from information received from other nodes, or by generating information. The terms "include," "comprise," and variations thereof do not mean including only the items listed, but may include only the items listed, or may include additional items in addition to the items listed. Additionally, the term "or" as used in this disclosure is not intended to be an exclusive or. Additionally, any reference to elements using designations such as "first," "second," etc., as used in this disclosure is not intended to generally limit the quantity or order of those elements. These designations may be used herein as a convenient method of distinguishing between two or more elements. Thus, reference to a first and a second element does not imply that only two elements may be employed therein or that the first element must precede the second element in some manner. In this disclosure, where articles are added by translation, such as a, an, and the in English, these articles are intended to include the plural unless the context clearly indicates otherwise.

[0151] The above describes the embodiments in detail with reference to the drawings, but the specific configuration is not limited to that described above, and various design changes, etc. are possible without departing from the spirit of the invention.

[0152] This application claims priority to Japanese Patent Application No. 2021-124559 (filed July 29, 2021), the entire contents of which are incorporated herein by reference. [Explanation of symbols]

[0153] 1: Mobile communication systems 10:NG-RAN 20:5GC 50: Network 100:UE 110: Receiving unit 120: Transmitter 130: Control section 200(200-1~200-3):gNB 210: Transmission unit 220: Receiving unit 230: Control section 240: Backhaul communication unit 300:AMF 310: Backhaul communication unit 320: Control section

Claims

1. The method includes receiving, by a user equipment, network slice restriction information relating to a network slice in which a restriction condition is provided from a base station or a core network device; The restriction condition is a condition that restricts use of the network slice, The network slice restriction information includes an identifier for identifying the network slice and information indicating the restriction condition, The restriction condition includes at least one of a user equipment group condition that specifies a group of the user equipment that restricts the use of the network slice, or a RAN condition that specifies a carrier frequency and a Radio Access Technology (RAT) that restricts the use of the network slice. Communications control method.

2. The user equipment determines whether to avoid using the network slice based on the network slice restriction information; and When the user equipment determines that the use of the network slice should be avoided, the user equipment performs control to avoid the use of the network slice. The communication control method according to claim 1 .

3. The control includes: The user equipment in an RRC idle state or an RRC inactive state lowers a priority of a cell supporting the network slice when performing cell selection or cell reselection. The communication control method according to claim 2.

4. The control includes: The method includes: avoiding the user equipment in an RRC connected state from requesting the core network device to use the network slice. The communication control method according to claim 2.

5. The user equipment receives, from the base station, restriction information indicating that the restriction condition is set for a network slice supported by the base station; The user equipment transmits an inquiry to the base station or the core network device to obtain the network slice restriction information in response to receiving the restriction information, Receiving the network slice restriction information includes receiving the network slice restriction information in response to the query. The communication control method according to claim 1 .

6. Sending the inquiry includes the user equipment in an RRC idle state or an RRC inactive state sending the inquiry using a message in a random access procedure. The communication control method according to claim 5.

7. The method further includes starting to use the network slice when the user equipment determines that the restriction condition is no longer satisfied when performing control to avoid using the network slice. The communication control method according to claim 2.

8. Receiving a notification that the restriction condition is lifted when the user equipment performs control to avoid using the network slice; and and the user equipment starts using the network slice in response to receiving the notification. The communication control method according to claim 2.

9. The user equipment includes a receiving unit that receives network slice restriction information regarding a network slice on which a restriction condition is set from a base station or a core network device, The restriction condition is a condition that restricts use of the network slice, The network slice restriction information includes an identifier for identifying the network slice and information indicating the restriction condition, The restriction condition includes at least one of a user equipment group condition that specifies a group of the user equipment that restricts the use of the network slice, or a RAN condition that specifies a carrier frequency and a Radio Access Technology (RAT) that restricts the use of the network slice. User equipment.

10. A chipset for controlling a user equipment, comprising: Execute a process of receiving network slice restriction information regarding a network slice in which a restriction condition is set from a base station or a core network device; The restriction condition is a condition that restricts use of the network slice, The network slice restriction information includes an identifier for identifying the network slice and information indicating the restriction condition, The restriction condition includes at least one of a user equipment group condition that specifies a group of the user equipment that restricts the use of the network slice, or a RAN condition that specifies a carrier frequency and a Radio Access Technology (RAT) that restricts the use of the network slice. Chipset.

11. A program for controlling a user device, The user equipment executes a process of receiving, from a base station or a core network device, network slice restriction information regarding a network slice on which a restriction condition is set; The restriction condition is a condition that restricts use of the network slice, The network slice restriction information includes an identifier for identifying the network slice and information indicating the restriction condition, The restriction condition includes at least one of a user equipment group condition that specifies a group of the user equipment that restricts the use of the network slice, or a RAN condition that specifies a carrier frequency and a Radio Access Technology (RAT) that restricts the use of the network slice. program.

12. A network device, A transmitting unit that transmits network slice restriction information regarding a network slice in which a restriction condition is set to a user device, The restriction condition is a condition that restricts use of the network slice, The network slice restriction information includes an identifier for identifying the network slice and information indicating the restriction condition, The restriction condition includes at least one of a user equipment group condition that specifies a group of the user equipment that restricts the use of the network slice, or a RAN condition that specifies a carrier frequency and a Radio Access Technology (RAT) that restricts the use of the network slice. Network device.

13. A mobile communication system having a network device, The network device transmits network slice restriction information regarding a network slice on which a restriction condition is set to a user device; The restriction condition is a condition that restricts use of the network slice, The network slice restriction information includes an identifier for identifying the network slice and information indicating the restriction condition, The restriction condition includes at least one of a user equipment group condition that specifies a group of the user equipment that restricts the use of the network slice, or a RAN condition that specifies a carrier frequency and a Radio Access Technology (RAT) that restricts the use of the network slice. Mobile communication system.

Images