COMMUNICATION CONTROL METHOD, USER EQUIPMENT, AND CORE NETWORK DEVICE

Abstract

This communication control method according to one embodiment includes: a step in which a user device determines communication conditions to be met by a network slice desired by the user device; and a step in which the user device sends to a core network device a creation request that is a message requesting the creation of the network slice and that includes information indicating the communication conditions.

Description

[Technical field]

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

[0002] Network slicing is defined in the specifications of 3GPP (Third Generation Partnership Project), a standardization project for mobile communication systems (see, for example, Non-Patent Document 1). Network slicing is a technology that creates multiple virtual networks (network slices) by logically dividing a physical network built by a telecommunications carrier. For example, a telecommunications carrier may create a network slice for each service type, such as eMBB (enhanced Mobile Broadband), URLLC (Ultra-Reliable and Low Latency Communications), and mMTC (massive Machine Type Communications). of create do It is possible.

[0003] In the 3GPP specifications, network slices created by a carrier are pre-configured in a user device. The user device uses the network slice by selecting a desired network slice from among these network slices and notifying the network. [Prior art documents] [Non-patent literature]

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

[0005] The communication control method according to the first aspect includes a step in which a user device determines communication conditions that a network slice desired by the user device should satisfy, and a step in which the user device transmits a creation request to a core network device, the creation request being a message requesting creation of the network slice, the creation request including information indicating the communication conditions.

[0006] A communication control method according to a second aspect includes a step in which a core network device receives a creation request from a user device requesting the creation of a network slice desired by the user device, the creation request including information indicating communication conditions determined by the user device that the network slice should satisfy.

[0007] A user device according to a third aspect includes a processor that executes the communication control method according to the first aspect.

[0008] A core network device according to a fourth aspect includes a processor that executes the communication control method according to the second aspect. [Brief description of the drawings]

[0009] [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] FIG. 13 illustrates a PDU session modification procedure according to one embodiment. [Figure 11] FIG. 1 illustrates a RAN Configuration Update procedure according to an embodiment. [Figure 12] A diagram showing an AMF Configuration Update procedure according to one embodiment. [Figure 13] FIG. 2 is a diagram illustrating a basic operation according to an embodiment. [Figure 14] FIG. 1 is a diagram illustrating an operation example 1 according to an embodiment. [Figure 15] FIG. 11 is a diagram illustrating an operation example 2 according to an embodiment. [Figure 16] FIG. 11 is a diagram illustrating an operation example 3 according to an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] However, the network slices already created by the telecommunications carrier may not necessarily meet the communication conditions desired by the user equipment.

[0011] Therefore, an object of the present disclosure is to enable the creation of a network slice that satisfies the communication conditions desired by a user equipment.

[0012] 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.

[0013] (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.

[0014] 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.

[0015] 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).

[0016] 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.

[0017] 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".

[0018] 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.

[0019] 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 .

[0020] 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.

[0021] 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.

[0022] 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.

[0023] 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.

[0024] 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.

[0025] 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.

[0026] 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.

[0027] 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 300 / UPF 400 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 by an F1 interface.

[0028] 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.

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

[0030] 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.

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

[0032] 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.

[0033] 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.

[0034] 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.

[0035] 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.

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

[0037] 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.

[0038] 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).

[0039] 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.

[0040] 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.

[0041] 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.

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

[0043] (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 the following, a "network slice" may be simply called a "slice."

[0044] 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.

[0045] 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.

[0046] 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.

[0047] 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).

[0048] 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.

[0049] 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.

[0050] 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.

[0051] 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.

[0052] 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.

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

[0054] (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.

[0055] 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.

[0056] (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 identifier of a slice requested by the UE 100. 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.

[0057] (3) PDU session modification procedure The PDU session modification procedure is a procedure that allows for configuration changes of an already established PDU session. FIG. 10 is a diagram showing the PDU session modification procedure. As shown in FIG. 10, in step Sc1, the UE 100 transmits a NAS message called PDU SESSION MODIFICATION REQUEST to the AMF 300. In step Sb2, the AMF 300 transmits a NAS message called a PDU SESSION MODIFICATION ACKNOWLEDGE message to the UE 100. Here, the PDU SESSION MODIFICATION REQUEST message includes an identifier of the PDU session and configuration data updated by the UE 100. MODIFICATIONThe ACKNOWLEDGE message is a message that confirms that the setting data has been updated successfully.

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

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

[0060] Figure 11 is a diagram showing a RAN Configuration Update procedure. As shown in Figure 11, in step Sd1, the gNB 200 transmits an NGAP message called a RAN CONFIGURATION UPDATE message to the AMF 300, the NGAP message including the application level configuration data updated by the gNB 200. In step Sd2, 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.

[0061] In addition, if AMF300 fails to update the configuration data, it sends a RAN CONFIGURATION FAILURE message indicating the failure to gNB200.

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

[0063] Figure 12 is a diagram showing the AMF Configuration Update procedure. As shown in Figure 12, in step Se1, AMF300 transmits an NGAP message called an AMF CONFIGURATION UPDATE message to gNB200, which includes application-level configuration data updated by AMF300. In step Se2, 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)).

[0064] In addition, if gNB200 fails to update the configuration data, it sends an AMF CONFIGURATION FAILURE message indicating the failure to AMF300.

[0065] (Basic operation) Next, a basic operation according to the embodiment will be described.

[0066] In the technical specifications of 3GPP, network slices created by a communication operator are pre-configured in the UE 100. The UE 100 selects a desired network slice from among these network slices and notifies the network, thereby using the network slice.

[0067] For example, network slices created by a telecommunications carrier are stored in a SIM (Subscriber Identity Module) of UE 100, and UE 100 selects a desired network slice from among these network slices. Then, UE 100 notifies AMF 300 of a REGISTRATION REQUEST message including a "Requested NSSAI" including a slice identifier of the selected slice. After that, UE 100 receives a REGISTRATION ACCEPT message including an "Allowed NSSAI" including the slice identifier, thereby becoming able to use the slice.

[0068] However, there are cases where a network slice already created by a communication carrier does not necessarily satisfy communication conditions desired by the UE 100. In this case, communication cannot be performed in a slice appropriate for the UE 100.

[0069] In an embodiment, UE100 determines communication conditions that a network slice desired by UE100 should satisfy. UE100 transmits a creation request to AMF300, which is a message requesting creation of the network slice and includes information indicating the communication conditions. This allows the network to grasp the communication conditions that a network slice desired by UE100 should satisfy, and to create a slice appropriate for UE100. This allows UE100 to communicate using a slice appropriate for UE100.

[0070] Fig. 13 is a diagram showing a basic operation according to the embodiment. As shown in Fig. 13, in step S1, UE 100 determines communication conditions that a network slice desired by UE 100 should satisfy. The communication conditions include (1) requested service quality, (2) requested communication path, (3) requested DN, (4) requested security, (5) requested connection destination, (6) requested communication carrier, (7) requested application, (8) requested usage schedule, (9) requested ApprovalThe method includes at least one of the authentication methods. In the following, the "network slice desired by UE 100" may be referred to as the "UE desired slice". The communication request may be a slice specified by UE 100. For example, the user of UE 100 obtains a slice dedicated to the organization (such as a company) to which the user belongs, and determines a slice identifier of the slice as the communication request.

[0071] Next, each communication condition will be described in detail.

[0072] (1) Required service quality The requested service quality indicates the service quality that the UE desired slice should satisfy. The requested service quality includes QoS (Quality of Service) parameters. The QoS parameters may include 5QI (5G QoS identifier), ARP (allocation and retention priority), GFBR (guaranteed flow bit rate), MFBR (maximum flow bit rate), etc. In addition, when the UE 100 connects to the 5GC via an LTE base station, the QoS parameters may include QCI (QoS class identifier), ARP, MBR (maximum bit rate), GBR (guaranteed bit rate), etc. In addition, please refer to the existing 3GPP technical specifications for specific parameters included in the QoS parameters. This is not limited in the present disclosure.

[0073] (2) Request communication path The requested communication path indicates a communication path of user data in the UE desired slice. Such a communication path is a path configured of network nodes through which user data of the UE 100 must pass when transporting the user data to the DN on the UE desired slice. Such a network node is, for example, the UPF 400. The requested communication path is configured of, for example, identifiers of multiple UPFs 400.

[0074] (3) Request DN The requested DN indicates the DN to which the UE should connect to its desired slice.

[0075] (4) Security requirements The requested security indicates a security function supported by the UE 100 on the UE desired slice. The security function is, for example, an encryption algorithm, a protocol (for example, IPsec VPN, etc.), and the like.

[0076] (5) Requested connection destination The requested connection destination is UE100 but , indicates the destination (e.g., IP address) to connect to via the UE's desired slice.

[0077] (6) Requesting entity The requesting carrier indicates a communication carrier capable of handling the UE desired slice. For example, when the UE 100 wants to communicate on the UE desired slice even during roaming, the UE 100 requests a communication carrier. The requesting carrier may be indicated by a PLMN (PLMN ID). The requesting carrier may also be indicated by a carrier code.

[0078] (7) Request Application The requested application indicates an application to be executed on the UE desired slice. The requested application may be permitted in advance by the core network (e.g., AMF 300) to be executed on the UE desired slice. The requested application may be indicated by an application identifier.

[0079] (8) Request for Use The request usage schedule indicates the scheduled time for using the UE's desired slice. The scheduled time may be indicated by frequency, time, or time period. The timer for recreating slices in the CN part and the RAN part described later may be set according to the request usage schedule.

[0080] (9) Request authentication method The requested authentication method indicates an authentication method required for using the UE desired slice. The authentication method includes information required for authentication (e.g., ID, password, etc.), qualifications (e.g., membership qualifications held by the user of the UE 100), a payment method (e.g., credit card number, etc.), etc.

[0081] In step S2, UE 100 transmits a slice creation request to AMF 300 to request the creation of a network slice. AMF 300 receives the slice creation request from UE 100. The slice creation request includes information indicating communication conditions. The slice creation request may be transmitted by a NAS message such as the above-mentioned REGISTRATION REQUEST message or PDU SESSION ESTABLISHMENT REQUEST message. The slice creation request may be transmitted by a new NAS message. Note that UE 100 may transmit the slice creation request to AMF 300 on behalf of a group consisting of multiple UEs 100.

[0082] In step S3, AMF 300 transmits a slice creation result to UE 100. UE 100 receives the slice creation result from AMF 300. The slice creation result is a slice creation success notification or a slice creation failure notification. The slice creation success notification includes a slice identifier that identifies a slice created based on a communication condition. The slice creation failure notification includes information indicating that the creation of the slice has failed. Detailed operations related to the slice creation failure notification will be described in Operation Example 3 described later.

[0083] The slice creation result may be transmitted in the above-mentioned REGISTRATION ACCEPT message, PDU SESSION ESTABLISHMENT RESPONSE message, PDU SESSION MODIFICATION ACKNOWLEDGE message, etc. The slice creation result may be transmitted in a new NAS message.

[0084] In the following, the explanation will be given on the assumption that the slice creation result is a slice creation success notification.

[0085] In step S4, the UE 100 uses the slice (UE desired slice) identified by the slice identifier received in step S3. An example of using the slice is as follows.

[0086] First example: When performing initial registration to the network, UE 100 requests a UE desired slice from AMF 300. Specifically, UE 100 notifies AMF 300 of a REGISTRATION REQUEST message including a "Requested NSSAI" including the slice identifier received in step S3.

[0087] Second example: UE 100 requests AMF 300 to establish a PDU session on the UE desired slice. Specifically, UE 100 transmits a PDU SESSION ESTABLISHMENT REQUEST message including the slice identifier received in step S3 to AMF 300.

[0088] Third example: UE 100 changes the slice associated with the already established PDU session to the UE desired slice. Specifically, UE 100 transmits a PDU SESSION ESTABLISHMENT modification request message including the slice identifier received in step S3 to AMF 300. Note that signaling for associating the already established PDU session with the UE desired slice may be initiated by gNB 200, AMF 300, or SMF.

[0089] In a basic operation, the communication conditions may be determined by an application layer of the UE 100. The application layer provides the determined communication conditions to the NAS layer of the UE 100, and the NAS layer transmits a slice creation request including the communication conditions to the AMF 300. The application layer of the UE 100 may provide the communication conditions to the AS layer of the UE 100. The communication conditions may be notified from the application layer of the UE 100 to the AS layer via the NAS layer. The communication conditions may be determined by a user of the UE 100.

[0090] (Example 1) Next, an operation example 1 based on the basic operation of the embodiment will be described. FIG 14 is a diagram showing the operation example 1.

[0091] As shown in FIG. 14, the operation in step S101 is similar to the operation in step S1 in the basic operation.

[0092] In step S102, AMF300 attempts to create a CN part of the UE desired slice. Specifically, AMF300 extracts communication conditions (hereinafter, CN communication conditions) that the CN part should satisfy from among the communication conditions, and attempts to create a CN part that satisfies the CN communication conditions. Here, the CN communication conditions are, for example, the above-mentioned requested communication path, requested DN, requested security, requested connection destination, requested communication carrier, requested application, etc.

[0093] The AMF 300 attempts to create a CN part in cooperation with other network nodes as necessary. For example, when a requested communication path is included in the CN communication conditions, the AMF 300 attempts to create a CN part in cooperation with each network node (UPF 400) on the communication path.

[0094] In step S103, AMF300 determines whether the creation of the CN part was successful. Here, if a CN part that satisfies at least one of the CN communication conditions can be created, AMF300 determines that the creation of the CN part was successful. If not (if all of the CN communication conditions are not satisfied), AMF300 determines that the creation of the CN part failed. Note that if there is an existing slice supported by AMF300 that satisfies the communication conditions, AMF300 may extract that slice. In this case, AMF300 determines that the creation of the CN part was successful.

[0095] When it is determined that the creation of the CN part has failed (step S103: NO), in step S104, AMF 300 transmits a slice creation failure notification as a slice creation result to UE 100. The slice creation failure notification includes cause information indicating that the cause of the failure in the creation of the slice lies in the core network device (AMF 300).

[0096] After transmitting the slice creation failure notification, the AMF 300 may set a flag in its own storage area indicating that the creation has failed. After setting such a flag, the AMF 300 may start a timer to prompt itself to create again. The slice creation failure notification may further include information indicating that the UE desired slice can be created in the future. In this case, the slice creation failure notification may further include a scheduled time for creating the UE desired slice. The operation of the UE 100 that has received the slice creation failure notification will be described in Operation Example 3 described later.

[0097] On the other hand, when it is determined that the creation of the CN part is successful (step S103: YES), in step S105, the AMF300 transmits a RAN part creation request to the gNB200 to request the creation of a RAN part of the UE desired slice. Specifically, first, the AMF300 assigns a slice identifier to the slice including the CN part created by the AMF300, and stores it in its own storage area. Second, the AMF300 extracts communication conditions (hereinafter, RAN communication conditions) that the RAN part should satisfy from the communication conditions received in step S101. The RAN communication conditions include, for example, a required service quality. Third, the AMF300 transmits a RAN part creation request including the slice identifier and the RAN communication conditions to the gNB200. The RAN part creation request may be transmitted, for example, in the above-mentioned AMF CONFIGURATION UPDATE message. The RAN part creation request may be transmitted in a new NGAP message.

[0098] In step S106, the gNB 200 attempts to create a RAN part of the UE desired slice. Specifically, the gNB 200 attempts to create a RAN part that satisfies the RAN communication conditions received in step S105. For example, the gNB 200 attempts to secure radio resources (time and frequency resources that can be allocated to the UE 100) so as to satisfy the RAN communication conditions (required service quality).

[0099] In step S107, the gNB200 determines whether the creation of the RAN part has been successful. If the RAN part that satisfies at least one of the RAN communication conditions has been created, the gNB200 determines that the creation of the RAN part has been successful. If not, the gNB200 determines that the creation of the RAN part has failed.

[0100] In addition, if there is an existing radio resource that satisfies the communication conditions among the existing radio resources supported by the gNB 200, the gNB 200 may allocate the radio resource. In this case, the gNB 200 determines that the creation of the RAN part is successful.

[0101] When it is determined that the creation of the RAN part has failed (step S107: NO), in step S108, the gNB 200 transmits a RAN part creation failure notification to the AMF 300. The AMF 300 receives the RAN part creation failure notification from the gNB 200. This allows the AMF 300 to know that the creation of the UE desired slice requested by the UE 100 has failed. After determining that the creation of the RAN part has failed, the gNB 200 may set a flag in its own storage area indicating that the creation has failed. After setting such a flag, the gNB 200 may start a timer that prompts itself to create the slice again.

[0102] The RAN part creation failure notification includes cause information indicating the cause of the failure in creating the RAN part. Such a cause may be, for example, an inability to secure radio resources. The RAN part creation failure notification may further include information indicating that the RAN part can be created when the resource situation improves in the future. In this case, the RAN part creation failure notification may further include a scheduled time for creating the RAN part. The RAN part creation failure notification may be transmitted, for example, by the above-mentioned AMF CONFIGURATION UPDATE FAILURE message. The RAN part creation failure notification may be transmitted by a new NGAP message.

[0103] In step S109, the AMF 300 transmits a slice creation failure notification as a slice creation result to the UE 100. The slice creation failure notification includes cause information indicating that the cause of the failure in creating the slice is in the RAN (gNB 200).

[0104] On the other hand, if it is determined that the RAN part creation has been successful (step S107: YES), in step S110, the gNB 200 transmits a RAN part creation success notification to the AMF 300. The AMF 300 receives the RAN part creation success notification from the gNB 200. This allows the AMF 300 to know that the UE desired slice requested by the UE 100 has been successfully created.

[0105] The RAN part creation success notification may be sent in the above-mentioned AMF CONFIGURATION UPDATE ACKNOWLEDGE message. Also, the RAN part creation success notification may be sent in a new NGAP message.

[0106] In step S112, AMF 300 transmits a slice creation success notification to UE 100 as a slice creation result.

[0107] The operation of step S113 is similar to the operation of step S4 in the basic operation.

[0108] (Example 2) Next, an operation example 2 will be described. Differences from the above operation examples will be mainly described.

[0109] Operation example 2 is an operation example in the case where a slice based on communication conditions is created, but some of the communication conditions are not satisfied. FIG 15 is a diagram showing operation example 2.

[0110] As shown in FIG. 15, the operation of step S201 is similar to the operation of step S1 in the basic operation.

[0111] In step S202, the UE 100 receives a slice creation success notification from the AMF 300. The slice creation success notification includes a slice identifier for identifying the created slice, information indicating that at least one of the communication conditions for the slice is not satisfied, and cause information indicating the cause of the condition not being satisfied. The cause information indicates that the cause of the condition not being satisfied is in the RAN (gNB 200), or indicates that the cause of the condition not being satisfied is in the CN (AMF 300).

[0112] The slice creation success notification may further include detailed conditions for the communication conditions that are not met. For example, if the requested service quality is not met, the detailed conditions may include the details of the communication conditions that the created slice does not meet. vinegarIndicates the quality of service (QoS parameters). If the requested communication path is not satisfied, the detailed conditions indicate the communication path on the created slice.

[0113] The UE 100 that receives such a slice creation success notification can understand that the slice has been created but some communication requirements for the slice are not satisfied.

[0114] The slice creation success notification received by the UE 100 from the AMF 300 may be provided from the NAS layer of the UE 100 to the AS layer of the UE 100. This allows the AS layer to grasp the slice creation status and to request an update of the slice, which will be described later.

[0115] In step S203, the UE 100 determines whether the slice needs to be updated. For example, the UE 100 may determine whether the slice needs to be updated based on the detailed condition received in step S202. If the UE 100 does not accept the condition indicated by the detailed condition, the UE 100 determines that the slice needs to be updated.

[0116] When the UE 100 determines whether the slice needs to be updated (step S203: YES), the UE 100 transmits a slice update request for updating the slice so as to satisfy the unsatisfied communication condition. The UE 100 determines the transmission destination of the slice update request as the gNB 200 or the AMF 300 based on the cause information.

[0117] In step S204, UE 100 determines whether the cause information indicates gNB 200. If the cause information indicates gNB 200 (step S204: YES), in step S205, UE 100 transmits a slice update request to gNB 200. This can reduce overhead compared to a request via AMF 300. The slice update request includes a slice identifier of a slice for which an update is requested, and a communication condition requested by UE 100 for the slice.

[0118] In addition, the content of the slice update request may be determined by an application layer of the UE 100. The application layer transmits the determined content to the AS layer of the UE 100. After that, the UE 100 (AS layer) transmits the slice update request to the gNB 200.

[0119] In step S206, the gNB 200 transmits the slice update result to the UE 100. The UE 100 receives the slice update result from the gNB 200. The slice update result includes update success information indicating that the slice update has been successful or update failure information indicating that the slice update has failed. Update success information The UE 100 that has received the slice update result including the update failure information can use the updated slice. On the other hand, the UE 100 that has received the slice update result including the update failure information can request the gNB 200 to update the slice again.

[0120] Here, we will explain the message used when sending a slice update request from UE100 to gNB200, and the message used when sending a slice update result from gNB200 to UE100.

[0121] For the UE 100 in the RRC idle state or the RRC inactive state, the slice update request and the slice update result may be transmitted using a message during the random access procedure. This allows the UE 100 to receive the slice update result from the gNB 200 without transitioning to the RRC connected state, thereby reducing power consumption due to transitioning to the RRC connected state.

[0122] For the UE 100 in the RRC idle state or the RRC inactive state, the message used to transmit the slice update request may be MSG1 (Message 1) or MSG3 (Message 3) in a 4-step random access procedure. Also, the message used to transmit the slice update request may be MSGA (Message A) in a 2-step random access procedure. Also, the message used to transmit the slice update result may be MSG4 (Message 4) in a 4-step random access procedure. Also, the message used to transmit the slice update result may be MSGB (Message B) in a 2-step random access procedure. MSGA is a message obtained by integrating MSG1 and MSG3. MSGB is a message obtained by integrating MSG2 and MSG4.

[0123] 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 resource information 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, etc. MSG3 may be a message dedicated to a slice update request. 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, etc. MSG4 may be a message dedicated to a slice update result.

[0124] For the UE 100 in the RRC connected state, the slice update request is transmitted using, for example, a UEAssistanceInformation message. The slice update result is transmitted using, for example, an RRCReconfiguration message, an RRCRelease message, or the like.

[0125] In step S207, the gNB 200 transmits the slice update result to the AMF 300. The slice update result may be transmitted in a RAN Configuration Update message. Alternatively, the slice update result may be transmitted in a new NGAP message.

[0126] Next, a case in which UE 100 transmits a slice update request to AMF 300 will be described.

[0127] original When the cause information does not indicate the gNB200 (that is, the cause information indicates the AMF300) (step S204: NO), in step S208, the UE100 transmits a slice update request to the AMF300. The slice update request includes a slice identifier of a slice requesting an update and a communication condition requested by the UE100 for the slice. The slice update request may be transmitted in the above-mentioned PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message. The slice update request may be transmitted in a new NAS message.

[0128] In step S209, the AMF 300 transmits a slice update result to the UE 100. The UE 100 receives the slice update result from the AMF 300. The slice update result includes update success information indicating that the slice update has been successful or update failure information indicating that the slice update has failed. Update success information Includes slice The UE 100 that receives the update result can use the updated slice. sliceAfter receiving the update result, UE 100 can request AMF 300 to update the slice again.

[0129] The slice update result may be sent in a NAS message such as the above-mentioned REGISTRATION ACCEPT, PDU SESSION ESTABLISHMENT RESPONSE, or PDU SESSION MODIFICATION ACKNOWLEDGE message. The slice update result may also be sent in a new NAS message.

[0130] In the second operation example, the UE 100 may request the AMF 300 to update the RAN part of the UE desired slice. That is, the UE 100 may transmit a slice update request to the AMF 300 even if the cause information indicates the gNB 200. In this case, the AMF 300 forwards the request to the gNB 200. Although this generates overhead, this may be preferable in terms of management / sequence.

[0131] In the second operation example, the UE 100 may request the gNB 200 to update the CN part of the UE desired slice. That is, the UE 100 may transmit a slice update request to the gNB 200 even if the cause information indicates the AMF 300. In this case, the gNB 200 forwards the request to the AMF 300. Although this generates overhead, this may be preferable in terms of management / sequence.

[0132] (Modification 1 of Operation Example 2) Next, a modification 1 of the operation example 2 will be described. In comparison with the operation example 2, in the modification 1, the gNB 200 autonomously updates the slice even without receiving a slice update request from the UE 100. For example, when the usage status of radio resources is improved and the gNB 200 can create a RAN part that satisfies the requested service quality that was not satisfied at the time of the initial creation, the gNB 200 transmits the slice update result to the UE 100 and the AMF 300. In this case, the slice update result may be transmitted by a RAN paging message.

[0133] The gNB 200 may transmit a slice update result to multiple UEs 100 using the same slice. In this case, the gNB 200 transmits a RAN paging message by putting a slice identifier of the updated slice into an information element (PagingRecord) indicating the paging target in the RAN paging message. The gNB 200 may transmit the slice update result in a SIB.

[0134] (Modification 2 of Operation Example 2) Next, a second modification of the second operation example will be described.

[0135] Compared with the operation example 2, in the modification example 2, the AMF 300 autonomously updates the slice even if it does not receive a slice update request from the UE 100. For example, when the AMF 300 can create a slice that satisfies a communication condition that was not satisfied at the time of the initial creation, the AMF 300 transmits a slice update result to the UE 100 and the gNB 200. In this case, the slice update result may be transmitted by a CN paging message.

[0136] The AMF 300 may transmit a slice update result to multiple UEs 100 using the same slice. In this case, the AMF 300 transmits a CN paging message by putting a slice identifier of the updated slice into an information element (PagingRecord) indicating the paging target in the CN paging message.

[0137] (Example 3) Next, an operation example 3 will be described. Differences from the above operation examples will be mainly described.

[0138] The operation example 3 is an operation example regarding the operation of the UE 100 that has received a creation failure notification. FIG.

[0139] As shown in FIG. 16, the operation of step S301 is similar to the operation of step S1 in the basic operation.

[0140] In step S302, the UE 100 receives a slice creation failure notification from the AMF 300. The slice creation failure notification includes cause information indicating a cause of the slice creation failure. The cause information indicates that the cause of the failure is in the RAN (gNB 200) or that the cause of the failure is in the CN (AMF 300).

[0141] The UE 100 that has received the slice creation failure notification transmits a creation re-request to re-request creation of a slice. The UE 100 determines the transmission destination of the creation re-request as the gNB 200 or the AMF 300 based on the cause information.

[0142] The slice creation failure notification received by the UE 100 from the AMF 300 may be provided from the NAS layer of the UE 100 to the AS layer of the UE 100. This allows the AS layer to grasp the slice creation status and to request re-creation of the slice, which will be described later.

[0143] In step S303, UE 100 determines whether the cause information indicates gNB 200. If the cause information indicates gNB 200 (step S303: YES), in step S304, UE 100 transmits a creation re-request to gNB 200. This allows overhead to be reduced compared to a request via AMF 300. The creation re-request includes communication conditions requested by UE 100. The operation of gNB 200 that receives the creation re-request is the same as the operation from step S106 onwards in operation example 1.

[0144] When the cause information does not indicate the gNB 200 (that is, the cause information indicates the AMF 300) (step S303: NO), in step S305, the UE 100 transmits a creation re-request to the AMF 300. The operation of the AMF 300 that receives the creation re-request is similar to the operation from step S102 onwards in the operation example 1.

[0145] In the third operation example, when the UE 100 receives a slice creation failure notification from the AMF 300, the NAS layer of the UE 100 may provide the slice creation failure notification to the AS layer of the UE 100. In addition, the NAS layer may provide TA (Tracking Area) information managed by the NAS layer to the AS layer. This allows the AS layer to make decisions such as cell selection for slice connection.

[0146] (Modification of operation example 3) Next, a modification of the third operational example will be described.

[0147] In a modification of the operation example 3, the slice creation failure notification further includes information indicating a network device that supports an existing slice that satisfies the communication conditions. Such an existing slice is a slice that is not supported by the AMF 300 that received the slice creation request. As a result, even if the AMF 300 fails to create the UE desired slice, it is possible to introduce to the UE 100 a network device that supports an existing slice that satisfies the communication conditions, and the UE 100 is able to access the network device and use the UE desired slice.

[0148] The network device included in the slice creation failure notification is, for example, the gNB 200 that manages a cell other than the serving cell of the UE 100, the AMF 300 that belongs to a PLMN other than the serving PLMN of the UE 100, etc. The slice creation failure notification includes information indicating these cells and PLMNs. The UE 100 that has received the slice creation failure notification accesses the network device to use the slice.

[0149] (Other embodiments) A user of the UE 100 may request the core network to create a UE-requested slice on the Internet. For example, the user accesses a website for creating slices in a browser and inputs a communication request. The website notifies the user of a slice identifier of the created slice. The user then stores the slice identifier in a storage area (e.g., SIM) of the UE 100. This allows the UE 100 to use the UE-requested slice.

[0150] The above-mentioned operational flows (operation examples) 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.

[0151] 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.

[0152] 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).

[0153] 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.

[0154] 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.

[0155] This application claims priority to Japanese Patent Application No. 2021-129308 (filed August 5, 2021), the entire contents of which are incorporated herein by reference. [Explanation of symbols]

[0156] 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. A user equipment determines a communication condition that a network slice desired by the user equipment should satisfy; The user equipment transmits to a core network device a message requesting the creation of the network slice, the message including information indicating the communication conditions; and The core network device and the base station create the network slice; After sending the creation request, the user equipment receives from the core network device a creation success notification including a slice identifier that identifies the network slice created based on the communication conditions; and If the creation success notification includes information indicating that at least one of the communication conditions is not satisfied for the network slice, the user equipment transmits an update request to the core network device or the base station to update the network slice so as to satisfy at least one of the communication conditions. Communications control method.

2. The communication conditions are: The network slice includes at least one of a requested quality of service indicating a quality of service that the network slice should satisfy, a communication path of user data in the network slice, an application to be executed on the network slice, a planned time for using the network slice, and an authentication method required for using the network slice. The communication control method according to claim 1 .

3. The method further includes the step of: The communication control method according to claim 1 .

4. The core network device and the base station create the network slice; If the successful creation notification includes information indicating that at least one of the communication conditions is not satisfied for the network slice, the user equipment transmits an update request to the core network device or the base station to update the network slice so as to satisfy at least one of the communication conditions. The communication control method according to claim 1 .

5. The creation success notification includes cause information indicating whether a cause of at least one of the communication conditions not being satisfied is due to the core network device or the base station, Sending the update request comprises: If the cause information indicates the core network device, the user equipment sends the update request to the core network device; and if the cause information indicates the base station, the user equipment transmits the update request to the base station. The communication control method according to claim 4.

6. The method further comprises receiving, by the user equipment, information indicating that the network slice is updated from the base station or the core network device.

6. A communication control method according to claim 4 or 5.

7. A method for determining a communication condition that a network slice desired by a user equipment should satisfy, comprising: The user equipment transmits to a core network device a message requesting the creation of the network slice, the message including information indicating the communication conditions; and After sending the creation request, the user equipment receives a creation failure notification from the core network device, the creation failure notification including information indicating that creation of the network slice has failed and information indicating a network device belonging to an existing network slice that satisfies the communication condition; and the user device accessing the network device. Communications control method.

8. A method for determining a communication condition that a network slice desired by a user equipment should satisfy, comprising: The user equipment transmits to a core network device a message requesting the creation of the network slice, the message including information indicating the communication conditions; and The core network device and the base station create the network slice; After sending the creation request, the user equipment receives a creation failure notification from the core network device, the creation failure notification including information indicating that creation of the network slice has failed; The user equipment transmits a creation re-request to the core network device or the base station in response to receiving the creation failure notification, the creation re-request re-requesting the creation of the network slice; The creation failure notification includes cause information indicating whether the cause of the failure of the creation of the network slice is the core network device or the base station, Sending the creation re-request includes: When the cause information indicates the core network device, the user device sends the creation re-request to the core network device; and if the cause information indicates the base station, the user equipment transmits the generation re-request to the base station. Communications control method.

9. Determining the communication conditions includes an application layer of the user equipment determining the communication conditions; The sending of the creation request includes a non-access stratum (NAS) layer of the user device sending the communication conditions provided by the application layer in the creation request. A communication control method according to any one of claims 1 to 8.

10. The NAS layer may further provide the creation success notification to an Access Stratum (AS) layer of the user equipment. The communication control method according to any one of claims 1 to 6.

11. The NAS layer may further provide the creation failure notification to an AS layer of the user equipment. The communication control method according to claim 7 or 8.

12. A core network device receives, from a user equipment, a creation request for creating a network slice desired by the user equipment; The creation request includes information indicating communication conditions that the network slice should satisfy, as determined by the user equipment; The network slice includes a core network part created by the core network device and a Radio Access Network (RAN) part created by a base station, If the core network device succeeds in creating the core network part, the core network device transmits information required to create the RAN part to the base station based on the communication conditions. Communications control method.

13. When the core network device receives information from the base station indicating that the creation of the RAN part is successful, the core network device further transmits a creation success notification to the user device, the creation success notification including a slice identifier that identifies the network slice created based on the communication conditions. have The communication control method according to claim 12.

14. The method further includes transmitting a creation failure notification to the user equipment when the core network device fails to create the core network part or when the core network device receives information from the base station indicating that the creation of the RAN part has failed, the creation failure notification including information indicating that the creation of the network slice has failed. The communication control method according to claim 12.

15. A user device, A control unit that determines communication conditions that a network slice desired by the user equipment should satisfy; A transmission unit that transmits a message requesting the creation of the network slice to a core network device, the message including information indicating the communication conditions; and A receiving unit that receives a creation success notification from the core network device, the notification including a slice identifier that identifies the network slice created based on the communication conditions, When the creation success notification includes information indicating that at least one of the communication conditions is not satisfied for the network slice, the transmission unit transmits, to the core network device or the base station, an update request for updating the network slice so as to satisfy at least one of the communication conditions. User equipment.

16. A user device. A control unit that determines communication conditions that a network slice desired by the user equipment should satisfy; A transmission unit that transmits a message requesting the creation of the network slice to a core network device, the message including information indicating the communication conditions; and a receiving unit that receives, after the sending of the creation request, a creation failure notification from the core network device, the creation failure notification including information indicating that the creation of the network slice has failed and information indicating a network device belonging to an existing network slice that satisfies the communication condition; The control unit controls access to the network device. User equipment.

17. A user device. A control unit that determines communication conditions that a network slice desired by the user equipment should satisfy; A transmission unit that transmits a message requesting the creation of the network slice to a core network device, the message including information indicating the communication conditions; and A receiving unit that receives a creation failure notification from the core network device after transmitting the creation request, the creation failure notification including information indicating that the creation of the network slice has failed, The transmission unit transmits a creation re-request to the core network device or the base station in response to receiving the creation failure notification, the creation re-request re-requesting creation of the network slice; The creation failure notification includes cause information indicating whether the cause of the failure of the creation of the network slice is the core network device or the base station, When the cause information indicates the core network device, the transmission unit transmits the creation re-request to the core network device; The transmission unit transmits the creation re-request to the base station when the cause information indicates the base station. User equipment.

18. A core network device, A receiving unit that receives, from a user device, a creation request for requesting creation of a network slice desired by the user device; A transmitter unit, The creation request includes information indicating communication conditions that the network slice should satisfy, as determined by the user equipment; The network slice includes a core network part created by the core network device and a Radio Access Network (RAN) part created by a base station, When the creation of the core network part is successful, the transmission unit transmits information required to create the RAN part to the base station based on the communication conditions. Core network equipment.

Images