Emergency network separation method

Abstract

The network node includes a control unit and a communication unit. The communication unit is configured to, in an emergency, receive a message requesting a terminal device to use a first network slice, which is a network slice allocated for emergency use. The control unit is configured to, in an emergency, determine whether the terminal device is registered for emergency use; if the terminal device is registered for emergency use, establish a PDU session with the terminal device through the first network slice; if the terminal device is not registered for emergency use, reject the request.

Description

Cross-references of related applications

[0001] This application is based on and claims priority to Japanese Patent Application No. 2024-041939, filed on March 18, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This disclosure relates to an emergency network separation method, and more particularly to an emergency network separation method for separating a normally registered terminal device and a terminal device registered for emergency use during an emergency such as a disaster. Background Technology

[0003] The Third Generation Partnership Project (3GPP) defines network slicing. Network slicing is a technology that allows for fine-grained control of services for each application by virtually segmenting the network, implementing bandwidth limiting, and prioritization.

[0004] The network that is virtually segmented is called a network slice. Network slices are assigned an identifier called S-NSSAI (Single-Network Slice Selection Assistance Information). Existing technical documents Non-patent literature

[0005] Non-patent document 1: 3GPP TS 23.501 V18.4.0 (2023-12) Summary of the Invention

[0006] Non-patent document 1 describes the provision of an emergency service. In the emergency service, when an emergency such as a disaster occurs, Internet Protocol Multimedia Subsystem (IMS) service sessions are prioritized for UEs registered for emergency use over normally registered UEs.

[0007] Non-patent document 1 only describes prioritizing IMS service sessions for UEs registered for emergency use in the event of an emergency, but does not describe separating the network between normally registered UEs and UEs registered for emergency use.

[0008] This disclosure provides a technique for separating a network between normally registered terminal devices and terminal devices registered for emergency use in emergency situations.

[0009] To achieve the above objectives, the network node involved in the implementation method is a network node including a control unit and a communication unit. The communication unit is configured to receive a message requesting a terminal device to use a first network slice in an emergency. The first network slice is a network slice allocated for emergency use. The control unit is configured to determine whether the terminal device is registered for emergency use in an emergency. If the terminal device is registered for emergency use, a PDU session is established with the terminal device through the first network slice. If the terminal device is not registered for emergency use, the request is rejected.

[0010] Furthermore, the method involved in the implementation is a method performed by a network node, including: in an emergency, receiving a message requesting a terminal device to use a first network slice, wherein the first network slice is a network slice allocated for emergency use; determining whether the terminal device is registered for emergency use; if the terminal device is registered for emergency use, establishing a PDU session with the terminal device through the first network slice; and if the terminal device is not registered for emergency use, rejecting the request.

[0011] Based on the above configuration, in emergency situations, only terminal devices registered for emergency use can use the dedicated emergency network slice, thereby separating the network between normally registered terminal devices and those registered for emergency use. Furthermore, this configuration can be used to achieve other effects, either as a substitute for or in conjunction with this effect. Attached Figure Description

[0012] Figure 1 This is a diagram illustrating the configuration of the communication system according to the first embodiment. Figure 2 This is a block diagram illustrating the physical configuration of the network nodes according to the first embodiment. Figure 3 This is a block diagram illustrating the logical configuration of the network nodes involved in the first embodiment. Figure 4 This is a block diagram illustrating the physical configuration of the terminal device according to the first embodiment. Figure 5 This is a block diagram illustrating the logical configuration of the terminal device according to the first embodiment. Figure 6 This is a diagram illustrating an outline of the network slices involved in the first embodiment. Figure 7This is a flowchart illustrating the network slice registration process according to the first embodiment. Figure 8 This is a flowchart illustrating the network slice registration process under normal conditions according to the first embodiment. Figure 9 This is a flowchart illustrating the network slice registration process under emergency conditions according to the first embodiment. Figure 10 This is a flowchart illustrating the network slice registration process under emergency conditions according to the first embodiment. Figure 11 This is a flowchart illustrating the network slice registration process under emergency conditions according to the second embodiment. Figure 12 This is a flowchart illustrating the network slice registration process under emergency conditions according to the second embodiment. Figure 13 This is a flowchart illustrating the network slice selection process involved in the second embodiment. Detailed Implementation

[0013] Hereinafter, embodiments of this embodiment will be described in detail with reference to the accompanying drawings. Furthermore, in this specification and the accompanying drawings, elements that can be described in the same way are labeled with the same reference numerals, and repeated descriptions can be omitted.

[0014] The embodiments described below are merely examples of configurations that can implement this embodiment. The embodiments described below can be appropriately modified or changed depending on the configuration of the apparatus to which this embodiment is applied and various conditions. Not all combinations of elements included in the embodiments described below are necessary to implement this embodiment, and some elements can be appropriately omitted. Therefore, the scope of this embodiment is not limited to the configurations described in the embodiments described below. Configurations combining multiple configurations described in the embodiments described below can also be used, provided they do not contradict each other.

[0015] 1. First Implementation Method 1.1 Communication System Reference Figure 1 This describes the configuration of the communication system 1 involved in the implementation method. For example... Figure 1As shown, the communication system 1 includes a network node 10, a terminal apparatus 20, and a RAN node (base station apparatus) 30. The network node 10 is connected to a data network (DN) 40. DN 40 includes networks such as the Internet. The communication system 1 is configured according to predetermined technical specifications (TS). For example, the communication system 1 may comply with the technical specifications defined by 3GPP (e.g., 5G, 5G evolution, and 6G).

[0016] In communication system 1, for example, communication is performed between the various network nodes 10 described later, according to the 5G NR specification. Additionally, communication is performed between terminal device 20, RAN node 30, and network node 10. The area between terminal device 20 and RAN node 30 is a radio band.

[0017] Network node 10 constitutes the core network. Network node 10 includes Access and Mobility Management Function (AMF) 10a, User Plane Function (UPF) 10b, Unified Data Management (UDM) / Unified Data Repository (UDR) 10c, Application Function (AF) 10d, Network Slice Selection Function (NSSF) 10e, Session Management Function (SMF) 10f, Policy Control Function (PCF) 10g, and Network Exposure Function (NEF).

[0018] Network node 10 is not limited to network nodes such as AMF10a mentioned above, and may include other network nodes specified or to be specified in the 3GPP technical specifications. Furthermore, a portion of network nodes 10, such as AF10d, may not necessarily constitute the core network. Such network nodes 10 are located outside the communication system 1 and communicate with network nodes 10 within the communication system 1 via DN40.

[0019] In communication system 1, a user plane for sending and receiving user data and a control plane for sending and receiving control data are independently configured. That is, communication system 1 supports C / U separation. The user plane is called the U plane, and the control plane is called the C plane.

[0020] Terminal device 20 may be a device that wirelessly communicates with RAN node 30, for example, it may be a user equipment (UE) operating in accordance with the 3GPP 5G NR specification. Alternatively, terminal device 20 may be other devices specified in or to be specified in the 3GPP technical specifications.

[0021] Terminal device 20 may be, for example, a mobile phone terminal such as a smartphone, a tablet terminal, a laptop PC, a communication module, a communication card, or an IoT device such as a surveillance camera and a robot. Terminal device 20 may also be a vehicle (e.g., a car, a tram, etc.) or a device mounted thereon. Terminal device 20 may also be a transport vehicle other than a vehicle (e.g., a ship, an airplane, etc.) or a device mounted thereon. Terminal device 20 may also be a sensor or a device mounted thereon. Furthermore, terminal device 20 may also be referred to as a terminal, mobile station, mobile terminal, mobile device, mobile unit, subscriber station, subscriber terminal, subscriber device, subscriber unit, wireless station, wireless terminal, wireless device, wireless unit, remote station, remote terminal, remote device, remote unit, etc. Terminal device 20 may also be a device adapted to one or more of enhanced mobile broadband (eMBB), ultra-reliable and low-latency communications (URLLC), and massive machine-type communications (mMTC).

[0022] RAN node 30 forms a Radio Access Network (RAN) and manages at least one cell. A cell constitutes the smallest unit of a communication area. For example, a cell belongs to a frequency (e.g., a carrier frequency) and consists of a component carrier. The term "cell" sometimes refers to a wireless communication resource and sometimes to the communication target of terminal device 20. RAN node 30 conducts wireless communication with terminal device 20 located in its cell in both the U-plane and C-plane. In other words, RAN node 30 terminates both the U-plane and C-plane protocols for terminal device 20.

[0023] RAN node 30 communicates with network node 10 in both the U-plane and the C-plane. More specifically, RAN node 30 is connected to AMF10a in the C-plane via an NG-C interface (not shown) and to UPF10b in the U-plane via an NG-U interface (not shown).

[0024] RAN node 30 may be, for example, a gNB that provides the terminal device 20 with the U-plane and C-plane according to the 3GPP 5G NR specification and connects to the 3GPP 5GC (5G Core Network). Alternatively, RAN node 30 may be other devices specified or to be specified in the 3GPP technical specifications.

[0025] Next, refer to Figure 2 This describes the physical configuration of network node 10. For example... Figure 2 As shown, network node 10 includes a processor 101, a memory 102, and a transmitter / receiver 103 as hardware components. These elements in network node 10 are interconnected via an internal bus. Furthermore, network node 10 may include... Figure 2 Hardware elements other than those shown.

[0026] The processor 101 is a computing element that implements various functions of the network node 10. The processor 101 may be a system-on-a-chip (SoC) that includes elements such as a central processing unit (CPU), a graphics processing unit (GPU), and a memory controller.

[0027] The memory 102 comprises at least one storage medium, such as read-only memory (ROM), random access memory (RAM), hard disk drive (HDD), and solid state drive (SSD). The memory 102 is an element that temporarily or permanently stores programs and data used to perform various processes in the network node 10. The programs include one or more commands for actions of the network node 10. The processor 101 implements the functions of the network node 10 by expanding the program stored in the memory 102 into the memory 102 and / or system memory (not shown) and executing it.

[0028] The transmitter receiver 103 transmits and receives signals between other network nodes 10 and RAN nodes 30.

[0029] Next, refer to Figure 3This describes the logical configuration of network node 10. For example... Figure 3 As shown, network node 10 includes a control unit 110 and a communication unit 120 as functional blocks. The communication unit 120 includes at least one transmitting unit 111 and at least one receiving unit 122.

[0030] The control unit 110 may include at least one processor 101 and at least one memory 102. In other words, the control unit 110 may be implemented by the processor 101 and the memory 102. The control unit 110 performs various control processes in the network node 10. For example, the control unit 110 controls communication with other nodes (e.g., other network nodes 10 and RAN node 30) via the communication unit 120. That is, the control unit 110 controls the transmission and reception of data / information / messages via the communication unit 120.

[0031] The communication unit 120 includes a transmitter / receiver 103. In other words, the communication unit 120 is implemented by the transmitter / receiver 103. The communication unit 120 communicates with other network nodes 10 and RAN nodes 30 by transmitting and receiving signals.

[0032] By operating the control unit 110, various processes of the network node 10 in this embodiment are executed.

[0033] Next, refer to Figure 4 This describes the physical configuration of terminal device 20. For example... Figure 4 As shown, the terminal device 20 includes a processor 201, a memory 202, an input / output interface 203, a transmitter / receiver 204, and an antenna 205 as hardware elements. These elements in the terminal device 20 are interconnected via an internal bus. Alternatively, the terminal device 20 may also include... Figure 4 Hardware elements other than those shown.

[0034] The processor 201 is a computing element that implements various functions of the terminal device 20. The processor 201 may be a CPU, or may also include other processors such as a GPU.

[0035] The memory 202 is composed of at least one storage medium such as RAM. The memory 202 is an element that temporarily or permanently stores programs and data for performing various processes in the terminal device 20. The programs include one or more commands for the actions of the terminal device 20. The processor 201 implements the functions of the terminal device 20 by expanding the programs stored in the memory 202 into the memory 202 and / or system memory (not shown) and executing them.

[0036] The input / output interface 203 is an interface that receives operations from the terminal device 20 and provides them to the processor 201, and presents various information to the user. The input / output interface 203 is, for example, a touch panel.

[0037] Transmitter / receiver 204 is circuitry that performs various signal processing steps to enable wireless communication, including a baseband processor and RF circuitry. Transmitter / receiver 204 transmits and receives radio signals via antenna 205 to RAN node 30.

[0038] Next, refer to Figure 5 This describes the logical configuration of terminal device 20. For example... Figure 5 As shown, the terminal device 20 includes a control unit 210 and a communication unit 220 as functional blocks. The communication unit 220 includes at least one transmitting unit 121 and at least one receiving unit 122.

[0039] The control unit 210 may include at least one processor 201 and at least one memory 202. In other words, the control unit 210 may be implemented by the processor 201 and the memory 202. The control unit 210 performs various control processes in the terminal device 20. For example, the control unit 210 controls wireless communication with the RAN node 30 via the communication unit 220. That is, the control unit 210 controls the transmission and reception of data / information / messages via the communication unit 220.

[0040] The communication unit 220 includes a transmitter / receiver 204 and an antenna 205. In other words, the communication unit 220 is implemented by the transmitter / receiver and the antenna 205. The communication unit 220 communicates wirelessly with the RAN node 30 by transmitting and receiving wireless signals.

[0041] By operating the control unit 210, various processes of the terminal device 20 in this embodiment are executed.

[0042] 1.2 Network Slicing Next, refer to Figure 6 This section provides an overview of network slicing. Each network slice is established by virtually segmenting the network to enable terminal device 20 to communicate with DN40 via RAN node 30 and network node (UPF) 10. Within a network slice, data is transmitted by establishing a Protocol Data Unit (PDU) session between terminal device 20 and network node 10.

[0043] like Figure 6 As shown, regarding network slicing, multiple network slices are established between terminal device 20 and network node 10. Each network slice is identified by S-NSSAI.

[0044] The S-NSSAI data format includes Slice / Service type (SST) and Slice Differentiator (SD).

[0045] SSTs define the purpose of network slices, including standard SSTs and specific SSTs. Standard SSTs specify eMBB, URLLC, Massive Internet of Things (MIoT), Vehicle-to-X (V2X), and High-performance Machine-Type Communication (HMTC). Specific SSTs specify purposes freely set by operators. SDs are identifiers used to separate multiple network slices within the same SST.

[0046] 1.3 Network Slice Registration Terminal device 20 maintains an S-NSSAI that can be used within a Public Land Mobile Network (PLMN). This S-NSSAI is referred to as a Configured S-NSSAI. Terminal device 20 registers the S-NSSAI by executing a registration request against AMF10a. (See reference...) Figure 7 This is an example illustrating the S-NSSAI registration process.

[0047] First, terminal device 20 sends a Registration Request message to RAN node 30 (step S701). The Registration Request message includes S-NSSAI. This S-NSSAI is referred to as Requested S-NSSAI.

[0048] Next, RAN node 30 selects AMF10a based on request S-NSSAI and sends a registration request message to the selected AMF10a (step S702).

[0049] Next, AMF10a selects UDM / UDR10c and registers the S-NSSAI into the selected UDM / UDR10c (step S703). This S-NSSAI is referred to as the Subscribed S-NSSAI. The Subscribed S-NSSAI is stored in the UDM / UDR10c as Subscription Data.

[0050] Next, AMF10a notifies the terminal device 20 of the registered S-NSSAI (step S703). This S-NSSAI is referred to as the Allowed S-NSSAI.

[0051] In this way, the terminal device 20 can establish a PDU session with the UPF10b corresponding to the network slice, and communicate with the DN40 through the established PDU session.

[0052] 1.4 Emergency Dedicated Network Slicing Non-Patent Document 1 describes an emergency service where, in the event of an emergency, IMS service sessions are prioritized over normally registered UEs for UEs registered for emergency use. While UEs registered for emergency use can prioritize services such as calls, they cannot exclusively use the network. It is foreseeable that, in the event of an unprecedented large-scale disaster, a significant amount of traffic will be generated in networks covering the affected areas.

[0053] In the aforementioned situations, even if sessions are prioritized for UEs registered for emergency purposes, the UEs registered for emergency purposes may still be unable to make sufficient calls because services are generated within the network by normally registered UEs. On the other hand, because sessions are prioritized for UEs registered for emergency purposes, normally registered UEs may be almost unable to make calls.

[0054] In view of the above, in the event of an emergency, it is preferable to separate the network between normally registered terminal devices and terminal devices registered for emergency use.

[0055] In the first embodiment, in an emergency, a network slice is created that is only permitted to be used by terminal devices 20 registered for emergency purposes; that is, a network slice allocated for emergency purposes. Hereinafter, such a network slice is referred to as an Emergency Dedicated Network Slice or a first network slice. The Emergency Dedicated Network Slice is not used under normal circumstances, i.e., when no emergency occurs. Furthermore, network slices not allocated for emergency purposes are referred to as Normal Network Slices or second network slices.

[0056] Emergency-dedicated network slices can be identified, for example, through a standard SST or a specific SST within the SST in S-NSSAI. For instance, in an emergency-dedicated network slice, a standard SST or a specific SST can be assigned the value "X: Emergency Purpose". This allows for the identification of emergency-dedicated network slices.

[0057] In addition, emergency dedicated network slices can be identified not only by the SST value, but also by other data fields.

[0058] Next, refer to Figure 8 This example illustrates the S-NSSAI registration process under normal circumstances. As mentioned above, emergency dedicated network slices are not used under normal circumstances. Figure 8 In the process shown, registration for the emergency dedicated network slice is normally rejected. Thus, by not using the emergency dedicated network slice under normal circumstances, the terminal device 20 registered for emergency use can immediately and exclusively use the emergency dedicated network slice in the event of an emergency.

[0059] First, terminal device 20 sends a Registration Request message to RAN node 30 (step S801). The Registration Request message includes S-NSSAI. This S-NSSAI is referred to as Requested S-NSSAI. The S-NSSAI included in the Registration Request message includes a value in SST or similar indicating that it is an emergency dedicated network slice. Alternatively, in addition to S-NSSAI, the Registration Request message may include an indicator indicating that the network slice requested for registration is an emergency dedicated network slice.

[0060] Next, RAN node 30 selects AMF10a based on request S-NSSAI and sends a registration request message to the selected AMF10a (step S802).

[0061] AMF10a determines whether the requested S-NSSAI is an emergency dedicated network slice based on the SST value included in the registration request message (step S803). If the requested S-NSSAI is an emergency dedicated network slice, the process transitions to step S804. If the requested S-NSSAI is not an emergency dedicated network slice, the process transitions to step S806.

[0062] In step S804, AMF10a rejects S-NSSAI's registration. Then, AMF10a sends a registration rejection message to terminal device 20 (step S805).

[0063] In step S806, AMF10a selects UDM / UDR10c and registers S-NSSAI as a subscription to the selected UDM / UDR10c. The subscription S-NSSAI is stored in UDM / UDR10c as subscription data. Then, AMF10a notifies the terminal device 20 that S-NSSAI is allowed (step S807).

[0064] Thus, under normal circumstances, the use of the emergency dedicated network slice is denied. Therefore, in the event of an emergency, the terminal device 20 registered for emergency use can immediately and exclusively use the emergency dedicated network slice.

[0065] Furthermore, this embodiment illustrates an example of AMF10a performing the processes in steps 803 to S807, but is not limited to such an example. The processes in steps 803 to S807 can be performed individually or collaboratively by other network nodes 10, such as PCF10g.

[0066] Next, refer to Figure 9 This section provides an example illustrating the S-NSSAI registration process in an emergency. In this embodiment, emergency vehicles and emergency communication terminals are grouped within each prefecture or municipality, and groups of emergency-use terminal devices 20 are registered as emergency-use terminal devices. Hereinafter, terminal devices 20 registered as emergency-use devices are referred to as emergency-use terminal devices 20. Terminal devices 20 not registered as emergency-use devices are referred to as normal terminal devices 20 or non-emergency-use terminal devices 20.

[0067] Emergency-use terminal devices 20 are managed by AF10d as a group. Emergency-use terminal devices 20 can be identified by identifiers (UE-ID) such as the International Mobile Subscriber Identity (IMSI). Additionally, emergency-use terminal devices 20 can be registered in subscription data. In this case, the subscription data includes data indicating that the terminal device 20 is for emergency use.

[0068] In the event of an emergency, AF10d requests the group of emergency-use terminal devices 20 to use the emergency-dedicated network slice. In this way, the group of emergency-use terminal devices 20 can exclusively use the emergency-dedicated network slice in each area of ​​each prefecture or municipality.

[0069] First, AF10d sends a message requesting the use of an emergency dedicated network slice to each terminal device in the group of emergency use terminal devices 20 it manages (step S901). In response to the request message, each of the emergency use terminal devices 20 sends a response message to AF10d (step S902).

[0070] Furthermore, considering that at the time of step S901, each terminal device in the group of emergency-use terminal devices 20 is using a normal network slice, AF10d sends a message to each terminal device in the group of emergency-use terminal devices 20 requesting a switch from the normal network slice to the emergency-dedicated network slice. Then, in response to the message in step S902, AF10d uses the API service via NEF10h to send a message to SMF10g requesting the termination of the PDU session established with the emergency-use terminal device 20 through the normal network slice. SMF10f responds to this request message and terminates the PDU session established with the emergency-use terminal device 20.

[0071] Next, AF10d uses the API service via NEF10h to send a message to PCF10g requesting that the group of emergency purpose terminal devices 20 use the emergency dedicated network slice (step S903).

[0072] Next, PCF10g confirms that each terminal device in the group of emergency-use terminal devices 20 is a terminal device registered for emergency use based on the IMSI and the identifier (UE-ID) of the terminal device 20 registered in the HRL (step S904). Alternatively, PCF10g may also confirm that each terminal device in the group of emergency-use terminal devices 20 is a terminal device registered for emergency use based on subscription data registered in the UDM / UDR.

[0073] Furthermore, in the process of step S904, if the emergency use terminal device 20 is not a terminal device registered for emergency use, PCF10g may send a registration rejection message (not shown) to AF10d.

[0074] Next, PCF10g uses the API service via NEF10h to send a response message to AF10d (step S905).

[0075] Next, AF10d uses the API service via NEF10h to send a message to NSSF10e requesting the selection of an emergency dedicated network slice. NSSF10e responds to the request message and selects an emergency dedicated network slice (step S906).

[0076] Emergency dedicated network slices can be pre-assigned to each AF10d, i.e., each area of ​​each prefecture or municipality. In this case, in step S906, the request message sent by AF10d to NSSF10e includes S-NSSAI. The S-NSSAI included in the registration request message includes a value in SST or the like indicating that it is an emergency dedicated network slice. Alternatively, in addition to S-NSSAI, the registration request message may include an indicator indicating that the network slice requested for registration is an emergency dedicated network slice.

[0077] Alternatively, in the process of step S906, NSSF10e can select a network slice that has been assigned as an emergency dedicated network slice from among the S-NSSAIs registered in UDM / UDR10c.

[0078] Next, NSSF10e sends a message to SMF10f requesting the establishment of a PDU session through the selected emergency dedicated network slice. SMF10f responds to this request message and establishes a PDU session for the emergency dedicated network slice selected in step S906 (step S907). SMF10f then sends a message indicating the establishment of a PDU session to each terminal device in the group of emergency use terminal devices 20. Thus, a PDU session through the emergency dedicated network slice is established for the group of emergency use terminal devices 20.

[0079] Thus, in the event of an emergency, the group of emergency-use terminal devices 20 can exclusively use emergency-dedicated network slices, thereby enabling network separation between normal terminal devices 20 and emergency-use terminal devices 20.

[0080] exist Figure 9 In the example shown, AF10d requests the use (switching) of a network slice for the group of emergency-use terminal devices 20. It is conceivable that in an emergency, the users of emergency-use terminal devices 20 may not be aware of the need to use the dedicated emergency network slice. In this embodiment, AF10d manages emergency-use terminal devices 20 as a group and requests a network slice switch for the entire group. Thus, even under the aforementioned scenario, each terminal device in the group of emergency-use terminal devices 20 can use the dedicated emergency network slice in an emergency.

[0081] The above describes in Figure 9In the process shown, at the time point S901, the PDU session established through the normal network slice is terminated. Alternatively, if the emergency terminal device 20 supports a User Equipment Route Selection Policy (URSP), a PDU session through the emergency dedicated network slice can be established without terminating the PDU session established through the normal network slice.

[0082] When URSP is supported for Emergency Use Terminal Device 20, it can select and use any one of the multiple network slices specified in the URSP rules. The URSP rules specify the network slices and their corresponding PDU sessions. In this case, PCF10g can add emergency-specific network slices to the URSP rules. Since the URSP rules are sent to Emergency Use Terminal Device 20 via AMF10a, it can select the added emergency-specific network slice based on the URSP rules. Thus, Emergency Use Terminal Device 20 can use emergency-specific network slices without interrupting PDU sessions established through normal network slices. Such alternatives also apply to those described later. Figure 10 , Figure 11 as well as Figure 12 The process of explanation.

[0083] In addition, Figure 9 In the process shown, PCF10g, NSSF10e, and SMF10f collaboratively establish a PDU session upon a request from AFd, but this is not an exclusive example. A PDU session can also be established in response to a request from terminal device 20. (See reference...) Figure 10 This indicates that as Figure 9 The example shown is a variant of the S-NSSAI registration process in an emergency situation. Figure 10 During the process shown, a PDU session is established in response to a request from terminal device 20.

[0084] First, AF10d sends a message requesting the use of an emergency dedicated network slice to each terminal device in the group of emergency use terminal devices 20 it manages (step S1001). In response to the request message, each of the emergency use terminal devices 20 sends a response message to AF10d (step S1002).

[0085] Furthermore, considering that at the time of step S1001, each terminal device in the group of emergency use terminal devices 20 is using a normal network slice, AF10d sends a message to each terminal device in the group of emergency use terminal devices 20 requesting a switch from the normal network slice to the emergency dedicated network slice. Then, in response to the message in step S1002, AF10d uses the API service via NEF10h to send a message to SMF10g requesting the termination of the PDU session established with the emergency use terminal device 20 through the normal network slice. SMF10f responds to this request message and terminates the PDU session established with the emergency use terminal device 20.

[0086] Next, each of the emergency-use terminal devices 20 sends a message requesting the use of an emergency dedicated network slice to the PCF10g via the RAN node 30 (not shown) (step S1003). Furthermore, in the processing of step S1003, with... Figure 9 Similarly, in step S903 shown, AF10d can send a request message to PCF10g.

[0087] Next, PCF10g confirms that each terminal device in the group of emergency-use terminal devices 20 is a terminal device registered for emergency use based on the IMSI and the identifier (UE-ID) of the terminal device 20 registered in the HRL (step S1004). Alternatively, PCF10g may also confirm that each terminal device in the group of emergency-use terminal devices 20 is a terminal device registered for emergency use based on subscription data registered in the UDM / UDR.

[0088] Furthermore, in the process of step S1004, if the emergency use terminal device 20 is not a terminal device registered for emergency use, the PCF10g may send a registration rejection message (not shown) to each terminal device in the group of emergency use terminal devices 20.

[0089] Next, PCF10g sends response messages to each of the emergency use terminal devices 20 via RAN node 30 (not shown) (step S1005).

[0090] Next, each terminal device in the group of emergency use terminal devices 20 sends a request message to NSSF10e requesting the selection of an emergency dedicated network slice. NSSF10e responds to the request message and selects an emergency dedicated network slice (step S1006). Furthermore, in the processing of step S1006, with... Figure 9 Similarly, in step S906 shown, AF10d can send a request message to NSSF10e.

[0091] When an emergency dedicated network slice is pre-assigned to each AF10d, in step S1006, the request message sent by each terminal device in the group of emergency use terminal devices 20 to NSSF10e includes S-NSSAI. The S-NSSAI included in the registration request message includes a value indicating, such as SST, that it is an emergency dedicated network slice. Alternatively, in addition to S-NSSAI, the registration request message may include an indicator indicating that the network slice requested for registration is an emergency dedicated network slice.

[0092] Alternatively, in the process of step S1006, NSSF10e can select a network slice that has been assigned as an emergency dedicated network slice from among the S-NSSAIs registered in UDM / UDR10c.

[0093] Next, NSSF10e sends a request message to SMF10f requesting the establishment of a PDU session through the selected emergency dedicated network slice. SMF10f responds to this request message and establishes a PDU session for the emergency dedicated network slice selected in step S1006 (step S1007). SMF10f then sends a message indicating the establishment of a PDU session to each terminal device in the group of emergency use terminal devices 20. Thus, a PDU session through the emergency dedicated network slice is established for the group of emergency use terminal devices 20.

[0094] pass Figure 10 As shown in the process, when an emergency occurs, the group of emergency-use terminal devices 20 can also exclusively use emergency-dedicated network slices, thereby enabling network separation between normal terminal devices 20 and emergency-use terminal devices 20.

[0095] In addition, Figure 9 as well as Figure 10 In the illustrated process, the S-NSSAI registration process is executed via a trigger from the AF10d of the emergency use terminal device 20. However, the S-NSSAI registration process can also be executed via a trigger from the terminal device 20, without going through the AF10d. In this case, Figure 10 In the process shown, only steps S1003 to S1007 are executed.

[0096] The first embodiment has been described as above. In the first embodiment, the network is separated between the normal terminal device 20 and the emergency-use terminal device 20. Furthermore, the emergency-dedicated network slice is not used under normal circumstances, but is only used by the emergency-use terminal device 20 in emergency situations. Thus, when an emergency occurs, the emergency-use terminal device 20 can immediately and exclusively use the emergency-dedicated network slice.

[0097] Furthermore, in the first embodiment... Figure 9 as well as Figure 10 The execution entities of the various processes shown in the process are PCF10g, NSSF10e, and SMF10g, which are merely examples. In the process described in the first embodiment, a portion of the processing is executed by one or more of the network nodes 10.

[0098] 2. Second Implementation Method Next, the second embodiment will be described. In the second embodiment, the emergency dedicated network slice described in the first embodiment is also used under normal circumstances. Under normal circumstances, the emergency dedicated network slice can be used not only by the emergency purpose terminal device 20 but also by the normal terminal device 20. In the event of an emergency, only the emergency purpose terminal device 20 is allowed to use the emergency dedicated network slice.

[0099] Under normal circumstances, according to Figure 7 The process illustrated establishes a PDF session via an emergency-dedicated network slice based on requests from both the emergency-use terminal device 20 and the normal terminal device 20. This allows for efficient resource utilization by enabling the use of the emergency-dedicated network slice even under normal circumstances.

[0100] Reference Figure 11 This example illustrates the S-NSSAI registration process in an emergency. In this embodiment, emergency vehicles and emergency communication terminals are grouped in each area of ​​each prefecture or municipality, and groups of emergency-use terminal devices 20 are registered.

[0101] exist Figure 11 In the process shown, the emergency dedicated network slice is being used by the normal terminal device 20 until an emergency occurs.

[0102] First, AF10d sends a message requesting the use of an emergency dedicated network slice to each terminal device in the group of emergency use terminal devices 20 it manages (step S1101). In response to the request message, each of the emergency use terminal devices 20 sends a response message to AF10d (step S1102).

[0103] Furthermore, when each terminal device in the group of emergency use terminal devices 20 is using a normal network slice at the time point in step S1101, AF10d sends a message requesting a switch to the emergency dedicated network slice. Then, in response to the message in step S1102, AF10d uses the API service via NEF10h to send a message to SMF10g requesting the termination of the PDU session established with the emergency use terminal device 20 through the normal network slice. SMF10f responds to this request message and terminates the PDU session established with the emergency use terminal device 20.

[0104] Next, AF10d uses the API service via NEF10h to send a message to PCF10g requesting that the group of emergency purpose terminal devices 20 use the emergency dedicated network slice (step S1103).

[0105] Next, PCF10g confirms that each terminal device in the group of emergency-use terminal devices 20 is a terminal device registered for emergency use based on the IMSI and the identifier (UE-ID) of the terminal device 20 registered in the HRL (step S1104). Alternatively, PCF10g may also confirm that each terminal device in the group of emergency-use terminal devices 20 is a terminal device registered for emergency use based on subscription data registered in the UDM / UDR.

[0106] Furthermore, in the process of step S1104, if the emergency use terminal device 20 is not a terminal device registered for emergency use, PCF10g may send a registration rejection message (not shown) to AF10d.

[0107] Next, PCF10g uses the API service via NEF10h to send a response message to AF10d (step S1105).

[0108] Next, AF10d uses the API service via NEF10h to send a request message to NSSF10e to select an emergency dedicated network slice. NSSF10e responds to the request message and selects an emergency network slice (step S1106).

[0109] When an emergency dedicated network slice is pre-assigned to each AF10d, in step S1106, the request message sent by each terminal device in the group of emergency use terminal devices 20 to NSSF10e includes S-NSSAI. The S-NSSAI included in the registration request message includes a value indicating, such as SST, that it is an emergency dedicated network slice. Alternatively, in addition to S-NSSAI, the registration request message may include an indicator indicating that the network slice requested for registration is an emergency dedicated network slice.

[0110] Alternatively, in the process of step S1106, NSSF10e can select a network slice assigned as an emergency dedicated network slice from the S-NSSAI registered in UDM / UDR10c. As described above, assume that the emergency dedicated network slice selected by either method is being used by the normal terminal device 20.

[0111] Next, NSSF10e sends a message to SMF10f requesting the termination of the PDU session established with the normal terminal device 20 through the selected emergency dedicated network slice. SMF10f responds to the request message and terminates the PDU session established with the normal terminal device 20 (step S1107). In the process of step S1107, network nodes 10 such as AF10d can send a message to the terminal device 20 notifying it of a switch to another network slice due to a disaster before terminating the PDU session.

[0112] Network nodes 10 such as AMF10a, PCF10e, or SMF10f can determine whether it is a PDU session established for a normal terminal device 20 based on the identifier (UE-ID) of the terminal device 20 such as the IMSI registered in the HRL, or the subscription data registered in the UDM / UDR.

[0113] Next, NSSF10e sends a request message to establish a PDU session through the selected emergency dedicated network slice. SMF10f responds to this request message and establishes a PDU session for the emergency dedicated network slice selected in step S1106 (step S1108). SMF10f sends a message indicating that a PDU session has been established to each terminal device in the group of emergency use terminal devices 20. Thus, the PDU session established with the normal terminal devices 20 is terminated, while a PDU session through the emergency dedicated network slice is established for the group of emergency use terminal devices 20.

[0114] Thus, by allowing the use of emergency dedicated network slices under normal circumstances, and allowing only emergency-use terminal devices 20 to use emergency dedicated network slices in emergency situations, resources can be utilized effectively.

[0115] exist Figure 11 In the process shown, PCF10g, NSSF10e, and SMF10f cooperate to terminate and establish a PDU session in response to a request from AFd, but this is not an exclusive example. The PDU session can also be terminated and established in response to a request from terminal device 20. (See reference...) Figure 12 This indicates that as Figure 11 The example shown is a variant of the S-NSSAI registration process in an emergency situation. Figure 12 During the process shown, a PDU session is established in response to a request from terminal device 20 to disconnect.

[0116] First, AF10d sends a message requesting the use of an emergency dedicated network slice to each terminal device in the group of emergency use terminal devices 20 it manages (step S1201). In response to the request message, each of the emergency use terminal devices 20 sends a response message to AF10d (step S1202).

[0117] Furthermore, at the time point S1201, if each terminal device in the group of emergency use terminal devices 20 is using a normal network slice, AF10d sends a message requesting a switch to the emergency dedicated network slice. Then, in response to the message in step S1202, AF10d uses the API service via NEF10h to send a message to SMF10g requesting the termination of the PDU session established with the emergency use terminal device 20 through the normal network slice. SMF10f responds to this request message and terminates the PDU session established with the emergency use terminal device 20.

[0118] Next, each of the emergency-use terminal devices 20 sends a message requesting the use of an emergency dedicated network slice to the PCF10g via the RAN node 30 (not shown) (step S1203). Furthermore, in the processing of step S1203, with... Figure 11 Similarly, in step S1103 shown, AF10d can send a request message to PCF10g.

[0119] Next, PCF10g confirms that each terminal device in the group of emergency-use terminal devices 20 is a terminal device registered for emergency use based on the IMSI and the identifier (UE-ID) of the terminal device 20 registered in the HRL (step S1204). Alternatively, PCF10g may also confirm that each terminal device in the group of emergency-use terminal devices 20 is a terminal device registered for emergency use based on subscription data registered in the UDM / UDR.

[0120] Furthermore, in the process of step S1204, if the emergency use terminal device 20 is not a terminal device registered for emergency use, the PCF10g may send a registration rejection message (not shown) to each terminal device in the group of emergency use terminal devices 20.

[0121] Next, PCF10g sends response messages to each of the emergency use terminal devices 20 via RAN node 30 (not shown) (step S1205).

[0122] Next, each terminal device in the group of emergency use terminal devices 20 sends a request message to NSSF10e requesting the selection of an emergency dedicated network slice. NSSF10e responds to the request message and selects an emergency dedicated network slice (step S1206). Furthermore, in the processing of step S1206, with... Figure 9 Similarly, in step S1106 shown, AF10d can send a request message to NSSF10e.

[0123] When an emergency dedicated network slice is pre-assigned to each AF10d, in step S1206, the request message sent by each terminal device in the group of emergency use terminal devices 20 to NSSF10e includes S-NSSAI. The S-NSSAI included in the registration request message includes a value indicating, such as SST, that it is an emergency dedicated network slice. Alternatively, in addition to S-NSSAI, the registration request message may include an indicator indicating that the network slice requested for registration is an emergency dedicated network slice.

[0124] Alternatively, in the process of step S1006, NSSF10e can select a network slice assigned as an emergency dedicated network slice from the S-NSSAI registered in UDM / UDR10c. As described above, assume that the emergency dedicated network slice selected by either method is being used by the normal terminal device 20.

[0125] Next, NSSF10e sends a message to SMF10f requesting the termination of the PDU session established with the normal terminal device 20 through the selected emergency dedicated network slice. SMF10f responds to the request message and terminates the PDU session established with the normal terminal device 20 (step S1207). In the processing of step S1207, network nodes 10 such as AF10d can send a message to the terminal device 20 notifying it of a switch to another network slice due to a disaster before terminating the PDU session.

[0126] Network nodes 10 such as AMF10a, PCF10e, or SMF10f can determine whether it is a PDU session established for a normal terminal device 20 based on the identifier (UE-ID) of the terminal device 20 such as the IMSI registered in the HRL, or the subscription data registered in the UDM / UDR.

[0127] Next, NSSF10e sends a request message to SMF10f requesting the establishment of a PDU session through the selected emergency dedicated network slice. SMF10f responds to this request message and establishes a PDU session for the emergency dedicated network slice selected in step S1206 (step S1208). SMF10f then sends a message indicating the establishment of a PDU session to each terminal device in the group of emergency use terminal devices 20. Thus, a PDU session through the emergency dedicated network slice is established for the group of emergency use terminal devices 20.

[0128] pass Figure 12 The process shown also allows for efficient resource utilization by enabling the use of emergency dedicated network slices under normal circumstances, while allowing only emergency-use terminal devices 20 to use emergency dedicated network slices in emergency situations.

[0129] The second embodiment has been described above. In the second embodiment, the network is also separated between the normal terminal device 20 and the emergency-use terminal device 20. Furthermore, an emergency-dedicated network slice is used under normal circumstances, while in an emergency, the emergency-dedicated network slice is used only by the emergency-use terminal device 20. This allows for efficient resource utilization.

[0130] Furthermore, in the first embodiment... Figure 11 as well as Figure 12 The execution entities of the various processes shown in the process are PCF10g, NSSF10e, and SMF10g, which are merely examples. In the process described in the first embodiment, a portion of the processing is executed by one or more of the network nodes 10.

[0131] 3. Third Implementation Method Next, the third implementation method will be described. In the third implementation method, an emergency dedicated network slice is selected based on the service requirements of the network in the disaster-stricken area.

[0132] For example, the network slices used in an emergency vary depending on the number of terminal devices 20 present in the specific area where the disaster occurred. Depending on the situation, there is also a possibility of congestion in the selected emergency dedicated network slice due to the number of UEs causing the congestion.

[0133] When disasters such as earthquakes, tsunamis, volcanic eruptions, and floods occur, the disaster-stricken area is notified to the network. In the third embodiment, based on such notification, the area where the disaster occurred is determined, and service requirements for the network are determined based on factors such as the number of terminal devices 20 within that area. Then, an emergency dedicated network slice corresponding to the service requirements is selected.

[0134] Reference Figure 13 This describes the process of selecting an emergency dedicated network slice involved in this implementation. Figure 13 The process shown is also applied to Figure 9 The process shown Figure 10 The process shown Figure 11 The process shown and Figure 12 Any of the processes shown.

[0135] exist Figure 13 The process shown is applied to Figure 9 In the case of the process shown, Figure 13 The process shown illustrates Figure 9 The details of step S906 in the process shown are as follows. Similarly, in Figure 13 The process shown is applied to Figure 10 In the case of the process shown, Figure 13 The process shown illustrates Figure 10 The details of step S1006 in the process shown are as follows. Similarly, in Figure 13 The process shown is applied to Figure 11 In the case of the process shown, Figure 13 The process shown illustrates Figure 11 The details of step S1106 in the process shown are as follows. Similarly, in Figure 13 The process shown is applied to Figure 12 In the case of the process shown, Figure 13 The process shown illustrates Figure 12 Details of step S1206 in the process shown.

[0136] First, NSSF10e sends a message to AMF10a requesting a calculation of the number of terminal devices 20 present in the disaster-stricken area. AMF10a responds to the request message and calculates the number of terminal devices 20 present in the area (step S1301).

[0137] The area where the disaster occurred is notified by an external server (not shown) that provides emergency earthquake early warnings and information about the location of the disaster. AMF10a calculates the number of terminal devices 20 present in the area based on the number of terminal devices 20 registered in UDM / UDR10c.

[0138] Next, NSSF10e determines the service requirements of the network slice to be used in the disaster-stricken area based on the number of terminal devices 20 (step S1302). Service requirements can be determined, for example, based on the QoS parameters shown in Table 1. The QoS parameters shown in Table 1 are specified in the 3GPP technical specifications. [Table 1] Table 1: QoS Parameters

[0139] NSSF10e determines service requirements based on the number of terminal devices 20, using the QoS parameters shown in Table 1. Service requirements can be stored as a service requirement list in association with the number of terminal devices 20 and the QoS parameters shown in Table 1. Table 2 shows an example of a service requirement list. [Table 2] Table 2: List of Service Requirements

[0140] Next, NSSF10e selects an emergency dedicated network slice that meets the service requirements determined in step S1302 (step S1303). This selection is made by choosing an S-NSSAI from those S-NSSAIs registered in UDM / UDR10c.

[0141] To select an emergency dedicated network slice that meets the service requirements, QoS values ​​corresponding to the QoS provided for each network slice can be stored in UDM / UDR10c. These QoS values ​​can be stored as a QoS list for each network slice in association with S-NSSAI, using the QoS parameters shown in Table 1. Table 3 shows an example of a QoS list. [Table 3] Table 3: QoS List

[0142] By storing the QoS list in UDM / UDR10c, it is possible to appropriately select emergency dedicated network slices that meet service requirements. Furthermore, by storing the QoS list in UDM / UDR10c, the aforementioned selections can be made at detailed QoS levels.

[0143] Thus, by selecting an emergency-dedicated network slice based on the service requirements of the network in the disaster-stricken area, the emergency-use terminal device 20 can use the appropriate network slice in an emergency.

[0144] Furthermore, in this embodiment, network nodes 10 such as AMF10a determine service requests based on the number of registered UEs, but are not limited to this example. For instance, AF10d may determine service requests based on the number of terminal devices 20 it manages.

[0145] The third embodiment has been described above. In the third embodiment, an emergency-dedicated network slice is selected based on the service requirements of the network in the disaster-stricken area. Thus, in the event of an emergency, the emergency-use terminal device 20 can use an appropriate network slice that meets the service requirements.

[0146] Furthermore, in the third embodiment, Figure 13 The execution entities of the various processes shown in the process are AMF10a and NSSF10e, which are merely examples. In the process described in the first embodiment, a portion of the processing is executed by one or more of the network nodes 10.

[0147] 4. Variation Example The above describes the methods for implementing this embodiment, but this embodiment is not limited to the above embodiments. It should be understood that the above embodiments are merely examples and various variations are possible.

[0148] The words, phrases, etc., used in the above embodiments are merely examples and can be replaced with substantially the same or similar expressions. In particular, since the technologies involved in the above embodiments are related to technical specifications, the expressions in the above embodiments can be replaced with substantially the same or similar expressions in technical specifications (e.g., the technical specifications cited in this application specification).

[0149] In the above embodiments, the information sent and received may include the same or different messages or elements already described in the technical specifications, or it may include newly defined messages or elements. In the above embodiments, the information sent and received may use different layers and / or different channels than those described in the above embodiments.

[0150] The manner and / or function provided by the apparatus described in the above embodiments can be provided by software recorded in a physical memory device and a computer executing the software, by software alone, by hardware alone, or by a combination thereof. For example, in the case where any of the above-described apparatuses is provided by electronic circuitry as hardware, it can be provided by digital circuitry or analog circuitry including multiple logic circuits.

[0151] The apparatus described in the above embodiments executes a program stored in a non-transitory tangible storage medium. By executing this program, the method corresponding to the program is performed.

[0152] 5. Postscript The above-described embodiments and variations may be described in whole or in part as in the following notes, but are not limited to the content of the following notes. Hereinafter, the relationship of a note belonging to a note belonging to a note belonging to a note belonging to a note belonging to a note is expressed. All the subordinate relationships of notes expressed below are included in the above-described embodiments.

[0153] (Postscript 1) A network node includes a control unit and a communication unit. The aforementioned communication unit is configured to, in an emergency, receive a message requesting a terminal device to use a first network slice, wherein the first network slice is a network slice allocated for emergency purposes. The aforementioned control unit is configured to, in an emergency, To determine whether the aforementioned terminal device has been registered for emergency use, If the aforementioned terminal device is registered for emergency use, a PDU session is established for the aforementioned terminal device through the aforementioned first network slice. The aforementioned request is rejected if the terminal device has not been registered for emergency use.

[0154] (Postscript 2) According to the network node described in Appendix 1, the aforementioned communication unit is further configured to, under normal circumstances, receive messages requesting the aforementioned terminal device to use the aforementioned first network slice. The aforementioned control unit is further configured to reject the aforementioned request under normal circumstances.

[0155] (Note 3) According to the network node described in Appendix 1, the aforementioned communication unit is further configured to, under normal circumstances, receive messages requesting the aforementioned terminal device to use the aforementioned first network slice. The aforementioned control unit is further configured to register the aforementioned first network slice under normal circumstances.

[0156] (Postscript 4) According to the network node described in Appendix 3, the aforementioned control unit is further configured to disconnect the aforementioned PDU session established under normal circumstances.

[0157] (Note 5) According to any one of Appendices 1 to 4, when the aforementioned terminal device is using a second network slice that has not been allocated for emergency purposes under normal circumstances, the network node is... The aforementioned communication unit is further configured to, in an emergency, receive a message requesting the aforementioned terminal device to switch from the aforementioned second network slice to the aforementioned first network slice. The aforementioned control unit is further configured to, in an emergency, disconnect the PDU session established with the aforementioned terminal device through the aforementioned second network slice.

[0158] (Note 6) A network node, comprising a group of multiple terminal devices, is registered for the aforementioned first network slice according to any one of Appendices 1 to 5. The aforementioned communications unit is further configured to, in an emergency, receive messages requesting each terminal device in the aforementioned group to use the aforementioned first network slice.

[0159] (Note 7) According to the network node described in Appendix 6, the aforementioned communication unit is further configured to send a message requesting the use of the first network slice to each terminal device in the aforementioned group.

[0160] (Note 8) According to any one of the appendices 1 to 7, the aforementioned control unit is further configured to determine whether the aforementioned terminal device is registered for emergency use based on the identifier of the aforementioned terminal device.

[0161] (Note 9) According to any one of the appendices 1 to 7, the aforementioned control unit is further configured to determine, based on the aforementioned subscription data, whether the aforementioned terminal device has been registered for emergency use.

[0162] (Postscript 10) According to any one of Appendices 1 to 9, the aforementioned control unit is further configured to, in an emergency... Determine the network service requirements in the disaster-affected area. Based on the aforementioned service requirements, the first network slice is selected from the network slices allocated for emergency purposes.

[0163] (Postscript 11) According to the network node described in Appendix 10, the aforementioned control unit is further configured as follows: Calculate the number of terminal devices registered for emergency use that exist within the aforementioned area. The aforementioned service requirements are determined based on the number of terminal devices mentioned above.

[0164] (Postscript 12) One method, executed by a network node, includes: in emergency situations, Receive a message requesting the terminal device to use a first network slice, wherein the first network slice is a network slice allocated for emergency purposes; Determine whether the aforementioned terminal device has been registered for emergency use; In the event that the aforementioned terminal device is registered for emergency use, a PDU session is established for the aforementioned terminal device through the aforementioned first network slice; and The aforementioned request is rejected if the terminal device has not been registered for emergency use.

[0165] (Postscript 13) A program that, when executed, causes the processor in a network node to perform the following: Receive a message requesting the terminal device to use a first network slice, wherein the first network slice is a network slice allocated for emergency purposes; Determine whether the aforementioned terminal device has been registered for emergency use; In the event that the aforementioned terminal device is registered for emergency use, a PDU session is established for the aforementioned terminal device through the aforementioned first network slice; and The aforementioned request is rejected if the terminal device has not been registered for emergency use.

[0166] (Postscript 14) A computer-readable, non-transient tangible recording medium storing a program that, when executed, causes a processor in a network node to perform the following: Receive a message requesting the terminal device to use a first network slice, wherein the first network slice is a network slice allocated for emergency purposes; Determine whether the aforementioned terminal device has been registered for emergency use; In the event that the aforementioned terminal device is registered for emergency use, a PDU session is established for the aforementioned terminal device through the aforementioned first network slice; and The aforementioned request is rejected if the terminal device has not been registered for emergency use.

[0167] (Postscript 15) A terminal device includes a control unit and a communication unit. The aforementioned communications unit and the aforementioned communications unit are configured to, in emergency situations, A message is sent to the network node requesting the aforementioned terminal device to use the first network slice, which is a network slice allocated for emergency purposes. If the aforementioned terminal device is registered for emergency use, a message indicating that a PDU session has been established through the aforementioned first network slice is received from the aforementioned network node. If the aforementioned terminal device is not registered for emergency use, a message indicating that the aforementioned request is rejected is received from the aforementioned network node.

[0168] (Postscript 16) According to the terminal device described in Appendix 15, the aforementioned control unit and the aforementioned communication unit are further configured such that, under normal circumstances... Receive a message from the aforementioned network node requesting the aforementioned terminal device to use the aforementioned first network slice. Receive a message from the aforementioned network node indicating that the aforementioned request is rejected.

[0169] (Postscript 17) According to the terminal device described in Appendix 15, the aforementioned control unit and the aforementioned communication unit are further configured such that, under normal circumstances... Receive a message from the aforementioned network node requesting the aforementioned terminal device to use the aforementioned first network slice. Receive a message from the aforementioned network node indicating that the aforementioned first network slice has been registered.

[0170] (Postscript 18) A method, executed by a terminal device, includes: in an emergency, Send a message to the network node requesting the aforementioned terminal device to use the first network slice, wherein the first network slice is a network slice allocated for emergency purposes; In the event that the aforementioned terminal device is registered for emergency use, a message indicating that a PDU session has been established through the aforementioned first network slice is received from the aforementioned network node; and If the aforementioned terminal device is not registered for emergency use, a message indicating that the aforementioned request is rejected is received from the aforementioned network node.

[0171] (Postscript 19) A program that, when executed, causes the processor in a terminal device to perform the following: Send a message to the network node requesting the aforementioned terminal device to use the first network slice, wherein the first network slice is a network slice allocated for emergency purposes; In the event that the aforementioned terminal device is registered for emergency use, a message indicating that a PDU session has been established through the aforementioned first network slice is received from the aforementioned network node; and If the aforementioned terminal device is not registered for emergency use, a message indicating that the aforementioned request is rejected is received from the aforementioned network node.

[0172] (Postscript 20) A computer-readable, non-transient tangible recording medium storing a program that, when executed, causes a processor in a terminal device to perform the following: Send a message to the network node requesting the terminal device to use a first network slice, wherein the first network slice is a network slice allocated for emergency purposes; In the event that the aforementioned terminal device is registered for emergency use, a message indicating that a PDU session has been established through the aforementioned first network slice is received from the aforementioned network node; and If the aforementioned terminal device is not registered for emergency use, a message indicating that the aforementioned request is rejected is received from the aforementioned network node.

[0173] Furthermore, the disclosures in the aforementioned prior art documents and references are incorporated herein by reference. Figure Labels

[0174] 10 Network Nodes, 101 Processor, 102 Memory, 103 Transmitter / Receiver, 110 Control Unit, 120 Communication Unit, 20 Terminal Devices, 201 Processor, 202 Memory, 203 Input / Output Interfaces, 204 Transmitter / Receiver, 205 Antenna, 210 Control Unit, 220 Communication Unit, 30 RAN Nodes, 40 DN

Claims

1. A network node, comprising a control unit and a communication unit, The communication unit is configured to, in an emergency, receive a message requesting a terminal device to use a first network slice, wherein the first network slice is a network slice allocated for emergency purposes. The control unit is configured to, in an emergency... Determine whether the terminal device is registered for emergency use. If the terminal device is registered for emergency use, a PDU session is established for the terminal device via the first network slice. The request is rejected if the terminal device is not registered for emergency use.

2. The network node according to claim 1, wherein the communication unit is further configured to, under normal circumstances, receive a message requesting the terminal device to use the first network slice. The control unit is further configured to reject the request under normal circumstances.

3. The network node according to claim 1, wherein the communication unit is further configured to, under normal circumstances, receive a message requesting the terminal device to use the first network slice. The control unit is further configured to register the first network slice under normal circumstances.

4. The network node according to claim 3, wherein the control unit is further configured to disconnect the PDU session established under normal circumstances.

5. The network node according to claim 1, wherein under normal circumstances the terminal device is using a second network slice not allocated for emergency purposes, The communication unit is further configured to, in an emergency, receive a message requesting the terminal device to switch from the second network slice to the first network slice. The control unit is further configured to, in an emergency, disconnect the PDU session established with the terminal device via the second network slice.

6. The network node of claim 1, comprising a group of multiple terminal devices registered for the first network slice, The communication unit is further configured to receive, in an emergency, a message requesting each terminal device in the group to use the first network slice.

7. The network node according to claim 6, wherein the communication unit is further configured to send a message requesting the use of the first network slice to each terminal device in the group.

8. The network node according to claim 1, wherein the control unit is further configured to determine whether the terminal device is registered for emergency use based on the identifier of the terminal device.

9. The network node according to claim 1, wherein the control unit is further configured to determine, based on subscription data, whether the terminal device is registered for emergency use.

10. The network node according to claim 1, wherein the control unit is further configured to, in an emergency, Determine the network service requirements in the disaster-affected area. Based on the service requirements, the first network slice is selected from the network slices allocated for emergency purposes.

11. The network node according to claim 10, wherein the control unit is further configured to, Calculate the number of terminal devices registered for emergency use that exist within the area. The service requirements are determined based on the number of terminal devices.

12. A method, performed by a network node, the method comprising: In an emergency, Receive a message requesting the terminal device to use a first network slice, wherein the first network slice is a network slice allocated for emergency purposes; Determine whether the terminal device has been registered for emergency use; When the terminal device is registered for emergency use, a PDU session is established for the terminal device through the first network slice; as well as The request is rejected if the terminal device is not registered for emergency use.

13. A program that, when executed, causes a processor in a network node to perform: Receive a message requesting the terminal device to use a first network slice, wherein the first network slice is a network slice allocated for emergency purposes; Determine whether the terminal device has been registered for emergency use; When the terminal device is registered for emergency use, a PDU session is established for the terminal device through the first network slice; as well as The request is rejected if the terminal device is not registered for emergency use.

14. A terminal device, comprising a control unit and a communication unit, The communication unit and the communication unit are configured to, in an emergency, A message is sent to the network node requesting the terminal device to use a first network slice, which is a network slice allocated for emergency purposes. When the terminal device is registered for emergency use, a message indicating that a PDU session has been established through the first network slice is received from the network node. If the terminal device is not registered for emergency use, a message indicating that the request is rejected is received from the network node.

15. The terminal device according to claim 14, wherein the control unit and the communication unit are further configured such that, under normal circumstances, Receive a message from the network node requesting the terminal device to use the first network slice. Receive a message from the network node indicating that the request is rejected.

16. The terminal device according to claim 14, wherein the control unit and the communication unit are further configured such that, under normal circumstances, Receive a message from the network node requesting the terminal device to use the first network slice. Receive a message from the network node indicating that the first network slice has been registered.

17. A method, performed by a terminal device, comprising: In an emergency, Send a message to the network node requesting the terminal device to use a first network slice, wherein the first network slice is a network slice allocated for emergency purposes; When the terminal device is registered for emergency use, a message indicating that a PDU session has been established through the first network slice is received from the network node; as well as If the terminal device is not registered for emergency use, a message indicating that the request is rejected is received from the network node.

18. A program, when executed, causes a processor in a terminal device to perform: Send a message to the network node requesting the terminal device to use a first network slice, wherein the first network slice is a network slice allocated for emergency purposes; When the terminal device is registered for emergency use, a message indicating that a PDU session has been established through the first network slice is received from the network node; as well as If the terminal device is not registered for emergency use, a message indicating that the request is rejected is received from the network node.

Images