WO2023214456A1 - Network node and communication method - Google Patents

Network node and communication method Download PDF

Info

Publication number
WO2023214456A1
WO2023214456A1 PCT/JP2022/019538 JP2022019538W WO2023214456A1 WO 2023214456 A1 WO2023214456 A1 WO 2023214456A1 JP 2022019538 W JP2022019538 W JP 2022019538W WO 2023214456 A1 WO2023214456 A1 WO 2023214456A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
nssai
network
registration
network slice
Prior art date
Application number
PCT/JP2022/019538
Other languages
French (fr)
Japanese (ja)
Inventor
元洋 阿部
和人 清水
Original Assignee
株式会社Ｎｔｔドコモ
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社Ｎｔｔドコモ filed Critical 株式会社Ｎｔｔドコモ
Priority to PCT/JP2022/019538 priority Critical patent/WO2023214456A1/en
Publication of WO2023214456A1 publication Critical patent/WO2023214456A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data

Definitions

  • the present invention relates to a network node and a communication method in a communication system.
  • 5G or NR New Radio
  • 5G 5G or NR (New Radio) is being developed in order to further increase system capacity, further increase data transmission speed, and further reduce latency in wireless sections.
  • ⁇ 5G'' a wireless communication system called ⁇ 5G'' (hereinafter referred to as ⁇ 5G'' or ⁇ NR'').
  • 5G various wireless technologies are being studied in order to meet the requirements of achieving a throughput of 10 Gbps or more while reducing the delay in the wireless section to 1 ms or less.
  • 5GC 5G Core Network
  • EPC Evolved Packet Core
  • RAN Radio Access Network
  • Network architectures including NG-RAN (Next Generation - Radio Access Network) corresponding to Evolved Universal Terrestrial Radio Access Network are being considered (for example, Non-Patent Document 1 and Non-Patent Document 2).
  • a network slice for communication carriers to provide services to users is operated in 5GC.
  • service areas that provide network slices have been set for each registration area (RA). Therefore, it has been difficult to provide network slices in a service area different from the geographical range corresponding to the registered area.
  • the present invention has been made in view of the above points, and an object of the present invention is to improve the flexibility of setting a service area for providing network slices in a communication system.
  • a registration request is received from a terminal, including information indicating that a TAI (Tracking Area Identity) list consisting of tracking areas that provide network slices is supported and information indicating a network slice that is requested to be used.
  • a control unit that generates, based on the registration request, a registration permission that includes information related to the network slice that is requested to be used; and a transmission unit that transmits the registration permission to the terminal.
  • FIG. 1 is a diagram for explaining an example of a communication system.
  • FIG. 2 is a diagram for explaining an example of a communication system under a roaming environment.
  • FIG. 3 is a diagram showing an example (1) of connecting to a network slice. It is a figure which shows the example (2) of connecting to a network slice. It is a figure which shows the example (3) of connecting to a network slice. It is a sequence diagram for explaining example (1) of a registration request in an embodiment of the present invention.
  • FIG. 7 is a sequence diagram for explaining example (2) of a registration request in the embodiment of the present invention.
  • FIG. 7 is a sequence diagram for explaining example (3) of a registration request in the embodiment of the present invention.
  • FIG. 1 is a diagram for explaining an example of a communication system.
  • FIG. 2 is a diagram for explaining an example of a communication system under a roaming environment.
  • FIG. 3 is a diagram showing an example (1) of connecting to a network slice. It is a figure which shows the example (2) of connecting to
  • FIG. 7 is a sequence diagram for explaining example (4) of a registration request in the embodiment of the present invention.
  • FIG. 7 is a sequence diagram for explaining example (5) of a registration request in the embodiment of the present invention.
  • FIG. 3 is a diagram showing an example of storage operation in an embodiment of the present invention.
  • FIG. 3 is a diagram illustrating an example when a terminal moves according to an embodiment of the present invention.
  • FIG. 3 is a sequence diagram for explaining an example when a terminal moves in an embodiment of the present invention.
  • 1 is a diagram showing an example of a functional configuration of a base station 10 in an embodiment of the present invention. It is a diagram showing an example of a functional configuration of a terminal 20 in an embodiment of the present invention. It is a diagram showing an example of the hardware configuration of a base station 10 and a terminal 20 in an embodiment of the present invention. It is a figure showing an example of composition of vehicle 2001 in an embodiment of the present invention.
  • LTE Long Term Evolution
  • NR Universal Terrestrial Radio Access
  • LAN Local Area Network
  • configure the wireless parameters etc. may mean pre-configuring a predetermined value, or may mean that the network node 30 or Wireless parameters notified from the terminal 20 may also be set.
  • FIG. 1 is a diagram for explaining an example of a communication system.
  • the communication system includes a UE, which is a terminal 20, and a plurality of network nodes 30.
  • a UE which is a terminal 20
  • network nodes 30 there are no network nodes 30.
  • one network node 30 corresponds to each function, but one network node 30 may realize multiple functions, or multiple network nodes 30 may realize one function.
  • the "connection" described below may be a logical connection or a physical connection.
  • the RAN Radio Access Network
  • the RAN is a network node 30 having a radio access function, may include the base station 10, and is connected to the UE, the AMF (Access and Mobility Management Function), and the UPF (User plane function).
  • the AMF is a network node 30 having functions such as RAN interface termination, NAS (Non-Access Stratum) termination, registration management, connection management, reachability management, and mobility management.
  • the UPF is a network node 30 that has functions such as a PDU (Protocol Data Unit) session point for the outside that interconnects with a DN (Data Network), packet routing and forwarding, and user plane QoS (Quality of Service) handling.
  • the UPF and DN constitute a network slice.
  • a plurality of network slices may be constructed in a wireless communication network according to an embodiment of the present invention.
  • AMF includes UE, RAN, SMF (Session Management function), NSSF (Network Slice Selection Function), NEF (Network Exposure Function), NRF (Network Repository Function), UDM (Unified Data Management), AUSF (Authentication Server Function), Connected to PCF (Policy Control Function) and AF (Application Function).
  • AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are interconnected through their respective service-based interfaces, Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf. This is a network node 30.
  • the SMF is a network node 30 that has functions such as session management, UE IP (Internet Protocol) address assignment and management, DHCP (Dynamic Host Configuration Protocol) function, ARP (Address Resolution Protocol) proxy, and roaming function.
  • the NEF is a network node 30 that has a function of notifying other NFs (Network Functions) of capabilities and events.
  • the NSSF is a network node 30 that has functions such as selecting a network slice to which a UE connects, determining permitted NSSAI (Network Slice Selection Assistance Information), determining NSSAI to be configured, and determining an AMF set to which a UE connects. be.
  • the PCF is a network node 30 that has a function of controlling network policy.
  • AF is a network node 30 that has a function of controlling an application server.
  • An NRF is a network node 30 that has the ability to discover NF instances that provide services.
  • the UDM is a network node 30 that manages subscriber data and authentication data.
  • the UDM is connected to a UDR (User Data Repository) that holds the data.
  • FIG. 2 is a diagram for explaining an example of a communication system under a roaming environment.
  • the network is composed of a UE, which is a terminal 20, and a plurality of network nodes 30.
  • a UE which is a terminal 20
  • network nodes 30 it is assumed that one network node 30 corresponds to each function, but one network node 30 may realize multiple functions, or multiple network nodes 30 may realize one function.
  • the "connection" described below may be a logical connection or a physical connection.
  • the RAN is a network node 30 that has a radio access function and is connected to the UE, AMF, and UPF.
  • the AMF is a network node 30 that has functions such as RAN interface termination, NAS termination, registration management, connection management, reachability management, and mobility management.
  • the UPF is a network node 30 that has functions such as a PDU session point for the outside that interconnects with the DN, packet routing and forwarding, and user plane QoS handling.
  • the UPF and DN constitute a network slice. In the wireless communication network according to the embodiment of the present invention, a plurality of network slices are constructed.
  • AMF is connected to UE, RAN, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, AF, and SEPP (Security Edge Protection Proxy).
  • AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are interconnected through their respective service-based interfaces, Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf. This is a network node 30.
  • the SMF is a network node 30 that has functions such as session management, UE IP address assignment and management, DHCP function, ARP proxy, and roaming function.
  • a NEF is a network node 30 that has the ability to notify other NFs of capabilities and events.
  • the NSSF is a network node 30 that has functions such as selecting a network slice to which a UE connects, determining permitted NSSAIs, determining NSSAIs to be configured, and determining an AMF set to which a UE connects.
  • the PCF is a network node 30 that has a function of controlling network policy.
  • AF is a network node 30 that has a function of controlling an application server.
  • An NRF is a network node 30 that has the ability to discover NF instances that provide services.
  • SEPP is a non-transparent proxy that filters control plane messages between PLMNs (Public Land Mobile Networks).
  • the vSEPP shown in FIG. 2 is the SEPP in the visited network
  • the UE is in a roaming environment connected to the RAN and AMF in a VPLMN (Visited PLMN).
  • VPLMN and HPLMN are connected via vSEPP and hSEPP.
  • the UE can communicate with the HPLMN's UDM via the VPLMN's AMF, for example.
  • a network slice for communication carriers to provide services to users is operated in 5GC.
  • service areas that provide network slices have been set for each registration area (RA).
  • RA registration area
  • TA tracking area
  • FIG. 3 is a diagram showing an example (1) of connecting to a network slice.
  • the registration area that the service area of S-NSSAI (Single Network Slice Selection Assistance Information) #1 corresponds to consists of TA1, TA2, and TA3, and the service area of S-NSSAI #2 corresponds to. It is assumed that the registration area consists of TA4, TA5, and TA6.
  • the example in FIG. 3 is a case where the service area of S-NSSAI #1 coincides with the boundary of the registration area.
  • the UE when the UE sends a registration request (Requested NSSAI (S-NSSAI#1)) to the network in TA5, the network indicates that the connection to S-NSSAI #1 is not available. A response (Rejected NSSAI (S-NSSAI#1)) indicating this is sent to the UE. The Cause value of the response indicates that the corresponding S-NSSAI is not available in the current registration area.
  • FIG. 4 is a diagram showing an example (2) of connecting to a network slice.
  • the tracking area to which the service area of S-NSSAI#1 corresponds is composed of TA1, TA2, TA3, and TA4, and the tracking area to which the service area of S-NSSAI#2 corresponds is TA5. and TA6.
  • TA1 the tracking area to which the service area of S-NSSAI #1 does not coincide with the boundary of the registration area.
  • FIG. 5 is a diagram showing an example (3) of connecting to a network slice.
  • the tracking area to which the service area of S-NSSAI#1 corresponds is composed of TA1, TA2, TA3, and TA4, and the tracking area to which the service area of S-NSSAI#2 corresponds is TA5. and TA6.
  • the tracking area to which the service area of S-NSSAI#1 corresponds is TA5. and TA6.
  • the UE when the UE sends a registration request to the network, it may only allow access to the network even if it is in an area that cannot be connected to the network slice. Further, when the UE sends a registration request to the network, if the area is not connectable to the network slice, the network may notify the UE of a tracking area where the network slice can be used. Further, when the UE sends a registration request to the network, if the area is not connectable to the network slice, the network may notify the UE of the usable and unusable tracking areas. Further, when the UE sends a registration request to the network, if the network slice cannot be connected to the area, the network may refuse the connection and notify the UE of the usable area.
  • FIG. 6 is a sequence diagram for explaining example (1) of a registration request in the embodiment of the present invention.
  • the UE 20 transmits a registration request including first information to the AMF 30A.
  • the first information may be information indicating that the UE supports a registration area that takes network slices into consideration, ie a corresponding TAI (Tracking Area Identity) list.
  • the UE may request the network to generate a registration area, ie, a corresponding TAI list, taking network slices into consideration using the first information.
  • the first information indicates the UE's priority tendency regarding TAI list generation. For example, it indicates that priority is given to a registration area configuration that takes network slices into consideration.
  • the first information may be set in the 5GMM capability IE.
  • Considering network slices means generating a TAI list consisting only of TAs that support the S-NSSAI requested by the UE (included in the Requested NSSAI IE) (the S-NSSAI can be used by the TA). It may also mean "to take into account”. Alternatively, considering the network slice may mean that consideration is given to generating a TAI list consisting only of TAs that support the subscribed S-NSSAI of the UE.
  • the AMF 30A In the following step S102, the AMF 30A generates a TAI list that takes network slices into consideration.
  • the AMF 30A transmits registration permission including the eleventh information and the twelfth information to the UE 20.
  • the eleventh information may be a registration area considering network slices, that is, a corresponding TAI list.
  • the registration area that takes network slice into consideration, that is, the corresponding TAI list may be a TAI list that is configured only of TAs that support S-NSSAI requested by the UE (included in the Requested NSSAI IE).
  • the registration area considering network slices, that is, the corresponding TAI list may be a TAI list composed only of TAs that support the UE's Subscribed S-NSSAI.
  • the eleventh information may be included in the TAI list IE.
  • the UE that has received the 11th information moves from the registration area (TAI list) considering network slices to another RA so that the 12th information included in the Rejected NSSAI can be used in the next registration procedure. Good too.
  • S-NSSAI #2 is supported.
  • the UE When the UE is located in TA #3 and sends a message to the AMF 30A including S-NSSAI #1 and S-NSSAI #2 in the Requested NSSAI IE, the UE sends S-NSSAI #1 (with cause value "S -NSSAI not available in the current registration area" is set to Rejected NSSAI IE, and S-NSSAI #2 is Allowed NSSA I Receive the registration permission set in the IE.
  • the UE 20 receives the TAI list IE in which only TA #3 is configured. That is, the UE receives a TAI list composed of TAs that can be used by the S-NSSAI included in the Allowed NSSAI IE.
  • the UE 20 moves from TA #3 to TA #2 (moving from TA #3 to TA #2 means moving to another RA (straddling RA)), first The received "S-NSSAI not available in the current registration area" can be resolved, and the UE 20 can include S-NSSAI #1 in the registration request. More specifically, by moving from the original RA, the UE 20 stores S-NSSAI #1 in the Rejected NSSAI in the next registration request, even if S-NSSAI #1 is stored in the Rejected NSSAI of the NSSAI storage. Can be included in IE. At this time, the UE may or may not delete S-NSSAI #1 from Rejected NSSAI in the NSSAI storage.
  • the twelfth information may be an S-NSSAI that cannot be used at the current location of the UE 20, that is, it is not an Allowed NSSAI.
  • the twelfth information may be included in Rejected NSSAI.
  • the twelfth information may be included in the same message as the eleventh information.
  • the current location may be TAI, a geographic location, or other information indicating the location.
  • the UE 20 that has received the twelfth information does not use the twelfth information at the current location.
  • the UE 20 that has received the twelfth information may store the twelfth information in the NSSIA storage corresponding to the IE in which it is included.
  • FIG. 7 is a sequence diagram for explaining example (2) of a registration request in the embodiment of the present invention.
  • the UE 20 transmits a registration request including the second information to the AMF 30A.
  • the second information may be information indicating that the UE supports network slicing services at TA granularity.
  • the information may be information indicating that the UE 20 supports an IE including 21st information and an IE including 22nd information, which will be described later.
  • Support of the UE 20 may mean, for example, that the UE 20 supports the behavior meant by the 21st information and the 22nd information when receiving the 21st information and the 22nd information, It may also mean that upon receiving the 21st and 22nd information, the information is managed or can be managed in a special NSSAI storage for the 21st and 22nd information.
  • the second information may be set in the 5GMM capability IE.
  • step S202 the AMF 30A generates a limited allowed NSSAI with one or more of the UDM, NSSF, and NF. Subsequently, in step S203, the AMF 30A transmits registration permission including the 21st information and the 22nd information to the UE 20.
  • step S204 the UE 20 updates the NSSAI storage.
  • step S205 the UE 20 moves to a TA that supports S-NSSAI #1 or a TA that does not.
  • step S206 it is determined whether the S-NSSAI can be used based on the broadcast information (for example, SIB) and the NSSAI storage.
  • the 21st information may be an S-NSSAI that cannot be used at the current location of the UE 20 or that can be used at the current location, but may be an S-NSSAI that can be used at the location indicated by the 22nd information.
  • the 21st information may be included in the Limited Allowed NSSAI IE or the Conditional NSSAI IE.
  • the IE that includes the S-NSSAI is not limited to this.
  • the location may be TAI, a geographic location, or other information indicating the location.
  • the UE 20 that has received the 21st information does not use the 21st information if the 21st information is S-NSSAI that cannot be used at the current location. Not using the 21st information may mean not using it in any NAS procedure. For example, as long as the location of the UE is the current location, the 21st information may not be used in the registration procedure. Further, the 21st information does not need to be used in the PDU session establishment procedure. Not using it may mean not including it in each NAS message. On the other hand, the UE 20 that has received the 21st information may use the 21st information if the 21st information is S-NSSAI that can be used at the current location. The UE that has received the 21st information may store the 21st information in the NSSAI storage according to the IE that includes it.
  • the 22nd information may be the 21st information, that is, information indicating a location where the S-NSSAI can be used.
  • the 22nd information may be transmitted to the UE 20 in association with the 21st information.
  • the location may be TAI, a geographic location, or other information indicating the location.
  • the UE 20 that has received the 22nd information may utilize the 21st information if it detects that the UE 20 has moved to the position indicated by the 22nd information in addition to the behavior of the UE 20 based on the 21st information.
  • the UE 20 may detect that it has moved to the position indicated by the 22nd information based on the information included in the broadcast information.
  • one RA includes TA#1, TA#2, and TA#3, TA#1 and TA#2 support S-NSSAI#1, and TA#3 supports S-NSSAI#
  • S-NSSAI #1 is not supported but S-NSSAI #2 is supported.
  • the UE 20 When the UE 20 is located in TA #3 and sends a message to the AMF 30A including S-NSSAI #1 and S-NSSAI #2 in the Requested NSSAI IE, the UE 20 recognizes that S-NSSAI #1 is the 21st is set to the IE that contains the information, and S-NSSAI#2 receives the registration permission set to the Allowed NSSAI IE.
  • the UE receives 22nd information in which TA#1 and TA#2 associated with the 21st information are configured.
  • S-NSSAI #1 “Available” may mean that S-NSSAI #1 can be included in the registration request (permitted) in the registration procedure, or that S-NSSAI #1 can be used in the PDU session establishment request ( may mean that it is permitted).
  • the UE 20 may treat the 21st information received at TA #3 when moving to TA #1 or TA #2 as if it were S-NSSAI included in Allowed NSSAI.
  • the UE 20 transfers the 21st information (S-NSSAI#1) stored in the NSSAI storage corresponding to the IE containing the 21st information to the NSSAI corresponding to the IE containing the 21st information. It may also be deleted from the storage. Furthermore, the UE 20 may store the 21st information in Allowed NSSAI of the NSSAI storage. Thereby, the UE 20 can use S-NSSAI #1 included in Allowed NSSAI in the NSSAI storage in subsequent NAS procedures (for example, registration procedure or PDU session establishment procedure).
  • S-NSSAI#1 can be included in the Requested NSSAI IE in the registration procedure, and S-NSSAI#1 can be set in the S-NSSAI IE of the UL NAS TRANSPORT message for establishing a PDU session. It may mean that it is possible.
  • FIG. 8 is a sequence diagram for explaining example (3) of a registration request in the embodiment of the present invention.
  • the UE 20 transmits a registration request including the third information to the AMF 30A.
  • the third information may be information indicating that the UE supports TA granularity network slicing services.
  • the information may be information indicating that the UE 20 supports an IE including 32nd information and 33rd information and an IE including 22nd information, which will be described later.
  • Support of the UE 20 means, for example, that when receiving the 31st, 32nd, and/or 33rd information, the UE supports the behavior meant by the 31st, 32nd, and/or 33rd information.
  • the third information may be set in the 5GMM capability IE.
  • the AMF 30A transmits registration permission including the 31st information, the 32nd information, and the 33rd information to the UE 20.
  • the UE 20 updates the NSSAI storage.
  • the UE 20 moves to a TA that supports S-NSSAI #1 or a TA that does not.
  • the 31st information may be S-NSSAI that cannot be used at the current location of the UE 20 but may be available at other locations based on the 32nd information. Further, the 31st information may be S-NSSAI that cannot be used at the current location of the UE 20 but can be used at the location indicated by the 33rd information. The 31st information may be included in the Rejected NSSAI IE. Furthermore, the IE that includes the S-NSSAI is not limited to this.
  • the UE 20 that has received the 31st information does not use the 31st information at its current location. Not using the 31st information may mean not using it in any NAS procedure. For example, as long as the location of the UE 20 is the current location, the 31st information is not used in the registration procedure. Further, the 31st information is not used in the PDU session establishment procedure. Not using it may mean not including it in each NAS message.
  • the UE 20 that has received the 31st information may store it in the NSSAI storage according to the IE that includes the 31st information and the cause value included in the message in association with the 31st information.
  • the cause value may be "S-NSSAI not available in the current registration area".
  • the 32nd information may be a notification indicating an exception in handling the Rejected NSSAI.
  • Rejected NSSAI handling means that the cause value associated here is "S-NSSAI not available in the current registration area", so normal handling is "curre nt registration area” Rejected unless you go outside
  • the S-NSSAI contained in the NAS cannot be used by any NAS procedure.
  • the 32nd information can use the S-NSSAI included in the Rejected NSSAI in the NAS procedure by moving from the current position without going outside the "current registration area".
  • the location may be TAI, a geographic location, or other information indicating the location.
  • the UE 20 that has received the 32nd information does not use the 31st information at its current location. Not using the 31st information may mean not using it in any NAS procedure. For example, as long as the location of the UE 20 is the current location, the 31st information is not used in the registration procedure. Further, the 31st information is not used in the PDU session establishment procedure. Not using it may mean not including it in each NAS message. However, the UE 20 that has received the 32nd information may use the 31st information when moving from the current location.
  • one RA includes TA#1, TA#2, and TA#3, TA#1 and TA#2 support S-NSSAI#1, and TA#3 supports S-NSSAI#
  • S-NSSAI #1 is not supported but S-NSSAI #2 is supported.
  • the UE 20 recognizes that S-NSSAI #1 is the 31st information.
  • S-NSSAI #2 receives the registration permission set to the Allowed NSSAI IE.
  • the UE 20 receives 32nd information associated with the 31st information.
  • S-NSSAI #1 When the UE 20 moves outside TA #3, it can use S-NSSAI #1. "Available” may mean that S-NSSAI #1 can be included in a registration request in the registration procedure (is allowed), or that S-NSSAI #1 can be used in the PDU session establishment procedure ( It may also mean "permitted”.
  • the cause value associated with the 31st information that the UE 20 received at TA #3 is "S-NSSAI not available in the current registration area", that is, the granularity is RA, but the granularity of the cause value is In R.A.
  • the UE 20 may delete (delete/remove) the 31st information (S-NSSAI#1) stored in the Rejected NSSAI of the NSSAI storage from the Rejected NSSAI of the NSSAI storage. This allows the UE 20 to use S-NSSAI #1 in subsequent NAS procedures.
  • S-NSSAI #1 can be included in the Requested NSSAI IE in the registration request, and S-NSSAI #1 can be set in the S-NSSAI IE of the UL NAS TRANSPORT message for the PDU session establishment procedure. It may also mean that it is possible.
  • the 33rd information may be information indicating a location where the 31st information (S-NSSAI) can be used. It is transmitted to the UE 20 in association with the 31st information.
  • the location may be TAI, a geographic location, or other information indicating the location.
  • the UE 20 that has received the 33rd information may use the 31st information if it detects that the UE has moved to the position indicated by the 33rd information. .
  • the UE 20 may detect that the UE 20 has moved to the position indicated by the 33rd information based on the information included in the broadcast information.
  • one RA includes TA#1, TA#2, and TA#3, TA#1 and TA#2 support S-NSSAI#1, and TA#3 supports S-NSSAI#
  • S-NSSAI #1 is not supported but S-NSSAI #2 is supported.
  • the UE 20 sends the S-NSSAI #1 to the Rejected NSSAI IE.
  • S-NSSAI#2 receives the registration permission set to Allowed NSSAI IE.
  • the UE 20 receives 33rd information in which TA#1 and TA#2 associated with the 31st information are set.
  • S-NSSAI #1 “Available” may mean that S-NSSAI #1 can be included in the registration request (permitted) in the registration procedure, or that S-NSSAI #1 can be used (permitted) in the PDU session establishment procedure. It may mean that
  • the UE 20 may treat the 31st information received at TA #3 when moving to TA #1 or TA #2 as if it were S-NSSAI included in Allowed NSSAI. Specifically, the UE 20 may delete (delete/remove) the 31st information (S-NSSAI#1) stored in the Rejected NSSAI of the NSSAI storage from the Rejected NSSAI of the NSSAI storage. Furthermore, the UE may store the 31st information in the Allowed NSSAI of the NSSAI storage. Thereby, the UE can use S-NSSAI #1 included in Allowed NSSAI in the NSSAI storage in subsequent NAS procedures (for example, registration procedure or PDU session establishment procedure).
  • subsequent NAS procedures for example, registration procedure or PDU session establishment procedure.
  • S-NSSAI #1 can be included in the Requested NSSAI IE in the registration request, and S-NSSAI #1 can be set in the S-NSSAI IE of the UL NAS TRANSPORT message for establishing a PDU session. It may mean that it is possible.
  • the UE 20 When the UE 20 receives the 32nd information, it may optionally refer to the 33rd information and recognize at which position S-NSSAI #1 is available.
  • FIG. 9 is a sequence diagram for explaining example (4) of a registration request in the embodiment of the present invention.
  • the UE 20 transmits a registration request including the fourth information to the AMF 30A.
  • the fourth information may be information indicating that the UE supports TA granularity network slicing services.
  • the information may be information indicating that the UE 20 supports an IE including 42nd information to be described later.
  • Support of the UE 20 may mean, for example, that the UE supports the behavior meant by the 41st information and the 42nd information when receiving the 41st information and the 42nd information. However, when the 41st information and the 42nd information are received, it may mean that the information is/can be managed in a special NSSAI storage for the 41st information and the 42nd information.
  • the fourth information may be set in the 5GMM capability IE.
  • the AMF 30A transmits registration permission including the 41st information and the 42nd information to the UE 20.
  • the UE 20 updates the NSSAI storage.
  • the UE 20 moves to a TA that supports S-NSSAI #1 or a TA that does not.
  • the 41st information may be S-NSSAI that cannot be used at the current location of the UE 20 but can be used at the location indicated by the 42nd information.
  • the 41st information may be included in the Rejected NSSAI IE.
  • the IE that includes the S-NSSAI is not limited to this.
  • the location may be TAI, a geographic location, or other information indicating the location.
  • the UE 20 that has received the 41st information does not use the 41st information at its current location. Not using the 41st information may mean not using it in any NAS procedure. For example, as long as the location of the UE 20 is the current location, the 41st information is not used in the registration procedure. Further, the 41st information is not used in the PDU session establishment procedure. Not using it may mean not including it in each NAS message.
  • the UE 20 that has received the 41st information may store it in the NSSAI storage according to the IE that includes the 41st information and the cause value included in the message in association with the 41st information.
  • the cause value may be "S-NSSAI not available in the current registration area".
  • the 42nd information may be information indicating a location where the 41st information (S-NSSAI) can be used.
  • the 42nd information may be transmitted to the UE 20 in association with the 41st information.
  • the location may be TAI, a geographic location, or other information indicating the location.
  • the UE 20 that has received the 42nd information may use the 41st information if it detects that the UE 20 has moved to the position indicated by the 42nd information. .
  • the UE 20 may detect that the UE 20 has moved to the position indicated by the 42nd information based on the information included in the broadcast information.
  • one RA includes TA#1, TA#2, and TA#3, TA#1 and TA#2 support S-NSSAI#1, and TA#3 supports S-NSSAI#
  • S-NSSAI #1 is not supported but S-NSSAI #2 is supported.
  • the UE 20 When the UE 20 is in the area of TA #3 and sends a message to the AMF 30A with S-NSSAI #1 and S-NSSAI #2 included in the Required NSSAI IE, the UE 20 will receive the S-NSSAI #1 as the Rejected NSSAI IE. and S-NSSAI#2 receives the registration permission set to Allowed NSSAI IE.
  • the UE 20 receives the 42nd information in which TA#1 and TA#2 associated with the 41st information are set.
  • the UE 20 moves to TA #1 or TA #2, it can use S-NSSAI #1.
  • “Available” may mean that S-NSSAI#1 can be included in a registration request (permitted) in the registration procedure, or S-NSSAI#1 can be used in a PDU session establishment request (permitted). It may mean that
  • the UE 20 may treat the 41st information received at TA #3 when moving to TA #1 or TA #2 as if it were S-NSSAI included in Allowed NSSAI. Specifically, the UE may delete/remove the 41st information (S-NSSAI#1) stored in the Rejected NSSAI of the NSSAI storage from the Rejected NSSAI of the NSSAI storage. Furthermore, the UE may store the 41st information in Allowed NSSAI of the NSSAI storage. Thereby, the UE can use S-NSSAI #1 included in Allowed NSSAI in the NSSAI storage in subsequent NAS procedures (for example, registration procedure or PDU session establishment procedure).
  • S-NSSAI#1 stored in the Rejected NSSAI of the NSSAI storage from the Rejected NSSAI of the NSSAI storage.
  • the UE may store the 41st information in Allowed NSSAI of the NSSAI storage. Thereby, the UE can use S-NSSAI #1 included in Allowed NSSAI
  • S-NSSAI #1 can be included in the Requested NSSAI IE in the registration request, and S-NSSAI #1 can be set in the S-NSSAI IE of the UL NAS TRANSPORT message for establishing a PDU session. It may mean that it is possible.
  • FIG. 10 is a sequence diagram for explaining example (5) of a registration request in the embodiment of the present invention.
  • the UE 20 transmits a registration request including the fifth information to the AMF 30A.
  • the fifth information may be information indicating that the UE supports TA granularity network slicing services. Support of the UE 20 may mean whether or not to support a network slice service of TA granularity, or may mean, for example, whether or not to support 52nd information.
  • the fifth information may be set in the 5GMM capability IE.
  • the AMF 30A transmits registration permission including the 51st information and the 52nd information to the UE 20.
  • the UE 20 updates the NSSAI storage.
  • the UE 20 moves to another TA.
  • the 51st information may be S-NSSAI that cannot be used at the current location of the UE 20.
  • the 51st information may be included in the Rejected NSSAI IE.
  • the IE that includes the S-NSSAI is not limited to this.
  • the location may be TAI, a geographic location, or other information indicating the location.
  • the UE 20 that has received the 51st information does not use the 51st information at its current location. Not using the 51st information may mean not using it in any NAS procedure. For example, as long as the location of the UE 20 is the current location, the 51st information is not used in the registration procedure. Furthermore, the 51st information is not used in the PDU session establishment procedure. Not using it may mean not including it in each NAS message.
  • the UE 20 that has received the 51st information may store it in the NSSAI storage according to the IE that includes the 51st information and the cause value included in the message in association with the 51st information.
  • the cause value may be the 52nd information.
  • the 52nd information may be a cause value associated with the 51st information.
  • the cause value may be a value indicating that the scope of the Rejected NSSAI is tracking area granularity, and may be, for example, "S-NSSAI not available in the current tracking area".
  • the UE that has received the 52nd information does not use the 51st information at its current location. Not using the 51st information may mean not using it in any NAS procedure. For example, as long as the location of the UE is the current location, the 51st information is not used in the registration procedure. Furthermore, the 51st information is not used in the PDU session establishment procedure. Not using it may mean not including it in each NAS message. However, the UE that has received the 52nd information may use the 51st information if it moves outside its current location.
  • one RA includes TA#1, TA#2, and TA#3, TA#1 and TA#2 support S-NSSAI#1, and TA#3 supports S-NSSAI#
  • S-NSSAI #1 is not supported but S-NSSAI #2 is supported.
  • the UE 20 recognizes that S-NSSAI #1 is the 51st is set to the IE that contains the information, and S-NSSAI#2 receives the registration permission set to the Allowed NSSAI IE.
  • the UE 20 receives the 52nd information associated with the 51st information.
  • the UE 20 moves outside TA #3, it can use S-NSSAI #1.
  • “Available” may mean that S-NSSAI #1 can be included in the registration request (permitted) in the registration procedure, or that S-NSSAI #1 can be used in the PDU session establishment request ( may mean that it is permitted).
  • the cause value associated with the 51st information that the UE 20 received at TA #3 is "S-NSSAI not available in the current tracking area", that is, the granularity is TA, so if it goes outside the TA, it will cause Value restrictions can be resolved and S-NSSAI#1 can be used.
  • the UE may delete/remove the 51st information (S-NSSAI#1) stored in the Rejected NSSAI of the NSSAI storage from the Rejected NSSAI of the NSSAI storage. This allows the UE 20 to use S-NSSAI #1 in subsequent NAS procedures.
  • S-NSSAI #1 can be included in the Requested NSSAI IE in the registration request, and S-NSSAI #1 can be set in the S-NSSAI IE of the UL NAS TRANSPORT message for establishing a PDU session. It may mean that it is possible.
  • FIG. 11 is a diagram showing an example of storage operation in the embodiment of the present invention.
  • TA1 supports S-NSSAI #1 and TA2 does not support S-NSSAI #1.
  • the UE activates NSSAA (Network Slice-Specific Authentication and Authorization) and receives "Pending NSSAI (S-NSSAI #1)" from the AMF.
  • NSSAA Network Slice-Specific Authentication and Authorization
  • S-NSSAI #1 Serving NSSAI
  • the UE moves to TA2 and receives "Rejected NSSAI (S-NSSAI #1) with cause per TA" from the AMF.
  • the cause value indicates that it is not possible in the current tracking area.
  • the behavior of NSSAI storage in the UE may be as shown below.
  • the S-NSSAI (S-NSSAI#1 in the example of FIG. 11) may be mapped to the S-NSSAI rejected in the current tracking area and held in the NSSAI storage. That is, the granularity of each tracking area may be newly defined.
  • FIG. 12 is a diagram showing an example when the terminal moves in the embodiment of the present invention.
  • the tracking area to which the service area of S-NSSAI#1 corresponds is composed of TA1, TA2, TA3, and TA4, and the tracking area to which the service area of S-NSSAI#2 corresponds is TA5. and TA6.
  • the UE makes a registration request at TA5, receives a response (Allowed NSSAI(S-NSSAI#1)) from the network indicating that a connection to S-NSSAI#1 is available, and the UE It may also be connected to S-NSSAI #2.
  • S-NSSAI #1 and S-NSSAI #2 can be used as network slice services, so network slice selection may be performed. That is, the UE may change the connection from S-NSSAI #2 to S-NSSAI #1.
  • FIG. 13 is a sequence diagram for explaining an example when the terminal moves in the embodiment of the present invention.
  • the AMF 30A and the NSSF 30C trigger reselection of a network slice.
  • the AMF 30A may be triggered by the AI inferring the movement of the UE based on a notification from another AS (Access Stratum).
  • AS Access Stratum
  • the AMF 30A sends a GET request of Nnssf_NSSelection including a network slice instance switching request and a Selected NSIID (Network slice instance ID), that is, information indicating the selected or oldNSIID, to the NSSF 30C.
  • the NSSF 30C may be an NF that has a network slice instance switching and selection function. Having a network slice instance switching selection function may mean having a function of notifying the AMF 30A of the NSI ID to which switching is to be made.
  • the AMF 30A may transmit the above information as an Attribute included in the GET request of Nnssf_NSSelection.
  • the NSSF 30C reselects a network slice.
  • the NSSF 30C transmits 200OK of Nnssf_NSSelection to the AMF 30A.
  • the message may include a switch destination network slice instance candidate and a priority of the switch destination network slice instance candidate. Candidates for switching destination network slice instances may be notified by NSSID. There may be multiple candidates for the network slice instance to switch to. The priority of network slice instance candidates may be the priority associated with each candidate when there are multiple network slice instance candidates to switch to.
  • the AMF 30A that has received the information indicating the priority determines candidates for the switching destination network slice instance based on the priority.
  • the NSSF 30C may include the new NSSID, the associated NSSAI, the set NSSAI, and the allowed NSSAI in Nnssf_NSSelection and transmit it to the AMF 30A.
  • the AMF 30A transmits the CONFIGRATION UPDATE COMMAND including information indicating "registration requested" to the UE 20.
  • the information prompts the UE 20 to register its location.
  • the UE 20 transmits a registration request to the AMF 30A.
  • the AMF 30A manages the mapping of the switching destination NSIID and the switching destination S-NSSAI in response to the registration request transmitted from the UE 20 in response to the message. Further, when receiving a registration request transmitted from the UE 20, if AMF relocation (see Non-Patent Document 2) is required, AMF relocation may be activated. In subsequent step S608, the AMF 30A transmits registration permission to the UE 20.
  • the granularity of providing network slices can be changed from each registered area to each tracking area, and network slices can be provided based on the tracking area where the user is located.
  • Base station 10, network node 30 and terminal 20 include functionality to implement the embodiments described above. However, the base station 10, network node 30, and terminal 20 may each have only some of the functions in the embodiment.
  • FIG. 14 is a diagram showing an example of the functional configuration of the base station 10.
  • base station 10 includes a transmitting section 110, a receiving section 120, a setting section 130, and a control section 140.
  • the functional configuration shown in FIG. 14 is only an example. As long as the operations according to the embodiments of the present invention can be carried out, the functional divisions and functional parts may have any names.
  • the network node 30 may have the same functional configuration as the base station 10. Further, the network node 30 having a plurality of different functions in the system architecture may be configured from a plurality of network nodes 30 separated for each function.
  • the transmitting unit 110 includes a function of generating a signal to be transmitted to the terminal 20 or other network node 30, and transmitting the signal by wire or wirelessly.
  • the receiving unit 120 includes a function of receiving various signals transmitted from the terminal 20 or other network nodes 30 and acquiring, for example, information on a higher layer from the received signals.
  • the setting unit 130 stores preset setting information and various setting information to be sent to the terminal 20 in a storage device, and reads them from the storage device as necessary.
  • the contents of the setting information include, for example, settings related to network slices.
  • control unit 140 performs processing related to network slices in the network. Further, the control unit 140 performs processing related to communication with the terminal 20.
  • a functional unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and a functional unit related to signal reception in the control unit 140 may be included in the receiving unit 120.
  • FIG. 15 is a diagram showing an example of the functional configuration of the terminal 20.
  • the terminal 20 includes a transmitting section 210, a receiving section 220, a setting section 230, and a control section 240.
  • the functional configuration shown in FIG. 15 is only an example. As long as the operations according to the embodiments of the present invention can be carried out, the functional divisions and functional parts may have any names.
  • the transmitter 210 creates a transmission signal from the transmission data and wirelessly transmits the transmission signal.
  • the receiving unit 220 wirelessly receives various signals and obtains higher layer signals from the received physical layer signals. Further, the receiving unit 220 has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL/UL control signal, reference signal, etc. transmitted from the network node 30.
  • the setting unit 230 stores various setting information received from the network node 30 by the receiving unit 220 in a storage device, and reads it from the storage device as necessary.
  • the setting unit 230 also stores setting information that is set in advance.
  • the contents of the setting information include, for example, settings related to network slices.
  • control unit 240 performs processing related to connection control to the network and network slices.
  • a functional unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and a functional unit related to signal reception in the control unit 240 may be included in the receiving unit 220.
  • each functional block may be realized using one physically or logically coupled device, or may be realized using two or more physically or logically separated devices directly or indirectly (e.g. , wired, wireless, etc.) and may be realized using a plurality of these devices.
  • the functional block may be realized by combining software with the one device or the plurality of devices.
  • Functions include judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, These include, but are not limited to, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning. I can't do it.
  • a functional block (configuration unit) that performs transmission is called a transmitting unit or a transmitter. In either case, as described above, the implementation method is not particularly limited.
  • the network node 30, terminal 20, etc. in an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure.
  • FIG. 16 is a diagram illustrating an example of the hardware configuration of the base station 10 and the terminal 20 according to an embodiment of the present disclosure.
  • Network node 30 may have a similar hardware configuration to base station 10.
  • the base station 10 and terminal 20 described above are physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc. Good too.
  • the word “apparatus” can be read as a circuit, a device, a unit, etc.
  • the hardware configuration of the base station 10 and the terminal 20 may be configured to include one or more of each device shown in the figure, or may be configured not to include some of the devices.
  • Each function in the base station 10 and the terminal 20 is performed by loading predetermined software (programs) onto hardware such as the processor 1001 and the storage device 1002, so that the processor 1001 performs calculations and controls communication by the communication device 1004. This is realized by controlling at least one of reading and writing data in the storage device 1002 and the auxiliary storage device 1003.
  • the processor 1001 for example, operates an operating system to control the entire computer.
  • the processor 1001 may be configured with a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, registers, and the like.
  • CPU central processing unit
  • control unit 140, control unit 240, etc. may be implemented by the processor 1001.
  • the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 to the storage device 1002, and executes various processes in accordance with these.
  • programs program codes
  • the control unit 140 of the base station 10 shown in FIG. 14 may be realized by a control program stored in the storage device 1002 and operated on the processor 1001.
  • the control unit 240 of the terminal 20 shown in FIG. 15 may be realized by a control program stored in the storage device 1002 and operated on the processor 1001.
  • Processor 1001 may be implemented by one or more chips. Note that the program may be transmitted from a network via a telecommunications line.
  • the storage device 1002 is a computer-readable recording medium, such as at least one of ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. may be configured.
  • the storage device 1002 may be called a register, cache, main memory, or the like.
  • the storage device 1002 can store executable programs (program codes), software modules, and the like to implement a communication method according to an embodiment of the present disclosure.
  • the auxiliary storage device 1003 is a computer-readable recording medium, such as an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (for example, a compact disk, a digital versatile disk, a Blu-ray disk, etc.). -ray disk), smart card, flash memory (eg, card, stick, key drive), floppy disk, magnetic strip, etc.
  • the above-mentioned storage medium may be, for example, a database including at least one of the storage device 1002 and the auxiliary storage device 1003, a server, or other suitable medium.
  • the communication device 1004 is hardware (transmission/reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc., for example.
  • the communication device 1004 includes, for example, a high frequency switch, a duplexer, a filter, a frequency synthesizer, etc. in order to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). It may be composed of.
  • FDD frequency division duplex
  • TDD time division duplex
  • the transmitting and receiving unit may be physically or logically separated into a transmitting unit and a receiving unit.
  • the input device 1005 is an input device (eg, keyboard, mouse, microphone, switch, button, sensor, etc.) that accepts input from the outside.
  • the output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that performs output to the outside. Note that the input device 1005 and the output device 1006 may have an integrated configuration (for example, a touch panel).
  • each device such as the processor 1001 and the storage device 1002 is connected by a bus 1007 for communicating information.
  • the bus 1007 may be configured using a single bus, or may be configured using different buses for each device.
  • the base station 10 and the terminal 20 also include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), and a field programmable gate array (FPGA).
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • PLD programmable logic device
  • FPGA field programmable gate array
  • a part or all of each functional block may be realized by the hardware.
  • processor 1001 may be implemented using at least one of these hardwares.
  • FIG. 17 shows an example of the configuration of the vehicle 2001.
  • the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, a front wheel 2007, a rear wheel 2008, an axle 2009, an electronic control unit 2010, and various sensors 2021 to 2029. , an information service section 2012 and a communication module 2013.
  • Each aspect/embodiment described in this disclosure may be applied to a communication device mounted on vehicle 2001, for example, may be applied to communication module 2013.
  • the drive unit 2002 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor.
  • the steering unit 2003 includes at least a steering wheel (also referred to as a steering wheel), and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.
  • the electronic control unit 2010 is composed of a microprocessor 2031, memory (ROM, RAM) 2032, and communication port (IO port) 2033. Signals from various sensors 2021 to 2029 provided in the vehicle 2001 are input to the electronic control unit 2010.
  • the electronic control unit 2010 may also be called an ECU (Electronic Control Unit).
  • Signals from various sensors 2021 to 2029 include a current signal from a current sensor 2021 that senses the motor current, a front wheel and rear wheel rotation speed signal obtained by a rotation speed sensor 2022, and a front wheel rotation speed signal obtained by an air pressure sensor 2023. and rear wheel air pressure signals, vehicle speed signals acquired by vehicle speed sensor 2024, acceleration signals acquired by acceleration sensor 2025, accelerator pedal depression amount signals acquired by accelerator pedal sensor 2029, and brake pedal sensor 2026. These include a brake pedal depression amount signal, a shift lever operation signal acquired by the shift lever sensor 2027, a detection signal for detecting obstacles, vehicles, pedestrians, etc. acquired by the object detection sensor 2028, and the like.
  • the information service department 2012 controls various devices such as car navigation systems, audio systems, speakers, televisions, and radios that provide (output) various information such as driving information, traffic information, and entertainment information, and these devices. It is composed of one or more ECUs.
  • the information service unit 2012 provides various multimedia information and multimedia services to the occupants of the vehicle 2001 using information acquired from an external device via the communication module 2013 and the like.
  • the information service department 2012 may include an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.) that accepts input from the outside, and an output device that performs output to the outside (for example, display, speaker, LED lamp, touch panel, etc.).
  • the driving support system unit 2030 includes a millimeter wave radar, LiDAR (Light Detection and Ranging), a camera, a positioning locator (for example, GNSS, etc.), map information (for example, a high-definition (HD) map, an autonomous vehicle (AV) map, etc.) ), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors that prevent accidents and reduce the driver's driving burden.
  • the system is comprised of various devices that provide functions for the purpose and one or more ECUs that control these devices. Further, the driving support system unit 2030 transmits and receives various information via the communication module 2013, and realizes a driving support function or an automatic driving function.
  • Communication module 2013 can communicate with microprocessor 2031 and components of vehicle 2001 via a communication port.
  • the communication module 2013 communicates with the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, electronic Data is transmitted and received between the microprocessor 2031, memory (ROM, RAM) 2032, and sensors 2021 to 29 in the control unit 2010.
  • the communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with external devices. For example, various information is transmitted and received with an external device via wireless communication.
  • the communication module 2013 may be located either inside or outside the electronic control unit 2010.
  • the external device may be, for example, a base station, a mobile station, or the like.
  • the communication module 2013 receives signals from the various sensors 2021 to 2028 described above that are input to the electronic control unit 2010, information obtained based on the signals, and input from the outside (user) obtained via the information service unit 2012. At least one of the information based on the information may be transmitted to an external device via wireless communication.
  • the electronic control unit 2010, various sensors 2021-2028, information service unit 2012, etc. may be called an input unit that receives input.
  • the PUSCH transmitted by the communication module 2013 may include information based on the above input.
  • the communication module 2013 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device, and displays it on the information service section 2012 provided in the vehicle 2001.
  • the information service unit 2012 is an output unit that outputs information (for example, outputs information to devices such as a display and a speaker based on the PDSCH (or data/information decoded from the PDSCH) received by the communication module 2013). may be called.
  • Communication module 2013 also stores various information received from external devices into memory 2032 that can be used by microprocessor 2031 . Based on the information stored in the memory 2032, the microprocessor 2031 controls the drive section 2002, steering section 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheel 2007, rear wheel 2008, and axle 2009 provided in the vehicle 2001. , sensors 2021 to 2029, etc. may be controlled.
  • information indicating that a TAI (Tracking Area Identity) list consisting of tracking areas that provide network slices is supported and network slices that request use are provided.
  • a receiving unit that receives a registration request including information indicating the network slice from the terminal;
  • a control unit that generates a registration permission including information related to the network slice requested to be used based on the registration request;
  • a network node is provided having a transmitter for transmitting.
  • the granularity of providing network slices can be changed from each registered area to each tracking area, and network slices can be provided based on the tracking area where the user is located. That is, in a communication system, flexibility in setting a service area for providing network slices can be improved.
  • the control unit may include, in the registration permission, a TAI list that provides the network slice requested for use.
  • the control unit may include information indicating a network slice with notification of a usable tracking area in the registration permission.
  • the control unit may include information indicating a network slice that cannot be used in the current tracking area in the registration permission.
  • the control unit may include information indicating a tracking area that can be used by the network slice requesting use in the registration permission.
  • the control unit may include information indicating that the network slice requested for use cannot be used in the current tracking area, in the registration permission.
  • a registration including information indicating that a TAI (Tracking Area Identity) list consisting of tracking areas providing network slices is supported and information indicating a network slice requested to be used.
  • a communication method performed by a network node is provided.
  • the granularity of providing network slices can be changed from each registered area to each tracking area, and network slices can be provided based on the tracking area where the user is located. That is, in a communication system, flexibility in setting a service area for providing network slices can be improved.
  • the operations of a plurality of functional sections may be physically performed by one component, or the operations of one functional section may be physically performed by a plurality of components.
  • the order of processing may be changed as long as there is no contradiction.
  • the software that runs on the processor of the network node 30 according to the embodiment of the present invention and the software that runs on the processor that the terminal 20 has according to the embodiment of the present invention are random access memory (RAM), flash memory, read-only memory, respectively. (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.
  • the notification of information is not limited to the aspects/embodiments described in this disclosure, and may be performed using other methods.
  • the notification of information may be physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling). , broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or a combination thereof.
  • RRC signaling may be called an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution-Advanced
  • SUPER 3G IMT-Advanced
  • 4G 4th generation mobile communication system
  • 5G 5th generation mobile communication system
  • FRA Fluture Radio Access
  • NR new Radio
  • W-CDMA registered trademark
  • GSM registered trademark
  • CDMA2000 Code Division Multiple Access 2000
  • UMB Universal Mobile Broadband
  • IEEE 802.11 Wi-Fi (registered trademark)
  • IEEE 802.16 WiMAX (registered trademark)
  • IEEE 802.20 UWB (Ultra-WideBand
  • Bluetooth registered trademark
  • a combination of a plurality of systems may be applied (for example, a combination of at least one of LTE and LTE-A and 5G).
  • Each aspect/embodiment described in this disclosure is LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system). system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is an integer or decimal number, for example)), FRA (Future Radio Access), NR (new Radio), New radio access ( NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802 Systems that utilize .16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth (registered trademark), and other appropriate systems, and that are extended, modified, created, and defined based on these.
  • the present invention may be
  • a specific operation performed by the network node 30 may be performed by its upper node in some cases.
  • various operations performed for communication with terminal 20 are performed by network node 30 and other network nodes other than network node 30 ( It is clear that this can be done by at least one of the following: for example, MME or S-GW (possible, but not limited to).
  • MME Mobility Management Entity
  • S-GW Packet Control Function
  • the other network node may be a combination of multiple other network nodes (for example, MME and S-GW).
  • the information, signals, etc. described in this disclosure can be output from an upper layer (or lower layer) to a lower layer (or upper layer). It may be input/output via multiple network nodes.
  • the input/output information may be stored in a specific location (for example, memory) or may be managed using a management table. Information etc. to be input/output may be overwritten, updated, or additionally written. The output information etc. may be deleted. The input information etc. may be transmitted to other devices.
  • the determination in the present disclosure may be performed based on a value represented by 1 bit (0 or 1), a truth value (Boolean: true or false), or a comparison of numerical values (e.g. , comparison with a predetermined value).
  • Software includes instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, whether referred to as software, firmware, middleware, microcode, hardware description language, or by any other name. , should be broadly construed to mean an application, software application, software package, routine, subroutine, object, executable, thread of execution, procedure, function, etc.
  • software, instructions, information, etc. may be sent and received via a transmission medium.
  • a transmission medium For example, if the software uses wired technology (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.) and/or wireless technology (infrared, microwave, etc.) to create a website, When transmitted from a server or other remote source, these wired and/or wireless technologies are included within the definition of transmission medium.
  • wired technology coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.
  • wireless technology infrared, microwave, etc.
  • data, instructions, commands, information, signals, bits, symbols, chips, etc. which may be referred to throughout the above description, may refer to voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these. It may also be represented by a combination of
  • At least one of the channel and the symbol may be a signal.
  • the signal may be a message.
  • a component carrier may also be called a carrier frequency, a cell, a frequency carrier, or the like.
  • system and “network” are used interchangeably.
  • radio resources may be indicated by an index.
  • Base Station BS
  • wireless base station base station
  • base station device fixed station
  • NodeB NodeB
  • eNodeB eNodeB
  • gNodeB gNodeB
  • a base station is sometimes referred to by terms such as macrocell, small cell, femtocell, and picocell.
  • a base station can accommodate one or more (eg, three) cells. If a base station accommodates multiple cells, the overall coverage area of the base station can be partitioned into multiple smaller areas, and each smaller area is divided into multiple subsystems (e.g., small indoor base stations (RRHs)). Communication services can also be provided by Remote Radio Head).
  • RRHs small indoor base stations
  • Communication services can also be provided by Remote Radio Head).
  • the term "cell” or “sector” refers to part or all of the coverage area of a base station and/or base station subsystem that provides communication services in this coverage.
  • the base station transmitting information to the terminal may be read as the base station instructing the terminal to control/operate based on the information.
  • MS Mobile Station
  • UE User Equipment
  • a mobile station is defined by a person skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless It may also be referred to as a terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.
  • At least one of a base station and a mobile station may be called a transmitting device, a receiving device, a communication device, etc.
  • the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, or the like.
  • the moving body refers to a movable object, and the moving speed is arbitrary. Naturally, this also includes cases where the moving object is stopped.
  • the mobile objects include, for example, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, carts, rickshaws, ships and other watercraft.
  • the mobile object may be a mobile object that autonomously travels based on a travel command. It may be a vehicle (e.g. car, airplane, etc.), an unmanned moving object (e.g. drone, self-driving car, etc.), or a robot (manned or unmanned). good.
  • the base station and the mobile station includes devices that do not necessarily move during communication operations.
  • at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.
  • IoT Internet of Things
  • the base station in the present disclosure may be replaced by a user terminal.
  • communication between a base station and a user terminal is replaced with communication between a plurality of terminals 20 (for example, it may be called D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.).
  • the terminal 20 may have the functions that the network node 30 described above has.
  • words such as "up” and “down” may be replaced with words corresponding to inter-terminal communication (for example, "side”).
  • uplink channels, downlink channels, etc. may be replaced with side channels.
  • the user terminal in the present disclosure may be replaced with a base station.
  • the base station may have the functions that the user terminal described above has.
  • determining may encompass a wide variety of operations.
  • “Judgment” and “decision” include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, search, and inquiry. (e.g., searching in a table, database, or other data structure), and regarding an ascertaining as a “judgment” or “decision.”
  • judgment and “decision” refer to receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, and access.
  • (accessing) may include considering something as a “judgment” or “decision.”
  • judgment and “decision” refer to resolving, selecting, choosing, establishing, comparing, etc. as “judgment” and “decision”. may be included.
  • judgment and “decision” may include regarding some action as having been “judged” or “determined.”
  • judgment (decision) may be read as “assuming", “expecting", “considering”, etc.
  • connection refers to any connection or coupling, direct or indirect, between two or more elements and to each other. It may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled.”
  • the bonds or connections between elements may be physical, logical, or a combination thereof. For example, "connection” may be replaced with "access.”
  • two elements may include one or more electrical wires, cables, and/or printed electrical connections, as well as in the radio frequency domain, as some non-limiting and non-inclusive examples. , electromagnetic energy having wavelengths in the microwave and optical (both visible and non-visible) ranges.
  • the reference signal can also be abbreviated as RS (Reference Signal), and may be called a pilot depending on the applied standard.
  • RS Reference Signal
  • the phrase “based on” does not mean “based solely on” unless explicitly stated otherwise. In other words, the phrase “based on” means both “based only on” and “based at least on.”
  • any reference to elements using the designations "first,” “second,” etc. does not generally limit the amount or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Thus, reference to a first and second element does not imply that only two elements may be employed or that the first element must precede the second element in any way.
  • a and B are different may mean “A and B are different from each other.” Note that the term may also mean that "A and B are each different from C”. Terms such as “separate” and “coupled” may also be interpreted similarly to “different.”
  • notification of prescribed information is not limited to being done explicitly, but may also be done implicitly (for example, not notifying the prescribed information). Good too.
  • S-NSSAI is an example of information indicating a network slice.
  • Base station 110 Transmitting section 120 Receiving section 130 Setting section 140 Control section 20 Terminal 210 Transmitting section 220 Receiving section 230 Setting section 240 Control section 30 Network node 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive section 2003 Steering section 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Front wheel 2008 Rear wheel 2009 Axle 2010 Electronic control section 2012 Information service section 2013 Communication module 2021 Current sensor 2022 Rotational speed sensor 2023 Air pressure sensor 2024 Vehicle speed sensor 202 5 Acceleration Sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driving support system section 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port (IO port)

Abstract

This network node comprises: a reception unit for receiving, from a terminal, a registration request including information indicating supporting of a tracking area identity (TAI) list composed of tracking areas in which network slices are provided, and information indicating a network slice for which use is requested; a control unit for generating, on the basis of the registration request, a registration acceptance including information relating to the network slice for which use is requested; and a transmission unit for transmitting the registration acceptance to the terminal.

Description

ネットワークノード及び通信方法Network nodes and communication methods
　本発明は、通信システムにおけるネットワークノード及び通信方法に関する。 The present invention relates to a network node and a communication method in a communication system.
　３ＧＰＰ（3rd Generation Partnership Project）では、システム容量の更なる大容量化、データ伝送速度の更なる高速化、無線区間における更なる低遅延化等を実現するために、５ＧあるいはＮＲ（New Radio）と呼ばれる無線通信方式（以下、当該無線通信方式を「５Ｇ」あるいは「ＮＲ」という。）の検討が進んでいる。５Ｇでは、１０Ｇｂｐｓ以上のスループットを実現しつつ無線区間の遅延を１ｍｓ以下にするという要求条件を満たすために、様々な無線技術の検討が行われている。 In the 3GPP (3rd Generation Partnership Project), 5G or NR (New Radio) is being developed in order to further increase system capacity, further increase data transmission speed, and further reduce latency in wireless sections. Studies are progressing on a wireless communication system called ``5G'' (hereinafter referred to as ``5G'' or ``NR''). In 5G, various wireless technologies are being studied in order to meet the requirements of achieving a throughput of 10 Gbps or more while reducing the delay in the wireless section to 1 ms or less.
　ＮＲでは、ＬＴＥ（Long Term Evolution）のネットワークアーキテクチャにおけるコアネットワークであるＥＰＣ（Evolved Packet Core）に対応する５ＧＣ（5G Core Network）及びＬＴＥのネットワークアーキテクチャにおけるＲＡＮ（Radio Access Network）であるＥ－ＵＴＲＡＮ（Evolved Universal Terrestrial Radio Access Network）に対応するＮＧ－ＲＡＮ（Next Generation - Radio Access Network）を含むネットワークアーキテクチャが検討されている（例えば非特許文献１及び非特許文献２）。 In NR, 5GC (5G Core Network) corresponds to EPC (Evolved Packet Core), which is the core network in LTE (Long Term Evolution) network architecture, and E-UTRAN (RAN), which is RAN (Radio Access Network) in LTE network architecture. Network architectures including NG-RAN (Next Generation - Radio Access Network) corresponding to Evolved Universal Terrestrial Radio Access Network are being considered (for example, Non-Patent Document 1 and Non-Patent Document 2).
　通信事業者がユーザにサービスを提供するためのネットワークスライスが５ＧＣにおいて運用されている。従来、ネットワークスライスを提供するサービスエリアは、登録エリア（Registration area, RA）ごとに設定されていた。そのため、ネットワークスライスを登録エリアに対応する地理的範囲とは異なるサービスエリアで提供することが困難であった。 A network slice for communication carriers to provide services to users is operated in 5GC. Conventionally, service areas that provide network slices have been set for each registration area (RA). Therefore, it has been difficult to provide network slices in a service area different from the geographical range corresponding to the registered area.
　本発明は上記の点に鑑みてなされたものであり、通信システムにおいて、ネットワークスライスを提供するサービスエリア設定の柔軟性を向上させることを目的とする。 The present invention has been made in view of the above points, and an object of the present invention is to improve the flexibility of setting a service area for providing network slices in a communication system.
　開示の技術によれば、ネットワークスライスを提供するトラッキングエリアで構成されるＴＡＩ（Tracking Area Identity）リストをサポートすることを示す情報及び使用を要求するネットワークスライスを示す情報を含む登録要求を端末から受信する受信部と、前記登録要求に基づいて、前記使用を要求するネットワークスライスに係る情報を含む登録許可を生成する制御部と、前記登録許可を前記端末に送信する送信部とを有するネットワークノードが提供される。 According to the disclosed technology, a registration request is received from a terminal, including information indicating that a TAI (Tracking Area Identity) list consisting of tracking areas that provide network slices is supported and information indicating a network slice that is requested to be used. a control unit that generates, based on the registration request, a registration permission that includes information related to the network slice that is requested to be used; and a transmission unit that transmits the registration permission to the terminal. provided.
　開示の技術によれば、通信システムにおいて、ネットワークスライスを提供するサービスエリア設定の柔軟性を向上させることができる。 According to the disclosed technology, it is possible to improve the flexibility of setting a service area for providing network slices in a communication system.
通信システムの例を説明するための図である。FIG. 1 is a diagram for explaining an example of a communication system. ローミング環境下の通信システムの例を説明するための図である。FIG. 2 is a diagram for explaining an example of a communication system under a roaming environment. ネットワークスライスに接続する例（１）を示す図である。FIG. 3 is a diagram showing an example (1) of connecting to a network slice. ネットワークスライスに接続する例（２）を示す図である。It is a figure which shows the example (2) of connecting to a network slice. ネットワークスライスに接続する例（３）を示す図である。It is a figure which shows the example (3) of connecting to a network slice. 本発明の実施の形態における登録要求の例（１）を説明するためのシーケンス図である。It is a sequence diagram for explaining example (1) of a registration request in an embodiment of the present invention. 本発明の実施の形態における登録要求の例（２）を説明するためのシーケンス図である。FIG. 7 is a sequence diagram for explaining example (2) of a registration request in the embodiment of the present invention. 本発明の実施の形態における登録要求の例（３）を説明するためのシーケンス図である。FIG. 7 is a sequence diagram for explaining example (3) of a registration request in the embodiment of the present invention. 本発明の実施の形態における登録要求の例（４）を説明するためのシーケンス図である。FIG. 7 is a sequence diagram for explaining example (4) of a registration request in the embodiment of the present invention. 本発明の実施の形態における登録要求の例（５）を説明するためのシーケンス図である。FIG. 7 is a sequence diagram for explaining example (5) of a registration request in the embodiment of the present invention. 本発明の実施の形態におけるストレージ動作の例を示す図である。FIG. 3 is a diagram showing an example of storage operation in an embodiment of the present invention. 本発明の実施の形態における端末移動時の例を示す図である。FIG. 3 is a diagram illustrating an example when a terminal moves according to an embodiment of the present invention. 本発明の実施の形態における端末移動時の例を説明するためのシーケンス図である。FIG. 3 is a sequence diagram for explaining an example when a terminal moves in an embodiment of the present invention. 本発明の実施の形態における基地局１０の機能構成の一例を示す図である。1 is a diagram showing an example of a functional configuration of a base station 10 in an embodiment of the present invention. 本発明の実施の形態における端末２０の機能構成の一例を示す図である。It is a diagram showing an example of a functional configuration of a terminal 20 in an embodiment of the present invention. 本発明の実施の形態における基地局１０及び端末２０のハードウェア構成の一例を示す図である。It is a diagram showing an example of the hardware configuration of a base station 10 and a terminal 20 in an embodiment of the present invention. 本発明の実施の形態における車両２００１の構成の一例を示す図である。It is a figure showing an example of composition of vehicle 2001 in an embodiment of the present invention.
　以下、図面を参照して本発明の実施の形態を説明する。なお、以下で説明する実施の形態は一例であり、本発明が適用される実施の形態は、以下の実施の形態に限られない。 Embodiments of the present invention will be described below with reference to the drawings. Note that the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.
　本発明の実施の形態の無線通信システムの動作にあたっては、適宜、既存技術が使用される。ただし、当該既存技術は、例えば既存のＬＴＥであるが、既存のＬＴＥに限られない。また、本明細書で使用する用語「ＬＴＥ」は、特に断らない限り、ＬＴＥ－Ａｄｖａｎｃｅｄ、及び、ＬＴＥ－Ａｄｖａｎｃｅｄ以降の方式（例：ＮＲ）、又は無線ＬＡＮ（Local Area Network）を含む広い意味を有するものとする。 Existing technologies are used as appropriate for the operation of the wireless communication system according to the embodiment of the present invention. However, the existing technology is, for example, existing LTE, but is not limited to existing LTE. Furthermore, unless otherwise specified, the term "LTE" used in this specification has a broad meaning including LTE-Advanced and a system after LTE-Advanced (e.g. NR), or wireless LAN (Local Area Network). shall have.
　また、本発明の実施の形態において、無線パラメータ等が「設定される（Configure）」とは、所定の値が予め設定（Pre-configure）されることであってもよいし、ネットワークノード３０又は端末２０から通知される無線パラメータが設定されることであってもよい。 Furthermore, in the embodiment of the present invention, "configure" the wireless parameters etc. may mean pre-configuring a predetermined value, or may mean that the network node 30 or Wireless parameters notified from the terminal 20 may also be set.
　図１は、通信システムの例を説明するための図である。図１に示されるように、通信システムは、端末２０であるＵＥ、複数のネットワークノード３０から構成される。以下、機能ごとに１つのネットワークノード３０が対応するものとするが、複数の機能を１つのネットワークノード３０が実現してもよいし、複数のネットワークノード３０が１つの機能を実現してもよい。また、以下に記載する「接続」は、論理的な接続であってもよいし、物理的な接続であってもよい。 FIG. 1 is a diagram for explaining an example of a communication system. As shown in FIG. 1, the communication system includes a UE, which is a terminal 20, and a plurality of network nodes 30. Hereinafter, it is assumed that one network node 30 corresponds to each function, but one network node 30 may realize multiple functions, or multiple network nodes 30 may realize one function. . Further, the "connection" described below may be a logical connection or a physical connection.
　ＲＡＮ（Radio Access Network）は、無線アクセス機能を有するネットワークノード３０であり、基地局１０を含んでもよく、ＵＥ、ＡＭＦ（Access and Mobility Management Function）及びＵＰＦ（User plane function）と接続される。ＡＭＦは、ＲＡＮインタフェースの終端、ＮＡＳ（Non-Access Stratum）の終端、登録管理、接続管理、到達性管理、モビリティ管理等の機能を有するネットワークノード３０である。ＵＰＦは、ＤＮ（Data Network）と相互接続する外部に対するＰＤＵ（Protocol Data Unit）セッションポイント、パケットのルーティング及びフォワーディング、ユーザプレーンのＱｏＳ（Quality of Service）ハンドリング等の機能を有するネットワークノード３０である。ＵＰＦ及びＤＮは、ネットワークスライスを構成する。本発明の実施の形態における無線通信ネットワークでは、複数のネットワークスライスが構築されてもよい。 The RAN (Radio Access Network) is a network node 30 having a radio access function, may include the base station 10, and is connected to the UE, the AMF (Access and Mobility Management Function), and the UPF (User plane function). The AMF is a network node 30 having functions such as RAN interface termination, NAS (Non-Access Stratum) termination, registration management, connection management, reachability management, and mobility management. The UPF is a network node 30 that has functions such as a PDU (Protocol Data Unit) session point for the outside that interconnects with a DN (Data Network), packet routing and forwarding, and user plane QoS (Quality of Service) handling. The UPF and DN constitute a network slice. A plurality of network slices may be constructed in a wireless communication network according to an embodiment of the present invention.
　ＡＭＦは、ＵＥ、ＲＡＮ、ＳＭＦ（Session Management function）、ＮＳＳＦ（Network Slice Selection Function）、ＮＥＦ（Network Exposure Function）、ＮＲＦ（Network Repository Function）、ＵＤＭ（Unified Data Management）、ＡＵＳＦ（Authentication Server Function）、ＰＣＦ（Policy Control Function）、ＡＦ（Application Function）と接続される。ＡＭＦ、ＳＭＦ、ＮＳＳＦ、ＮＥＦ、ＮＲＦ、ＵＤＭ、ＡＵＳＦ、ＰＣＦ、ＡＦは、各々のサービスに基づくインタフェース、Ｎａｍｆ、Ｎｓｍｆ、Ｎｎｓｓｆ、Ｎｎｅｆ、Ｎｎｒｆ、Ｎｕｄｍ、Ｎａｕｓｆ、Ｎｐｃｆ、Ｎａｆを介して相互に接続されるネットワークノード３０である。 AMF includes UE, RAN, SMF (Session Management function), NSSF (Network Slice Selection Function), NEF (Network Exposure Function), NRF (Network Repository Function), UDM (Unified Data Management), AUSF (Authentication Server Function), Connected to PCF (Policy Control Function) and AF (Application Function). AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are interconnected through their respective service-based interfaces, Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf. This is a network node 30.
　ＳＭＦは、セッション管理、ＵＥのＩＰ（Internet Protocol）アドレス割り当て及び管理、ＤＨＣＰ（Dynamic Host Configuration Protocol）機能、ＡＲＰ（Address Resolution Protocol）プロキシ、ローミング機能等の機能を有するネットワークノード３０である。ＮＥＦは、他のＮＦ（Network Function）に能力及びイベントを通知する機能を有するネットワークノード３０である。ＮＳＳＦは、ＵＥが接続するネットワークスライスの選択、許可されるＮＳＳＡＩ（Network Slice Selection Assistance Information）の決定、設定されるＮＳＳＡＩの決定、ＵＥが接続するＡＭＦセットの決定等の機能を有するネットワークノード３０である。ＰＣＦは、ネットワークのポリシ制御を行う機能を有するネットワークノード３０である。ＡＦは、アプリケーションサーバを制御する機能を有するネットワークノード３０である。ＮＲＦは、サービスを提供するＮＦインスタンスを発見する機能を有するネットワークノード３０である。ＵＤＭは、加入者データ及び認証データを管理するネットワークノード３０である。ＵＤＭは、当該データを保持するＵＤＲ（User Data Repository）と接続される。 The SMF is a network node 30 that has functions such as session management, UE IP (Internet Protocol) address assignment and management, DHCP (Dynamic Host Configuration Protocol) function, ARP (Address Resolution Protocol) proxy, and roaming function. The NEF is a network node 30 that has a function of notifying other NFs (Network Functions) of capabilities and events. The NSSF is a network node 30 that has functions such as selecting a network slice to which a UE connects, determining permitted NSSAI (Network Slice Selection Assistance Information), determining NSSAI to be configured, and determining an AMF set to which a UE connects. be. The PCF is a network node 30 that has a function of controlling network policy. AF is a network node 30 that has a function of controlling an application server. An NRF is a network node 30 that has the ability to discover NF instances that provide services. The UDM is a network node 30 that manages subscriber data and authentication data. The UDM is connected to a UDR (User Data Repository) that holds the data.
　図２は、ローミング環境下の通信システムの例を説明するための図である。図２に示されるように、ネットワークは、端末２０であるＵＥ、複数のネットワークノード３０から構成される。以下、機能ごとに１つのネットワークノード３０が対応するものとするが、複数の機能を１つのネットワークノード３０が実現してもよいし、複数のネットワークノード３０が１つの機能を実現してもよい。また、以下に記載する「接続」は、論理的な接続であってもよいし、物理的な接続であってもよい。 FIG. 2 is a diagram for explaining an example of a communication system under a roaming environment. As shown in FIG. 2, the network is composed of a UE, which is a terminal 20, and a plurality of network nodes 30. Hereinafter, it is assumed that one network node 30 corresponds to each function, but one network node 30 may realize multiple functions, or multiple network nodes 30 may realize one function. . Further, the "connection" described below may be a logical connection or a physical connection.
　ＲＡＮは、無線アクセス機能を有するネットワークノード３０であり、ＵＥ、ＡＭＦ及びＵＰＦと接続される。ＡＭＦは、ＲＡＮインタフェースの終端、ＮＡＳの終端、登録管理、接続管理、到達性管理、モビリティ管理等の機能を有するネットワークノード３０である。ＵＰＦは、ＤＮと相互接続する外部に対するＰＤＵセッションポイント、パケットのルーティング及びフォワーディング、ユーザプレーンのＱｏＳハンドリング等の機能を有するネットワークノード３０である。ＵＰＦ及びＤＮは、ネットワークスライスを構成する。本発明の実施の形態における無線通信ネットワークでは、複数のネットワークスライスが構築されている。 The RAN is a network node 30 that has a radio access function and is connected to the UE, AMF, and UPF. The AMF is a network node 30 that has functions such as RAN interface termination, NAS termination, registration management, connection management, reachability management, and mobility management. The UPF is a network node 30 that has functions such as a PDU session point for the outside that interconnects with the DN, packet routing and forwarding, and user plane QoS handling. The UPF and DN constitute a network slice. In the wireless communication network according to the embodiment of the present invention, a plurality of network slices are constructed.
　ＡＭＦは、ＵＥ、ＲＡＮ、ＳＭＦ、ＮＳＳＦ、ＮＥＦ、ＮＲＦ、ＵＤＭ、ＡＵＳＦ、ＰＣＦ、ＡＦ、ＳＥＰＰ（Security Edge Protection Proxy）と接続される。ＡＭＦ、ＳＭＦ、ＮＳＳＦ、ＮＥＦ、ＮＲＦ、ＵＤＭ、ＡＵＳＦ、ＰＣＦ、ＡＦは、各々のサービスに基づくインタフェース、Ｎａｍｆ、Ｎｓｍｆ、Ｎｎｓｓｆ、Ｎｎｅｆ、Ｎｎｒｆ、Ｎｕｄｍ、Ｎａｕｓｆ、Ｎｐｃｆ、Ｎａｆを介して相互に接続されるネットワークノード３０である。 AMF is connected to UE, RAN, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, AF, and SEPP (Security Edge Protection Proxy). AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are interconnected through their respective service-based interfaces, Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf. This is a network node 30.
　ＳＭＦは、セッション管理、ＵＥのＩＰアドレス割り当て及び管理、ＤＨＣＰ機能、ＡＲＰプロキシ、ローミング機能等の機能を有するネットワークノード３０である。ＮＥＦは、他のＮＦに能力及びイベントを通知する機能を有するネットワークノード３０である。ＮＳＳＦは、ＵＥが接続するネットワークスライスの選択、許可されるＮＳＳＡＩの決定、設定されるＮＳＳＡＩの決定、ＵＥが接続するＡＭＦセットの決定等の機能を有するネットワークノード３０である。ＰＣＦは、ネットワークのポリシ制御を行う機能を有するネットワークノード３０である。ＡＦは、アプリケーションサーバを制御する機能を有するネットワークノード３０である。ＮＲＦは、サービスを提供するＮＦインスタンスを発見する機能を有するネットワークノード３０である。ＳＥＰＰは、非透過的なプロキシであり、ＰＬＭＮ（Public Land Mobile Network）間のコントロールプレーンのメッセージをフィルタリングする。図２に示されるｖＳＥＰＰは、ｖｉｓｉｔｅｄネットワークにおけるＳＥＰＰであり、ｈＳＥＰＰは、ｈｏｍｅネットワークにおけるＳＥＰＰである。 The SMF is a network node 30 that has functions such as session management, UE IP address assignment and management, DHCP function, ARP proxy, and roaming function. A NEF is a network node 30 that has the ability to notify other NFs of capabilities and events. The NSSF is a network node 30 that has functions such as selecting a network slice to which a UE connects, determining permitted NSSAIs, determining NSSAIs to be configured, and determining an AMF set to which a UE connects. The PCF is a network node 30 that has a function of controlling network policy. AF is a network node 30 that has a function of controlling an application server. An NRF is a network node 30 that has the ability to discover NF instances that provide services. SEPP is a non-transparent proxy that filters control plane messages between PLMNs (Public Land Mobile Networks). The vSEPP shown in FIG. 2 is the SEPP in the visited network, and the hSEPP is the SEPP in the home network.
　図２に示されるように、ＵＥは、ＶＰＬＭＮ（Visited PLMN）においてＲＡＮ及びＡＭＦと接続されているローミング環境にある。ＶＰＬＭＮ及びＨＰＬＭＮ（Home PLMN）は、ｖＳＥＰＰ及びｈＳＥＰＰを経由して接続されている。ＵＥは、例えば、ＶＰＬＭＮのＡＭＦを介してＨＰＬＭＮのＵＤＭと通信が可能である。 As shown in FIG. 2, the UE is in a roaming environment connected to the RAN and AMF in a VPLMN (Visited PLMN). VPLMN and HPLMN (Home PLMN) are connected via vSEPP and hSEPP. The UE can communicate with the HPLMN's UDM via the VPLMN's AMF, for example.
　ここで、通信事業者がユーザにサービスを提供するためのネットワークスライスが５ＧＣにおいて運用されている。従来、ネットワークスライスを提供するサービスエリアは、登録エリア（Registration area, RA）ごとに設定されていた。例えば、登録エリアを構成するトラッキングエリア（Tracking area, TA）の境界に、ネットワークスライスを提供するサービスエリアの境界は一致していた。そのため、ネットワークスライスを登録エリアに対応する地理的範囲とは異なるサービスエリアで提供することが困難であった。 Here, a network slice for communication carriers to provide services to users is operated in 5GC. Conventionally, service areas that provide network slices have been set for each registration area (RA). For example, the boundaries of the service area that provides network slices coincided with the boundaries of the tracking area (TA) that constitutes the registered area. Therefore, it has been difficult to provide network slices in a service area different from the geographical range corresponding to the registered area.
　図３は、ネットワークスライスに接続する例（１）を示す図である。図３に示されるように、Ｓ－ＮＳＳＡＩ（Single Network Slice Selection Assistance Information）＃１のサービスエリアが対応する登録エリアは、ＴＡ１、ＴＡ２及びＴＡ３から構成され、Ｓ－ＮＳＳＡＩ＃２のサービスエリアが対応する登録エリアは、ＴＡ４、ＴＡ５及びＴＡ６から構成されるものとする。図３の例は、Ｓ－ＮＳＳＡＩ＃１のサービスエリアが登録エリアの境界と一致するケースである。 FIG. 3 is a diagram showing an example (1) of connecting to a network slice. As shown in Figure 3, the registration area that the service area of S-NSSAI (Single Network Slice Selection Assistance Information) #1 corresponds to consists of TA1, TA2, and TA3, and the service area of S-NSSAI #2 corresponds to. It is assumed that the registration area consists of TA4, TA5, and TA6. The example in FIG. 3 is a case where the service area of S-NSSAI #1 coincides with the boundary of the registration area.
　例えば、ＵＥがＴＡ５において、Ｓ－ＮＳＳＡＩ＃１に接続要求する（Requested NSSAI(S-NSSAI#1)）登録要求をネットワークに送信すると、ネットワークは、Ｓ－ＮＳＳＡＩ＃１への接続が利用できないことを示す応答（Rejected NSSAI(S-NSSAI#1)）をＵＥに送信する。当該応答のＣａｕｓｅ値は、現在の登録エリアでは該当のＳ－ＮＳＳＡＩは利用できないことを示す。 For example, when the UE sends a registration request (Requested NSSAI (S-NSSAI#1)) to the network in TA5, the network indicates that the connection to S-NSSAI #1 is not available. A response (Rejected NSSAI (S-NSSAI#1)) indicating this is sent to the UE. The Cause value of the response indicates that the corresponding S-NSSAI is not available in the current registration area.
　図４は、ネットワークスライスに接続する例（２）を示す図である。図４に示されるように、Ｓ－ＮＳＳＡＩ＃１のサービスエリアが対応するトラッキングエリアは、ＴＡ１、ＴＡ２、ＴＡ３及びＴＡ４から構成され、Ｓ－ＮＳＳＡＩ＃２のサービスエリアが対応するトラッキングエリアは、ＴＡ５及びＴＡ６から構成されるものとする。図４に示されるように、Ｓ－ＮＳＳＡＩ＃１のサービスエリアが登録エリアの境界と一致しないケースが想定される。 FIG. 4 is a diagram showing an example (2) of connecting to a network slice. As shown in FIG. 4, the tracking area to which the service area of S-NSSAI#1 corresponds is composed of TA1, TA2, TA3, and TA4, and the tracking area to which the service area of S-NSSAI#2 corresponds is TA5. and TA6. As shown in FIG. 4, a case is assumed in which the service area of S-NSSAI #1 does not coincide with the boundary of the registration area.
　図３と同様に、ＵＥがＴＡ５において、Ｓ－ＮＳＳＡＩ＃１に接続要求する（Requested NSSAI(S-NSSAI#1)）登録要求をネットワークに送信すると、ネットワークは、Ｓ－ＮＳＳＡＩ＃１への接続が利用できないことを示す応答（Rejected NSSAI(S-NSSAI#1)）をＵＥに送信する。当該応答のＣａｕｓｅ値は、現在の登録エリアではＳ－ＮＳＳＡＩは利用できないことを示す。 Similar to FIG. 3, when the UE sends a registration request (Requested NSSAI (S-NSSAI#1)) to the network in TA5, the network requests connection to S-NSSAI #1. A response (Rejected NSSAI (S-NSSAI#1)) is sent to the UE indicating that the The Cause value of the response indicates that S-NSSAI is not available in the current registration area.
　図５は、ネットワークスライスに接続する例（３）を示す図である。図５に示されるように、Ｓ－ＮＳＳＡＩ＃１のサービスエリアが対応するトラッキングエリアは、ＴＡ１、ＴＡ２、ＴＡ３及びＴＡ４から構成され、Ｓ－ＮＳＳＡＩ＃２のサービスエリアが対応するトラッキングエリアは、ＴＡ５及びＴＡ６から構成されるものとする。図５に示されるように、ＵＥがＴＡ５で登録要求を行い、ネットワークからＳ－ＮＳＳＡＩ＃１への接続が利用できないことを示す応答（Rejected NSSAI(S-NSSAI#1)）を受信したのち、同一登録エリア内のＴＡ４に移動した場合、ネットワークスライスのサービスとしてはＳ－ＮＳＳＡＩ＃１が使用できるはずが、ＵＥはＴＡ５で、Ｃａｕｓｅ値により現在の登録エリアではＳ－ＮＳＳＡＩ＃１への接続が利用できないことを示す応答を受信してＮＳＳＡＩストレージでＳ－ＮＳＳＡＩ＃１が利用できないＮＳＳＡＩとして保持されているため、ＵＥはＴＡ４を利用することができない。 FIG. 5 is a diagram showing an example (3) of connecting to a network slice. As shown in FIG. 5, the tracking area to which the service area of S-NSSAI#1 corresponds is composed of TA1, TA2, TA3, and TA4, and the tracking area to which the service area of S-NSSAI#2 corresponds is TA5. and TA6. As shown in FIG. 5, after the UE makes a registration request at TA5 and receives a response (Rejected NSSAI(S-NSSAI#1)) from the network indicating that the connection to S-NSSAI#1 is not available, If the UE moves to TA4 in the same registration area, it should be possible to use S-NSSAI #1 as a network slice service, but the UE is in TA5 and the Cause value prevents it from connecting to S-NSSAI #1 in the current registration area. Since the response indicating that S-NSSAI #1 is not available is received and the S-NSSAI #1 is held as an unavailable NSSAI in the NSSAI storage, the UE cannot use TA4.
　そこで、ＵＥが登録要求をネットワークに送信したとき、当該ネットワークスライスに接続できないエリアであっても、ネットワークへのアクセスのみを許容してもよい。また、ＵＥが登録要求をネットワークに送信したとき、当該ネットワークスライスに接続できないエリアである場合、ネットワークはＵＥに当該ネットワークスライスを使用できるトラッキングエリアを通知してもよい。また、ＵＥが登録要求をネットワークに送信したとき、当該ネットワークスライスに接続できないエリアである場合、ネットワークはＵＥに使用できるトラッキングエリア及び使用できないトラッキングエリアを通知してもよい。また、ＵＥが登録要求をネットワークに送信したとき、当該ネットワークスライスに接続できないエリアである場合、ネットワークは接続を拒否し、使用できるエリアをＵＥに通知してもよい。 Therefore, when the UE sends a registration request to the network, it may only allow access to the network even if it is in an area that cannot be connected to the network slice. Further, when the UE sends a registration request to the network, if the area is not connectable to the network slice, the network may notify the UE of a tracking area where the network slice can be used. Further, when the UE sends a registration request to the network, if the area is not connectable to the network slice, the network may notify the UE of the usable and unusable tracking areas. Further, when the UE sends a registration request to the network, if the network slice cannot be connected to the area, the network may refuse the connection and notify the UE of the usable area.
　図６は、本発明の実施の形態における登録要求の例（１）を説明するためのシーケンス図である。ステップＳ１０１において、ＵＥ２０は、第１の情報を含む登録要求（Registration request）をＡＭＦ３０Ａに送信する。第１の情報は、ネットワークスライスを考慮した登録エリアすなわち対応するＴＡＩ（Tracking Area Identity）リストをＵＥがサポートすることを示す情報であってもよい。ＵＥは第１の情報によりネットワークスライスを考慮した登録エリアすなわち対応するＴＡＩリストの生成をネットワークに要求してもよい。第１の情報は、ＴＡＩリスト生成に係るＵＥの優先傾向を示す。例えば、ネットワークスライスを考慮した登録エリア構成を優先することを示す。 FIG. 6 is a sequence diagram for explaining example (1) of a registration request in the embodiment of the present invention. In step S101, the UE 20 transmits a registration request including first information to the AMF 30A. The first information may be information indicating that the UE supports a registration area that takes network slices into consideration, ie a corresponding TAI (Tracking Area Identity) list. The UE may request the network to generate a registration area, ie, a corresponding TAI list, taking network slices into consideration using the first information. The first information indicates the UE's priority tendency regarding TAI list generation. For example, it indicates that priority is given to a registration area configuration that takes network slices into consideration.
　一つの登録エリア（ＲＡ）の中で特定のＳ－ＮＳＳＡＩが使用できるＴＡと使用できないＴＡが混在するケースを想定する。第１の情報は、５ＧＭＭ　ｃａｐａｂｉｌｉｔｙ　ＩＥに設定されていてもよい。ネットワークスライスを考慮したとは、ＵＥが要求した（Ｒｅｑｕｅｓｔｅｄ　ＮＳＳＡＩ　ＩＥに含めた）Ｓ－ＮＳＳＡＩをサポートしている（当該Ｓ－ＮＳＳＡＩを当該ＴＡで利用できる）ＴＡのみで構成されたＴＡＩリストを生成するように考慮、という意味であってもよい。もしくは、ネットワークスライスを考慮したとは、ＵＥのＳｕｂｓｃｒｉｂｅｄ　Ｓ－ＮＳＳＡＩをサポートしているＴＡのみで構成されたＴＡＩリストを生成するように考慮、という意味であってもよい。 Assume a case in which TAs that can use a specific S-NSSAI and TAs that cannot use it coexist within one registration area (RA). The first information may be set in the 5GMM capability IE. Considering network slices means generating a TAI list consisting only of TAs that support the S-NSSAI requested by the UE (included in the Requested NSSAI IE) (the S-NSSAI can be used by the TA). It may also mean "to take into account". Alternatively, considering the network slice may mean that consideration is given to generating a TAI list consisting only of TAs that support the subscribed S-NSSAI of the UE.
　続くステップＳ１０２において、ＡＭＦ３０Ａは、ネットワークスライスを考慮したＴＡＩリストを生成する。続くステップＳ１０３において、ＡＭＦ３０Ａは、第１１の情報及び第１２の情報を含む登録許可をＵＥ２０に送信する。第１１の情報は、ネットワークスライスを考慮した登録エリアすなわち対応するＴＡＩリストであってもよい。ネットワークスライスを考慮した登録エリアすなわち対応するＴＡＩリストとは、ＵＥが要求した（Ｒｅｑｕｅｓｔｅｄ　ＮＳＳＡＩ　ＩＥに含めた）Ｓ－ＮＳＳＡＩをサポートするＴＡのみで構成されたＴＡＩリストであってもよい。もしくは、ネットワークスライスを考慮した登録エリアすなわち対応するＴＡＩリストとは、ＵＥのＳｕｂｓｃｒｉｂｅｄ　Ｓ－ＮＳＳＡＩをサポートしているＴＡのみで構成されたＴＡＩリストであってもよい。第１１の情報はＴＡＩリストＩＥに含まれてもよい。 In the following step S102, the AMF 30A generates a TAI list that takes network slices into consideration. In subsequent step S103, the AMF 30A transmits registration permission including the eleventh information and the twelfth information to the UE 20. The eleventh information may be a registration area considering network slices, that is, a corresponding TAI list. The registration area that takes network slice into consideration, that is, the corresponding TAI list, may be a TAI list that is configured only of TAs that support S-NSSAI requested by the UE (included in the Requested NSSAI IE). Alternatively, the registration area considering network slices, that is, the corresponding TAI list, may be a TAI list composed only of TAs that support the UE's Subscribed S-NSSAI. The eleventh information may be included in the TAI list IE.
　第１１の情報を受信したＵＥは、ネットワークスライスを考慮した登録エリア（ＴＡＩリスト）から他のＲＡに移動することでＲｅｊｅｃｔｅｄ　ＮＳＳＡＩに含まれる第１２の情報を次の登録手順で使用できるようにしてもよい。 The UE that has received the 11th information moves from the registration area (TAI list) considering network slices to another RA so that the 12th information included in the Rejected NSSAI can be used in the next registration procedure. Good too.
　例えば、ＴＡ＃１とＴＡ＃２とＴＡ＃３があり、ＴＡ＃１とＴＡ＃２はＳ－ＮＳＳＡＩ＃１をサポートしており、ＴＡ＃３はＳ－ＮＳＳＡＩ＃１をサポートしていないがＳ－ＮＳＳＡＩ＃２をサポートしているようなケースを想定する。ＵＥがＴＡ＃３に在圏している時にＳ－ＮＳＳＡＩ＃１とＳ－ＮＳＳＡＩ＃２をＲｅｑｕｅｓｅｄ　ＮＳＳＡＩ　ＩＥに含めてメッセージをＡＭＦ３０Ａに送信すると、ＵＥは、Ｓ－ＮＳＳＡＩ＃１（ｃａｕｓｅ値"Ｓ－ＮＳＳＡＩ　ｎｏｔ　ａｖａｉｌａｂｌｅ　ｉｎ　ｔｈｅ　ｃｕｒｒｅｎｔ　ｒｅｇｉｓｔｒａｔｉｏｎ　ａｒｅａ"）がＲｅｊｅｃｔｅｄ　ＮＳＳＡＩ　ＩＥに設定され、Ｓ－ＮＳＳＡＩ＃２がＡｌｌｏｗｅｄ　ＮＳＳＡＩ　ＩＥに設定された登録許可を受信する。同時に、ＵＥ２０は、ＴＡ＃３のみが設定されたＴＡＩリストＩＥを受信する。すなわち、ＵＥは、Ａｌｌｏｗｅｄ　ＮＳＳＡＩ　ＩＥに含まれるＳ－ＮＳＳＡＩが使用できるＴＡで構成されたＴＡＩリストを受信する。 For example, there are TA#1, TA#2, and TA#3, and TA#1 and TA#2 support S-NSSAI#1, and TA#3 does not support S-NSSAI#1. Assume a case where S-NSSAI #2 is supported. When the UE is located in TA #3 and sends a message to the AMF 30A including S-NSSAI #1 and S-NSSAI #2 in the Requested NSSAI IE, the UE sends S-NSSAI #1 (with cause value "S -NSSAI not available in the current registration area" is set to Rejected NSSAI IE, and S-NSSAI #2 is Allowed NSSA I Receive the registration permission set in the IE. At the same time, the UE 20 receives the TAI list IE in which only TA #3 is configured. That is, the UE receives a TAI list composed of TAs that can be used by the S-NSSAI included in the Allowed NSSAI IE.
　当該動作により、例えば、ＵＥ２０がＴＡ＃３からＴＡ＃２に移動した場合（ＴＡ＃３からＴＡ＃２に移動するとは、別のＲＡに移動（ＲＡ跨り）したことを意味する）、先に受信した"Ｓ－ＮＳＳＡＩ　ｎｏｔ　ａｖａｉｌａｂｌｅ　ｉｎ　ｔｈｅ　ｃｕｒｒｅｎｔ　ｒｅｇｉｓｔｒａｔｉｏｎ　ａｒｅａ"を解消する事ができ、ＵＥ２０はＳ－ＮＳＳＡＩ＃１を登録要求に含めることができる。さらに具体的には、ＵＥ２０は、元のＲＡから移動することで、Ｓ－ＮＳＳＡＩ＃１がＮＳＳＡＩストレージのＲｅｊｅｃｔｅｄ　ＮＳＳＡＩに格納されていたとしても、次の登録要求でＳ－ＮＳＳＡＩ＃１をＲｅｑｕｅｓｔｅｄ　ＮＳＳＡＩ　ＩＥに含めることができる。このとき、ＵＥは、ＮＳＳＡＩストレージのＲｅｊｅｃｔｅｄ　ＮＳＳＡＩからＳ－ＮＳＳＡＩ＃１を削除（ｄｅｌｅｔｅ／ｒｅｍｏｖｅ）してもよいし、削除しなくもよい。 Due to this operation, for example, if the UE 20 moves from TA #3 to TA #2 (moving from TA #3 to TA #2 means moving to another RA (straddling RA)), first The received "S-NSSAI not available in the current registration area" can be resolved, and the UE 20 can include S-NSSAI #1 in the registration request. More specifically, by moving from the original RA, the UE 20 stores S-NSSAI #1 in the Rejected NSSAI in the next registration request, even if S-NSSAI #1 is stored in the Rejected NSSAI of the NSSAI storage. Can be included in IE. At this time, the UE may or may not delete S-NSSAI #1 from Rejected NSSAI in the NSSAI storage.
　第１２の情報は、ＵＥ２０の現在位置では使用できないすなわちＡｌｌｏｗｅｄ　ＮＳＳＡＩではないＳ－ＮＳＳＡＩであってもよい。第１２の情報は、Ｒｅｊｅｃｔｅｄ　ＮＳＳＡＩに含まれてもよい。第１２の情報は、第１１の情報が含まれているメッセージと同じメッセージに含まれていてもよい。現在位置とは、ＴＡＩであってもよいし、地理的位置であってもよいし、その他位置を示す情報であってもよい。第１２の情報を受信したＵＥ２０は、現在位置では第１２の情報を利用しない。第１２の情報を受信したＵＥ２０は、第１２の情報が含まれるＩＥに応じたＮＳＳＩＡストレージに格納されてもよい。 The twelfth information may be an S-NSSAI that cannot be used at the current location of the UE 20, that is, it is not an Allowed NSSAI. The twelfth information may be included in Rejected NSSAI. The twelfth information may be included in the same message as the eleventh information. The current location may be TAI, a geographic location, or other information indicating the location. The UE 20 that has received the twelfth information does not use the twelfth information at the current location. The UE 20 that has received the twelfth information may store the twelfth information in the NSSIA storage corresponding to the IE in which it is included.
　図７は、本発明の実施の形態における登録要求の例（２）を説明するためのシーケンス図である。ステップＳ２０１において、ＵＥ２０は、第２の情報を含む登録要求をＡＭＦ３０Ａに送信する。第２の情報は、ＴＡ粒度のネットワークスライスサービスをＵＥがサポートすることを示す情報であってもよい。後述する第２１の情報を含むＩＥ及び第２２の情報を含むＩＥをＵＥ２０がサポートすることを示す情報であってもよい。ＵＥ２０のサポートとは、例えば、第２１の情報及び第２２の情報を受信したとき、第２１の情報及び第２２の情報が意味する挙動をＵＥ２０がサポートしているという意味であってよいし、第２１及び第２２の情報を受信した際に、第２１及び第２２の情報のための特別なＮＳＳＡＩストレージで当該情報を管理する又は管理できることを意味してもよい。第２の情報は、５ＧＭＭ　ｃａｐａｂｉｌｉｔｙ　ＩＥに設定されていてもよい。 FIG. 7 is a sequence diagram for explaining example (2) of a registration request in the embodiment of the present invention. In step S201, the UE 20 transmits a registration request including the second information to the AMF 30A. The second information may be information indicating that the UE supports network slicing services at TA granularity. The information may be information indicating that the UE 20 supports an IE including 21st information and an IE including 22nd information, which will be described later. Support of the UE 20 may mean, for example, that the UE 20 supports the behavior meant by the 21st information and the 22nd information when receiving the 21st information and the 22nd information, It may also mean that upon receiving the 21st and 22nd information, the information is managed or can be managed in a special NSSAI storage for the 21st and 22nd information. The second information may be set in the 5GMM capability IE.
　続くステップＳ２０２において、ＡＭＦ３０Ａは、ＵＤＭ、ＮＳＳＦ及びＮＦのいずれか又は複数と共に、制限付き許可されたＮＳＳＡＩ（Limited allowed NSSAI）を生成する。続いて、ステップＳ２０３において、ＡＭＦ３０Ａは、第２１の情報及び第２２の情報を含む登録許可をＵＥ２０に送信する。続くステップＳ２０４では、ＵＥ２０はＮＳＳＡＩストレージを更新する。続くステップＳ２０５では、ＵＥ２０はＳ－ＮＳＳＡＩ＃１をサポートするＴＡ又はサポートしないＴＡに移動する。続くステップＳ２０６では、報知情報（例えばＳＩＢ）及びＮＳＳＡＩストレージに基づいてＳ－ＮＳＳＡＩが使用できるか否かを決定する。 In the following step S202, the AMF 30A generates a limited allowed NSSAI with one or more of the UDM, NSSF, and NF. Subsequently, in step S203, the AMF 30A transmits registration permission including the 21st information and the 22nd information to the UE 20. In the following step S204, the UE 20 updates the NSSAI storage. In the following step S205, the UE 20 moves to a TA that supports S-NSSAI #1 or a TA that does not. In the following step S206, it is determined whether the S-NSSAI can be used based on the broadcast information (for example, SIB) and the NSSAI storage.
　第２１の情報は、ＵＥ２０の現在位置で使用できないか又は現在位置で使用できるＳ－ＮＳＳＡＩであって、第２２の情報が示す位置では使用できるＳ－ＮＳＳＡＩであってもよい。第２１の情報は、Ｌｉｍｉｔｅｄ　Ａｌｌｏｗｅｄ　ＮＳＳＡＩ　ＩＥに含まれてもよいし、Ｃｏｎｄｉｔｉｏｎａｌ　ＮＳＳＡＩ　ＩＥに含まれてもよい。また、当該Ｓ－ＮＳＳＡＩを含めるＩＥはこれに限らなくてもよい。位置とは、ＴＡＩであってもよいし、地理的位置でもよいし、その他位置を示す情報であってもよい。 The 21st information may be an S-NSSAI that cannot be used at the current location of the UE 20 or that can be used at the current location, but may be an S-NSSAI that can be used at the location indicated by the 22nd information. The 21st information may be included in the Limited Allowed NSSAI IE or the Conditional NSSAI IE. Furthermore, the IE that includes the S-NSSAI is not limited to this. The location may be TAI, a geographic location, or other information indicating the location.
　第２１の情報を受信したＵＥ２０は、第２１の情報が現在位置で使用できないＳ－ＮＳＳＡＩである場合第２１の情報を利用しない。第２１の情報を利用しないとは、いかなるＮＡＳ手順で利用しないという意味であってもよい。例えば、ＵＥの位置が現在位置である限り、登録手順で第２１の情報を利用しなくてもよい。また、ＰＤＵセッション確立手順においても第２１の情報を利用しなくてもよい。利用しないとは、各ＮＡＳメッセージに含めないという意味であってもよい。一方、第２１の情報を受信したＵＥ２０は、第２１の情報が現在位置で使用できるＳ－ＮＳＳＡＩである場合第２１の情報を利用してもよい。第２１の情報を受信したＵＥは、第２１の情報が含まれるＩＥに応じたＮＳＳＡＩストレージに格納されてよい。 The UE 20 that has received the 21st information does not use the 21st information if the 21st information is S-NSSAI that cannot be used at the current location. Not using the 21st information may mean not using it in any NAS procedure. For example, as long as the location of the UE is the current location, the 21st information may not be used in the registration procedure. Further, the 21st information does not need to be used in the PDU session establishment procedure. Not using it may mean not including it in each NAS message. On the other hand, the UE 20 that has received the 21st information may use the 21st information if the 21st information is S-NSSAI that can be used at the current location. The UE that has received the 21st information may store the 21st information in the NSSAI storage according to the IE that includes it.
　第２２の情報は、第２１の情報すなわちＳ－ＮＳＳＡＩが使用できる位置を示す情報であってもよい。第２２の情報は、第２１の情報と関連付けられてＵＥ２０に送信されてもよい。位置とは、ＴＡＩであってもよいし、地理的位置でもよいし、その他位置を示す情報であってもよい。 The 22nd information may be the 21st information, that is, information indicating a location where the S-NSSAI can be used. The 22nd information may be transmitted to the UE 20 in association with the 21st information. The location may be TAI, a geographic location, or other information indicating the location.
　第２２の情報を受信したＵＥ２０は、第２１の情報によるＵＥ２０の挙動に加えて、第２２の情報が示す位置に移動したことを検知した場合、第２１の情報を利用してもよい。ＵＥ２０は、報知情報に含まれる情報に基づいて、第２２の情報が示す位置に移動したことを検知してもよい。 The UE 20 that has received the 22nd information may utilize the 21st information if it detects that the UE 20 has moved to the position indicated by the 22nd information in addition to the behavior of the UE 20 based on the 21st information. The UE 20 may detect that it has moved to the position indicated by the 22nd information based on the information included in the broadcast information.
　例えば、一つのＲＡにＴＡ＃１とＴＡ＃２とＴＡ＃３が含まれており、ＴＡ＃１とＴＡ＃２はＳ－ＮＳＳＡＩ＃１をサポートしており、ＴＡ＃３はＳ－ＮＳＳＡＩ＃１をサポートしていないがＳ－ＮＳＳＡＩ＃２をサポートしているようなケースを想定する。ＵＥ２０がＴＡ＃３に在圏しているとき、Ｓ－ＮＳＳＡＩ＃１とＳ－ＮＳＳＡＩ＃２をＲｅｑｕｅｓｅｄ　ＮＳＳＡＩ　ＩＥに含めてメッセージをＡＭＦ３０Ａに送信すると、ＵＥ２０は、Ｓ－ＮＳＳＡＩ＃１が第２１の情報を含めるＩＥに設定され、Ｓ－ＮＳＳＡＩ＃２がＡｌｌｏｗｅｄ　ＮＳＳＡＩ　ＩＥに設定された登録許可を受信する。同時に、ＵＥは、第２１の情報に関連付けられたＴＡ＃１とＴＡ＃２が設定された第２２の情報を受信する。ＵＥ２０は、ＴＡ＃１またはＴＡ＃２に移動した場合、Ｓ－ＮＳＳＡＩ＃１を利用できる。利用できるとは、登録手順において、登録要求にＳ－ＮＳＳＡＩ＃１を含めることができる（許可されている）という意味であってよいし、ＰＤＵセッション確立要求でＳ－ＮＳＳＡＩ＃１を利用できる（許可されている）という意味であってよい。言い換えると、ＵＥ２０は、ＴＡ＃１またはＴＡ＃２への移動に際してＴＡ＃３で受信した第２１の情報をあたかもＡｌｌｏｗｅｄ　ＮＳＳＡＩに含まれるＳ－ＮＳＳＡＩとして取り扱ってよい。 For example, one RA includes TA#1, TA#2, and TA#3, TA#1 and TA#2 support S-NSSAI#1, and TA#3 supports S-NSSAI# Let us assume a case where S-NSSAI #1 is not supported but S-NSSAI #2 is supported. When the UE 20 is located in TA #3 and sends a message to the AMF 30A including S-NSSAI #1 and S-NSSAI #2 in the Requested NSSAI IE, the UE 20 recognizes that S-NSSAI #1 is the 21st is set to the IE that contains the information, and S-NSSAI#2 receives the registration permission set to the Allowed NSSAI IE. At the same time, the UE receives 22nd information in which TA#1 and TA#2 associated with the 21st information are configured. When the UE 20 moves to TA #1 or TA #2, it can use S-NSSAI #1. "Available" may mean that S-NSSAI #1 can be included in the registration request (permitted) in the registration procedure, or that S-NSSAI #1 can be used in the PDU session establishment request ( may mean that it is permitted). In other words, the UE 20 may treat the 21st information received at TA #3 when moving to TA #1 or TA #2 as if it were S-NSSAI included in Allowed NSSAI.
　具体的には、ＵＥ２０は、第２１の情報が含まれるＩＥに応じたＮＳＳＡＩストレージに格納されている第２１の情報（Ｓ－ＮＳＳＡＩ＃１）を第２１の情報が含まれるＩＥに応じたＮＳＳＡＩストレージから削除（ｄｅｌｅｔｅ／ｒｅｍｏｖｅ）してもよい。さらに、ＵＥ２０は、第２１の情報をＮＳＳＡＩストレージのＡｌｌｏｗｅｄ　ＮＳＳＡＩに格納してもよい。これによって、ＵＥ２０はＮＳＳＡＩストレージのＡｌｌｏｗｅｄ　ＮＳＳＡＩに含まれるＳ－ＮＳＳＡＩ＃１を以降のＮＡＳ手順（例えば登録手順又はＰＤＵセッション確立手順）で利用できる。具体的には、登録手順でＳ－ＮＳＳＡＩ＃１をＲｅｑｕｅｓｔｅｄ　ＮＳＳＡＩ　ＩＥに含めることが可能となり、ＰＤＵセッション確立のためのＵＬ　ＮＡＳ　ＴＲＡＮＳＰＯＲＴメッセージのＳ－ＮＳＳＡＩ　ＩＥにＳ－ＮＳＳＡＩ＃１を設定することができるという意味であってよい。 Specifically, the UE 20 transfers the 21st information (S-NSSAI#1) stored in the NSSAI storage corresponding to the IE containing the 21st information to the NSSAI corresponding to the IE containing the 21st information. It may also be deleted from the storage. Furthermore, the UE 20 may store the 21st information in Allowed NSSAI of the NSSAI storage. Thereby, the UE 20 can use S-NSSAI #1 included in Allowed NSSAI in the NSSAI storage in subsequent NAS procedures (for example, registration procedure or PDU session establishment procedure). Specifically, S-NSSAI#1 can be included in the Requested NSSAI IE in the registration procedure, and S-NSSAI#1 can be set in the S-NSSAI IE of the UL NAS TRANSPORT message for establishing a PDU session. It may mean that it is possible.
　図８は、本発明の実施の形態における登録要求の例（３）を説明するためのシーケンス図である。ステップＳ３０１において、ＵＥ２０は、第３の情報を含む登録要求をＡＭＦ３０Ａに送信する。第３の情報は、ＴＡ粒度のネットワークスライスサービスをＵＥがサポートすることを示す情報であってもよい。後述する第３２の情報及び第３３の情報を含むＩＥ及び第２２の情報を含むＩＥをＵＥ２０がサポートすることを示す情報であってもよい。ＵＥ２０のサポートとは、例えば、第３１及び第３２及び／又は第３３の情報を受信した際に、第３１及び第３２及び／又は第３３の情報が意味する挙動をＵＥがサポートしているという意味であってよいし、第３１及び第３２及び／又は第３３の情報を受信したとき、第３１及び第３２及び／又は第３３の情報のための特別なＮＳＳＡＩストレージで当該情報を管理する／できることを意味してもよい。第３の情報は、５ＧＭＭ　ｃａｐａｂｉｌｉｔｙ　ＩＥに設定されていてもよい。 FIG. 8 is a sequence diagram for explaining example (3) of a registration request in the embodiment of the present invention. In step S301, the UE 20 transmits a registration request including the third information to the AMF 30A. The third information may be information indicating that the UE supports TA granularity network slicing services. The information may be information indicating that the UE 20 supports an IE including 32nd information and 33rd information and an IE including 22nd information, which will be described later. Support of the UE 20 means, for example, that when receiving the 31st, 32nd, and/or 33rd information, the UE supports the behavior meant by the 31st, 32nd, and/or 33rd information. and when receiving the 31st and 32nd and/or 33rd information, manage said information in a special NSSAI storage for the 31st and 32nd and/or 33rd information; It can also mean something that can be done. The third information may be set in the 5GMM capability IE.
　続くステップＳ３０２において、ＡＭＦ３０Ａは、第３１の情報、第３２の情報及び第３３の情報を含む登録許可をＵＥ２０に送信する。続くステップＳ３０３では、ＵＥ２０はＮＳＳＡＩストレージを更新する。続くステップＳ３０４では、ＵＥ２０はＳ－ＮＳＳＡＩ＃１をサポートするＴＡ又はサポートしないＴＡに移動する。続くステップＳ３０５では、報知情報（例えばＳＩＢ）及びＮＳＳＡＩストレージに基づいてＳ－ＮＳＳＡＩが使用できるか否かを決定する。 In the following step S302, the AMF 30A transmits registration permission including the 31st information, the 32nd information, and the 33rd information to the UE 20. In the following step S303, the UE 20 updates the NSSAI storage. In the following step S304, the UE 20 moves to a TA that supports S-NSSAI #1 or a TA that does not. In the following step S305, it is determined whether the S-NSSAI can be used based on the broadcast information (for example, SIB) and the NSSAI storage.
　第３１の情報は、ＵＥ２０の現在位置では使用できないが第３２の情報に基づき他の位置では利用できる可能性のあるＳ－ＮＳＳＡＩであってもよい。また、第３１の情報は、ＵＥ２０の現在位置では使用できないが第３３の情報が示す位置では使用できるＳ－ＮＳＳＡＩであってもよい。第３１の情報は、Ｒｅｊｅｃｔｅｄ　ＮＳＳＡＩ　ＩＥに含まれていてもよい。また、当該Ｓ－ＮＳＳＡＩを含めるＩＥはこれに限定されなくてもよい。 The 31st information may be S-NSSAI that cannot be used at the current location of the UE 20 but may be available at other locations based on the 32nd information. Further, the 31st information may be S-NSSAI that cannot be used at the current location of the UE 20 but can be used at the location indicated by the 33rd information. The 31st information may be included in the Rejected NSSAI IE. Furthermore, the IE that includes the S-NSSAI is not limited to this.
　第３１の情報を受信したＵＥ２０は、現在位置では第３１の情報を利用しない。第３１の情報を利用しないとは、いかなるＮＡＳ手順で利用しないという意味であってよい。例えば、ＵＥ２０の位置が現在位置である限り、登録手順で第３１の情報を利用しない。また、ＰＤＵセッション確立手順でも第３１の情報を利用しない。利用しないとは、各ＮＡＳメッセージに含めないという意味であってよい。 The UE 20 that has received the 31st information does not use the 31st information at its current location. Not using the 31st information may mean not using it in any NAS procedure. For example, as long as the location of the UE 20 is the current location, the 31st information is not used in the registration procedure. Further, the 31st information is not used in the PDU session establishment procedure. Not using it may mean not including it in each NAS message.
　第３１の情報を受信したＵＥ２０は、第３１の情報を含めるＩＥ及び第３１の情報に関連付けて当該メッセージに含まれるｃａｕｓｅ値に応じたＮＳＳＡＩストレージに格納されてもよい。当該ｃａｕｓｅ値とは、"Ｓ－ＮＳＳＡＩ　ｎｏｔ　ａｖａｉｌａｂｌｅ　ｉｎ　ｔｈｅ　ｃｕｒｒｅｎｔ　ｒｅｇｉｓｔｒａｔｉｏｎ　ａｒｅａ"であってよい。 The UE 20 that has received the 31st information may store it in the NSSAI storage according to the IE that includes the 31st information and the cause value included in the message in association with the 31st information. The cause value may be "S-NSSAI not available in the current registration area".
　第３２の情報は、Ｒｅｊｅｃｔｅｄ　ＮＳＳＡＩ取り扱いの例外（Ｅｘｃｅｐｔｉｏｎ）を示す通知であってもよい。Ｒｅｊｅｃｔｅｄ　ＮＳＳＡＩ取り扱いとは、ここで関連付けられているｃａｕｓｅ値は、"Ｓ－ＮＳＳＡＩ　ｎｏｔ　ａｖａｉｌａｂｌｅ　ｉｎ　ｔｈｅ　ｃｕｒｒｅｎｔ　ｒｅｇｉｓｔｒａｔｉｏｎ　ａｒｅａ"であるため、正常な取り扱いとしては、"ｃｕｒｒｅｎｔ　ｒｅｇｉｓｔｒａｔｉｏｎ　ａｒｅａ"外に出ない限りＲｅｊｅｃｔｅｄ　ＮＳＳＡＩに含まれているＳ－ＮＳＳＡＩをいかなるＮＡＳ手順でも利用できない。第３２の情報は、この正常取り扱いの例外として、"ｃｕｒｒｅｎｔ　ｒｅｇｉｓｔｒａｔｉｏｎ　ａｒｅａ"外に出ずとも現在位置から移動することでＲｅｊｅｃｔｅｄ　ＮＳＳＡＩに含まれているＳ－ＮＳＳＡＩをＮＡＳ手順で利用することができる。位置とは、ＴＡＩであってもよいし、地理的位置でもよいし、その他位置を示す情報であってもよい。 The 32nd information may be a notification indicating an exception in handling the Rejected NSSAI. Rejected NSSAI handling means that the cause value associated here is "S-NSSAI not available in the current registration area", so normal handling is "curre nt registration area" Rejected unless you go outside The S-NSSAI contained in the NAS cannot be used by any NAS procedure. As an exception to this normal handling, the 32nd information can use the S-NSSAI included in the Rejected NSSAI in the NAS procedure by moving from the current position without going outside the "current registration area". The location may be TAI, a geographic location, or other information indicating the location.
　第３２の情報を受信したＵＥ２０は、現在位置では第３１の情報を利用しない。第３１の情報を利用しないとは、いかなるＮＡＳ手順で利用しないという意味であってよい。例えば、ＵＥ２０の位置が現在位置である限り、登録手順で第３１の情報を利用しない。また、ＰＤＵセッション確立手順でも第３１の情報を利用しない。利用しないとは、各ＮＡＳメッセージに含めないという意味であってよい。しかしながら、第３２の情報を受信したＵＥ２０は、現在位置からに移動した場合、第３１の情報を利用してもよい。 The UE 20 that has received the 32nd information does not use the 31st information at its current location. Not using the 31st information may mean not using it in any NAS procedure. For example, as long as the location of the UE 20 is the current location, the 31st information is not used in the registration procedure. Further, the 31st information is not used in the PDU session establishment procedure. Not using it may mean not including it in each NAS message. However, the UE 20 that has received the 32nd information may use the 31st information when moving from the current location.
　例えば、一つのＲＡにＴＡ＃１とＴＡ＃２とＴＡ＃３が含まれており、ＴＡ＃１とＴＡ＃２はＳ－ＮＳＳＡＩ＃１をサポートしており、ＴＡ＃３はＳ－ＮＳＳＡＩ＃１をサポートしていないがＳ－ＮＳＳＡＩ＃２をサポートしているようなケースを想定する。ＵＥ２０がＴＡ＃３に在圏している時にＳ－ＮＳＳＡＩ＃１とＳ－ＮＳＳＡＩ＃２をＲｅｑｕｅｓｅｄ　ＮＳＳＡＩ　ＩＥに含めてメッセージをＡＭＦ３０に送信すると、ＵＥ２０は、Ｓ－ＮＳＳＡＩ＃１が第３１の情報を含めるＩＥに設定され、Ｓ－ＮＳＳＡＩ＃２がＡｌｌｏｗｅｄ　ＮＳＳＡＩ　ＩＥに設定された登録許可を受信する。同時に、ＵＥ２０は、第３１の情報に関連付けられた第３２の情報を受信する。ＵＥ２０は、ＴＡ＃３の外に移動した場合、Ｓ－ＮＳＳＡＩ＃１を利用できる。利用できるとは、登録手順において、登録要求にＳ－ＮＳＳＡＩ＃１を載せることができる（許可されている）という意味であってよいし、ＰＤＵセッション確立手順でＳ－ＮＳＳＡＩ＃１を利用できる（許可されている）という意味であってもよい。 For example, one RA includes TA#1, TA#2, and TA#3, TA#1 and TA#2 support S-NSSAI#1, and TA#3 supports S-NSSAI# Let us assume a case where S-NSSAI #1 is not supported but S-NSSAI #2 is supported. When the UE 20 is in the area of TA #3 and sends a message to the AMF 30 including S-NSSAI #1 and S-NSSAI #2 in the Requested NSSAI IE, the UE 20 recognizes that S-NSSAI #1 is the 31st information. , and S-NSSAI #2 receives the registration permission set to the Allowed NSSAI IE. At the same time, the UE 20 receives 32nd information associated with the 31st information. When the UE 20 moves outside TA #3, it can use S-NSSAI #1. "Available" may mean that S-NSSAI #1 can be included in a registration request in the registration procedure (is allowed), or that S-NSSAI #1 can be used in the PDU session establishment procedure ( It may also mean "permitted".
　言い換えると、ＵＥ２０がＴＡ＃３で受信した第３１の情報に関連付けられるｃａｕｓｅ値は、"Ｓ－ＮＳＳＡＩ　ｎｏｔ　ａｖａｉｌａｂｌｅ　ｉｎ　ｔｈｅ　ｃｕｒｒｅｎｔ　ｒｅｇｉｓｔｒａｔｉｏｎ　ａｒｅａ"すなわち、粒度がＲＡであるが、ｃａｕｓｅ値の粒度をＲＡではなく、現在位置（例えばＴＡ）とする例外的な取り扱いをすることを示す。具体的には、ＵＥ２０は、ＮＳＳＡＩストレージのＲｅｊｅｃｔｅｄ　ＮＳＳＡＩに格納されている第３１の情報（Ｓ－ＮＳＳＡＩ＃１）をＮＳＳＡＩストレージのＲｅｊｅｃｔｅｄ　ＮＳＳＡＩから削除（ｄｅｌｅｔｅ／ｒｅｍｏｖｅ）してもよい。これによって、ＵＥ２０は以降のＮＡＳ手順でＳ－ＮＳＳＡＩ＃１を利用できる。具体的には、登録要求でＳ－ＮＳＳＡＩ＃１をＲｅｑｕｅｓｔｅｄ　ＮＳＳＡＩ　ＩＥに含めることができるし、ＰＤＵセッション確立手順のためのＵＬ　ＮＡＳ　ＴＲＡＮＳＰＯＲＴメッセージのＳ－ＮＳＳＡＩ　ＩＥにＳ－ＮＳＳＡＩ＃１を設定することができるという意味であってもよい。 In other words, the cause value associated with the 31st information that the UE 20 received at TA #3 is "S-NSSAI not available in the current registration area", that is, the granularity is RA, but the granularity of the cause value is In R.A. Indicates that the current position (for example, TA) is treated as an exception. Specifically, the UE 20 may delete (delete/remove) the 31st information (S-NSSAI#1) stored in the Rejected NSSAI of the NSSAI storage from the Rejected NSSAI of the NSSAI storage. This allows the UE 20 to use S-NSSAI #1 in subsequent NAS procedures. Specifically, S-NSSAI #1 can be included in the Requested NSSAI IE in the registration request, and S-NSSAI #1 can be set in the S-NSSAI IE of the UL NAS TRANSPORT message for the PDU session establishment procedure. It may also mean that it is possible.
　第３３の情報は、第３１の情報（Ｓ－ＮＳＳＡＩ）が使える位置を示す情報であってもよい。第３１の情報と関連付けられてＵＥ２０に送信される。位置とは、ＴＡＩであってもよいし、地理的位置でもよいし、その他位置を示す情報であってもよい。 The 33rd information may be information indicating a location where the 31st information (S-NSSAI) can be used. It is transmitted to the UE 20 in association with the 31st information. The location may be TAI, a geographic location, or other information indicating the location.
　第３３の情報を受信したＵＥ２０は、第３１の情報で記載したＵＥの挙動に加えて、第３３の情報が示す位置に移動したことを検知した場合、第３１の情報を利用してもよい。ＵＥ２０は、報知情報に含まれる情報に基づいて、第３３の情報が示す位置に移動したことを検知してもよい。 In addition to the behavior of the UE described in the 31st information, the UE 20 that has received the 33rd information may use the 31st information if it detects that the UE has moved to the position indicated by the 33rd information. . The UE 20 may detect that the UE 20 has moved to the position indicated by the 33rd information based on the information included in the broadcast information.
　例えば、一つのＲＡにＴＡ＃１とＴＡ＃２とＴＡ＃３が含まれており、ＴＡ＃１とＴＡ＃２はＳ－ＮＳＳＡＩ＃１をサポートしており、ＴＡ＃３はＳ－ＮＳＳＡＩ＃１をサポートしていないがＳ－ＮＳＳＡＩ＃２をサポートしているようなケースを想定する。ＵＥがＴＡ＃３に在圏しているときにＳ－ＮＳＳＡＩ＃１とＳ－ＮＳＳＡＩ＃２をＲｅｑｕｅｓｅｄ　ＮＳＳＡＩ　ＩＥに含めてメッセージをＡＭＦ３０に送信すると、ＵＥ２０は、Ｓ－ＮＳＳＡＩ＃１がＲｅｊｅｃｔｅｄ　ＮＳＳＡＩ　ＩＥに設定され、Ｓ－ＮＳＳＡＩ＃２がＡｌｌｏｗｅｄ　ＮＳＳＡＩ　ＩＥに設定された登録許可を受信する。同時に、ＵＥ２０は、第３１の情報に関連付けられたＴＡ＃１とＴＡ＃２が設定された第３３の情報を受信する。ＵＥ２０は、ＴＡ＃１またはＴＡ＃２に移動した場合、Ｓ－ＮＳＳＡＩ＃１を利用できる。利用できるとは、登録手順において、登録要求にＳ－ＮＳＳＡＩ＃１を含めることができる（許可される）という意味であってよいし、ＰＤＵセッション確立手順でＳ－ＮＳＳＡＩ＃１を利用できる（許可される）という意味であってよい。 For example, one RA includes TA#1, TA#2, and TA#3, TA#1 and TA#2 support S-NSSAI#1, and TA#3 supports S-NSSAI# Let us assume a case where S-NSSAI #1 is not supported but S-NSSAI #2 is supported. When the UE is located in TA #3 and sends a message to the AMF 30 with S-NSSAI #1 and S-NSSAI #2 included in the Requested NSSAI IE, the UE 20 sends the S-NSSAI #1 to the Rejected NSSAI IE. and S-NSSAI#2 receives the registration permission set to Allowed NSSAI IE. At the same time, the UE 20 receives 33rd information in which TA#1 and TA#2 associated with the 31st information are set. When the UE 20 moves to TA #1 or TA #2, it can use S-NSSAI #1. "Available" may mean that S-NSSAI #1 can be included in the registration request (permitted) in the registration procedure, or that S-NSSAI #1 can be used (permitted) in the PDU session establishment procedure. It may mean that
　言い換えると、ＵＥ２０は、ＴＡ＃１またはＴＡ＃２への移動に際してＴＡ＃３で受信した第３１の情報をあたかもＡｌｌｏｗｅｄ　ＮＳＳＡＩに含まれるＳ－ＮＳＳＡＩとして取り扱ってよい。具体的には、ＵＥ２０は、ＮＳＳＡＩストレージのＲｅｊｅｃｔｅｄ　ＮＳＳＡＩに格納されている第３１の情報（Ｓ－ＮＳＳＡＩ＃１）をＮＳＳＡＩストレージのＲｅｊｅｃｔｅｄ　ＮＳＳＡＩから削除（ｄｅｌｅｔｅ／ｒｅｍｏｖｅ）してもよい。さらに、ＵＥは、第３１の情報をＮＳＳＡＩストレージのＡｌｌｏｗｅｄ　ＮＳＳＡＩに格納してもよい。これによって、ＵＥはＮＳＳＡＩストレージのＡｌｌｏｗｅｄ　ＮＳＳＡＩに含まれるＳ－ＮＳＳＡＩ＃１を以降のＮＡＳ手順（例えば登録手順又はＰＤＵセッション確立手順）で利用できる。具体的には、登録要求でＳ－ＮＳＳＡＩ＃１をＲｅｑｕｅｓｔｅｄ　ＮＳＳＡＩ　ＩＥに含めることができるし、ＰＤＵセッション確立のためのＵＬ　ＮＡＳ　ＴＲＡＮＳＰＯＲＴメッセージのＳ－ＮＳＳＡＩ　ＩＥにＳ－ＮＳＳＡＩ＃１を設定することができるという意味であってよい。 In other words, the UE 20 may treat the 31st information received at TA #3 when moving to TA #1 or TA #2 as if it were S-NSSAI included in Allowed NSSAI. Specifically, the UE 20 may delete (delete/remove) the 31st information (S-NSSAI#1) stored in the Rejected NSSAI of the NSSAI storage from the Rejected NSSAI of the NSSAI storage. Furthermore, the UE may store the 31st information in the Allowed NSSAI of the NSSAI storage. Thereby, the UE can use S-NSSAI #1 included in Allowed NSSAI in the NSSAI storage in subsequent NAS procedures (for example, registration procedure or PDU session establishment procedure). Specifically, S-NSSAI #1 can be included in the Requested NSSAI IE in the registration request, and S-NSSAI #1 can be set in the S-NSSAI IE of the UL NAS TRANSPORT message for establishing a PDU session. It may mean that it is possible.
　ＵＥ２０は、第３２の情報を受信した場合に、オプショナルとして第３３の情報を参照しいずれの位置でＳ－ＮＳＳＡＩ＃１が利用可能であるか認識してもよい。 When the UE 20 receives the 32nd information, it may optionally refer to the 33rd information and recognize at which position S-NSSAI #1 is available.
　図９は、本発明の実施の形態における登録要求の例（４）を説明するためのシーケンス図である。ステップＳ４０１において、ＵＥ２０は、第４の情報を含む登録要求をＡＭＦ３０Ａに送信する。第４の情報は、ＴＡ粒度のネットワークスライスサービスをＵＥがサポートすることを示す情報であってもよい。後述する第４２の情報を含むＩＥをＵＥ２０がサポートすることを示す情報であってもよい。ＵＥ２０のサポートとは、例えば、第４１の情報及び第４２の情報を受信した際に、第４１の情報及び第４２の情報が意味する挙動をＵＥがサポートしているという意味であってもよいし、第４１の情報及び第４２の情報を受信したとき、第４１の情報及び第４２の情報のための特別なＮＳＳＡＩストレージで当該情報を管理する／できることを意味してもよい。第４の情報は、５ＧＭＭ　ｃａｐａｂｉｌｉｔｙ　ＩＥに設定されていてもよい。 FIG. 9 is a sequence diagram for explaining example (4) of a registration request in the embodiment of the present invention. In step S401, the UE 20 transmits a registration request including the fourth information to the AMF 30A. The fourth information may be information indicating that the UE supports TA granularity network slicing services. The information may be information indicating that the UE 20 supports an IE including 42nd information to be described later. Support of the UE 20 may mean, for example, that the UE supports the behavior meant by the 41st information and the 42nd information when receiving the 41st information and the 42nd information. However, when the 41st information and the 42nd information are received, it may mean that the information is/can be managed in a special NSSAI storage for the 41st information and the 42nd information. The fourth information may be set in the 5GMM capability IE.
　続くステップＳ４０２において、ＡＭＦ３０Ａは、第４１の情報及び第４２の情報を含む登録許可をＵＥ２０に送信する。続くステップＳ４０３では、ＵＥ２０はＮＳＳＡＩストレージを更新する。続くステップＳ４０４では、ＵＥ２０はＳ－ＮＳＳＡＩ＃１をサポートするＴＡ又はサポートしないＴＡに移動する。続くステップＳ４０５では、報知情報（例えばＳＩＢ）及びＮＳＳＡＩストレージに基づいてＳ－ＮＳＳＡＩが使用できるか否かを決定する。 In the following step S402, the AMF 30A transmits registration permission including the 41st information and the 42nd information to the UE 20. In the following step S403, the UE 20 updates the NSSAI storage. In the following step S404, the UE 20 moves to a TA that supports S-NSSAI #1 or a TA that does not. In the following step S405, it is determined whether the S-NSSAI can be used based on the broadcast information (for example, SIB) and the NSSAI storage.
　第４１の情報は、ＵＥ２０の現在位置では使用できないが第４２の情報が示す位置では使えるＳ－ＮＳＳＡＩであってもよい。第４１の情報とは、Ｒｅｊｅｃｔｅｄ　ＮＳＳＡＩ　ＩＥに含まれていてもよい。また、当該Ｓ－ＮＳＳＡＩを含めるＩＥはこれに限定されなくてもよい。位置とは、ＴＡＩであってもよいし、地理的位置でもよいし、その他位置を示す情報であってもよい。 The 41st information may be S-NSSAI that cannot be used at the current location of the UE 20 but can be used at the location indicated by the 42nd information. The 41st information may be included in the Rejected NSSAI IE. Furthermore, the IE that includes the S-NSSAI is not limited to this. The location may be TAI, a geographic location, or other information indicating the location.
　第４１の情報を受信したＵＥ２０は、現在位置では第４１の情報を利用しない。第４１の情報を利用しないとは、いかなるＮＡＳ手順で利用しないという意味であってよい。例えば、ＵＥ２０の位置が現在位置である限り、登録手順で第４１の情報を利用しない。また、ＰＤＵセッション確立手順でも第４１の情報を利用しない。利用しないとは、各ＮＡＳメッセージに含めないという意味であってよい。 The UE 20 that has received the 41st information does not use the 41st information at its current location. Not using the 41st information may mean not using it in any NAS procedure. For example, as long as the location of the UE 20 is the current location, the 41st information is not used in the registration procedure. Further, the 41st information is not used in the PDU session establishment procedure. Not using it may mean not including it in each NAS message.
　第４１の情報を受信したＵＥ２０は、第４１の情報を含めるＩＥ及び第４１の情報に関連付けて当該メッセージに含まれるｃａｕｓｅ値に応じたＮＳＳＡＩストレージに格納されてよい。ｃａｕｓｅ値とは、"Ｓ－ＮＳＳＡＩ　ｎｏｔ　ａｖａｉｌａｂｌｅ　ｉｎ　ｔｈｅ　ｃｕｒｒｅｎｔ　ｒｅｇｉｓｔｒａｔｉｏｎ　ａｒｅａ"であってよい。 The UE 20 that has received the 41st information may store it in the NSSAI storage according to the IE that includes the 41st information and the cause value included in the message in association with the 41st information. The cause value may be "S-NSSAI not available in the current registration area".
　第４２の情報は、第４１の情報（Ｓ－ＮＳＳＡＩ）が使える位置を示す情報であってもよい。第４２の情報は、第４１の情報と関連付けられてＵＥ２０に送信されてもよい。位置とは、ＴＡＩであってもよいし、地理的位置でもよいし、その他位置を示す情報であってもよい。 The 42nd information may be information indicating a location where the 41st information (S-NSSAI) can be used. The 42nd information may be transmitted to the UE 20 in association with the 41st information. The location may be TAI, a geographic location, or other information indicating the location.
　第４２の情報を受信したＵＥ２０は、第４１の情報で記載したＵＥ２０の挙動に加えて、第４２の情報が示す位置に移動したことを検知した場合、第４１の情報を利用してもよい。ＵＥ２０は、報知情報に含まれる情報に基づいて、第４２の情報が示す位置に移動したことを検知してもよい。 In addition to the behavior of the UE 20 described in the 41st information, the UE 20 that has received the 42nd information may use the 41st information if it detects that the UE 20 has moved to the position indicated by the 42nd information. . The UE 20 may detect that the UE 20 has moved to the position indicated by the 42nd information based on the information included in the broadcast information.
　例えば、一つのＲＡにＴＡ＃１とＴＡ＃２とＴＡ＃３が含まれており、ＴＡ＃１とＴＡ＃２はＳ－ＮＳＳＡＩ＃１をサポートしており、ＴＡ＃３はＳ－ＮＳＳＡＩ＃１をサポートしていないがＳ－ＮＳＳＡＩ＃２をサポートしているようなケースを想定する。ＵＥ２０がＴＡ＃３に在圏しているときにＳ－ＮＳＳＡＩ＃１とＳ－ＮＳＳＡＩ＃２をＲｅｑｕｅｓｅｄ　ＮＳＳＡＩ　ＩＥに含めてメッセージをＡＭＦ３０Ａに送信すると、ＵＥ２０は、Ｓ－ＮＳＳＡＩ＃１がＲｅｊｅｃｔｅｄ　ＮＳＳＡＩ　ＩＥに設定され、Ｓ－ＮＳＳＡＩ＃２がＡｌｌｏｗｅｄ　ＮＳＳＡＩ　ＩＥに設定された登録許可を受信する。同時に、ＵＥ２０は、第４１の情報に関連付けられたＴＡ＃１とＴＡ＃２が設定された第４２の情報を受信する。ＵＥ２０は、ＴＡ＃１またはＴＡ＃２に移動した場合、Ｓ－ＮＳＳＡＩ＃１を利用できる。利用できるとは、登録手順において、登録要求にＳ－ＮＳＳＡＩ＃１を含めることができる（許可される）という意味であってよいし、ＰＤＵセッション確立要求でＳ－ＮＳＳＡＩ＃１を利用できる（許可される）という意味であってよい。 For example, one RA includes TA#1, TA#2, and TA#3, TA#1 and TA#2 support S-NSSAI#1, and TA#3 supports S-NSSAI# Let us assume a case where S-NSSAI #1 is not supported but S-NSSAI #2 is supported. When the UE 20 is in the area of TA #3 and sends a message to the AMF 30A with S-NSSAI #1 and S-NSSAI #2 included in the Required NSSAI IE, the UE 20 will receive the S-NSSAI #1 as the Rejected NSSAI IE. and S-NSSAI#2 receives the registration permission set to Allowed NSSAI IE. At the same time, the UE 20 receives the 42nd information in which TA#1 and TA#2 associated with the 41st information are set. When the UE 20 moves to TA #1 or TA #2, it can use S-NSSAI #1. "Available" may mean that S-NSSAI#1 can be included in a registration request (permitted) in the registration procedure, or S-NSSAI#1 can be used in a PDU session establishment request (permitted). It may mean that
　言い換えると、ＵＥ２０は、ＴＡ＃１またはＴＡ＃２への移動に際してＴＡ＃３で受信した第４１の情報をあたかもＡｌｌｏｗｅｄ　ＮＳＳＡＩに含まれるＳ－ＮＳＳＡＩとして取り扱ってよい。具体的には、ＵＥは、ＮＳＳＡＩストレージのＲｅｊｅｃｔｅｄ　ＮＳＳＡＩに格納されている第４１の情報（Ｓ－ＮＳＳＡＩ＃１）をＮＳＳＡＩストレージのＲｅｊｅｃｔｅｄ　ＮＳＳＡＩから削除（ｄｅｌｅｔｅ／ｒｅｍｏｖｅ）してもよい。さらに、ＵＥは、第４１の情報をＮＳＳＡＩストレージのＡｌｌｏｗｅｄ　ＮＳＳＡＩに格納してもよい。これによって、ＵＥはＮＳＳＡＩストレージのＡｌｌｏｗｅｄ　ＮＳＳＡＩに含まれるＳ－ＮＳＳＡＩ＃１を以降のＮＡＳ手順（例えば登録手順又はＰＤＵセッション確立手順）で利用できる。具体的には、登録要求でＳ－ＮＳＳＡＩ＃１をＲｅｑｕｅｓｔｅｄ　ＮＳＳＡＩ　ＩＥに含めることができるし、ＰＤＵセッション確立のためのＵＬ　ＮＡＳ　ＴＲＡＮＳＰＯＲＴメッセージのＳ－ＮＳＳＡＩ　ＩＥにＳ－ＮＳＳＡＩ＃１を設定することができるという意味であってよい。 In other words, the UE 20 may treat the 41st information received at TA #3 when moving to TA #1 or TA #2 as if it were S-NSSAI included in Allowed NSSAI. Specifically, the UE may delete/remove the 41st information (S-NSSAI#1) stored in the Rejected NSSAI of the NSSAI storage from the Rejected NSSAI of the NSSAI storage. Furthermore, the UE may store the 41st information in Allowed NSSAI of the NSSAI storage. Thereby, the UE can use S-NSSAI #1 included in Allowed NSSAI in the NSSAI storage in subsequent NAS procedures (for example, registration procedure or PDU session establishment procedure). Specifically, S-NSSAI #1 can be included in the Requested NSSAI IE in the registration request, and S-NSSAI #1 can be set in the S-NSSAI IE of the UL NAS TRANSPORT message for establishing a PDU session. It may mean that it is possible.
　図１０は、本発明の実施の形態における登録要求の例（５）を説明するためのシーケンス図である。ステップＳ５０１において、ＵＥ２０は、第５の情報を含む登録要求をＡＭＦ３０Ａに送信する。第５の情報は、ＴＡ粒度のネットワークスライスサービスをＵＥがサポートすることを示す情報であってもよい。ＵＥ２０のサポートとは、ＴＡ粒度のネットワークスライスサービスをサポートするか否かを意味してもよいし、例えば、第５２の情報をサポートするか否かを意味してもよい。第５の情報は、５ＧＭＭ　ｃａｐａｂｉｌｉｔｙ　ＩＥに設定されていてもよい。 FIG. 10 is a sequence diagram for explaining example (5) of a registration request in the embodiment of the present invention. In step S501, the UE 20 transmits a registration request including the fifth information to the AMF 30A. The fifth information may be information indicating that the UE supports TA granularity network slicing services. Support of the UE 20 may mean whether or not to support a network slice service of TA granularity, or may mean, for example, whether or not to support 52nd information. The fifth information may be set in the 5GMM capability IE.
　続くステップＳ５０２において、ＡＭＦ３０Ａは、第５１の情報及び第５２の情報を含む登録許可をＵＥ２０に送信する。続くステップＳ５０３では、ＵＥ２０はＮＳＳＡＩストレージを更新する。続くステップＳ５０４では、ＵＥ２０は他のＴＡに移動する。続くステップＳ５０５では、ＳＩＢ及びＮＳＳＡＩストレージに基づいてＳ－ＮＳＳＡＩが使用できるか否かを決定する。 In the following step S502, the AMF 30A transmits registration permission including the 51st information and the 52nd information to the UE 20. In the following step S503, the UE 20 updates the NSSAI storage. In the following step S504, the UE 20 moves to another TA. In the following step S505, it is determined whether S-NSSAI can be used based on the SIB and NSSAI storage.
　第５１の情報は、ＵＥ２０の現在位置では使用できないＳ－ＮＳＳＡＩであってもよい。第５１の情報は、Ｒｅｊｅｃｔｅｄ　ＮＳＳＡＩ　ＩＥに含まれていてもよい。また、当該Ｓ－ＮＳＳＡＩを含めるＩＥはこれに限定されなくてもよい。位置とは、ＴＡＩであってもよいし、地理的位置でもよいし、その他位置を示す情報であってもよい。 The 51st information may be S-NSSAI that cannot be used at the current location of the UE 20. The 51st information may be included in the Rejected NSSAI IE. Furthermore, the IE that includes the S-NSSAI is not limited to this. The location may be TAI, a geographic location, or other information indicating the location.
　第５１の情報を受信したＵＥ２０は、現在位置では第５１の情報を利用しない。第５１の情報を利用しないとは、いかなるＮＡＳ手順で利用しないという意味であってよい。例えば、ＵＥ２０の位置が現在位置である限り、登録手順で第５１の情報を利用しない。また、ＰＤＵセッション確立手順でも第５１の情報を利用しない。利用しないとは、各ＮＡＳメッセージに含めないという意味であってよい。 The UE 20 that has received the 51st information does not use the 51st information at its current location. Not using the 51st information may mean not using it in any NAS procedure. For example, as long as the location of the UE 20 is the current location, the 51st information is not used in the registration procedure. Furthermore, the 51st information is not used in the PDU session establishment procedure. Not using it may mean not including it in each NAS message.
　第５１の情報を受信したＵＥ２０は、第５１の情報を含めるＩＥ及び第５１の情報に関連付けて当該メッセージに含まれるｃａｕｓｅ値に応じたＮＳＳＡＩストレージに格納されてよい。ｃａｕｓｅ値は、第５２の情報であってよい。 The UE 20 that has received the 51st information may store it in the NSSAI storage according to the IE that includes the 51st information and the cause value included in the message in association with the 51st information. The cause value may be the 52nd information.
　第５２の情報は、第５１の情報に関連付けられるｃａｕｓｅ値であってもよい。ｃａｕｓｅ値は、Ｒｅｊｅｃｔｅｄ　ＮＳＳＡＩのスコープがトラッキングエリア粒度であることを示す値でよく、例えば、"Ｓ－ＮＳＳＡＩ　ｎｏｔ　ａｖａｉｌａｂｌｅ　ｉｎ　ｔｈｅ　ｃｕｒｒｅｎｔ　ｔｒａｃｋｉｎｇ　ａｒｅａ"であってよい。 The 52nd information may be a cause value associated with the 51st information. The cause value may be a value indicating that the scope of the Rejected NSSAI is tracking area granularity, and may be, for example, "S-NSSAI not available in the current tracking area".
　第５２の情報を受信したＵＥは、現在位置では第５１の情報を利用しない。第５１の情報を利用しないとは、いかなるＮＡＳ手順で利用しないという意味であってよい。例えば、ＵＥの位置が現在位置である限り、登録手順で第５１の情報を利用しない。また、ＰＤＵセッション確立手順でも第５１の情報を利用しない。利用しないとは、各ＮＡＳメッセージに含めないという意味であってよい。しかし、第５２の情報を受信したＵＥは、現在位置の外に移動した場合、第５１の情報を利用してもよい。 The UE that has received the 52nd information does not use the 51st information at its current location. Not using the 51st information may mean not using it in any NAS procedure. For example, as long as the location of the UE is the current location, the 51st information is not used in the registration procedure. Furthermore, the 51st information is not used in the PDU session establishment procedure. Not using it may mean not including it in each NAS message. However, the UE that has received the 52nd information may use the 51st information if it moves outside its current location.
　例えば、一つのＲＡにＴＡ＃１とＴＡ＃２とＴＡ＃３が含まれており、ＴＡ＃１とＴＡ＃２はＳ－ＮＳＳＡＩ＃１をサポートしており、ＴＡ＃３はＳ－ＮＳＳＡＩ＃１をサポートしていないがＳ－ＮＳＳＡＩ＃２をサポートしているようなケースを想定する。ＵＥ２０がＴＡ＃３に在圏しているときにＳ－ＮＳＳＡＩ＃１とＳ－ＮＳＳＡＩ＃２をＲｅｑｕｅｓｅｄ　ＮＳＳＡＩ　ＩＥに含めてメッセージをＡＭＦ３０Ａに送信すると、ＵＥ２０は、Ｓ－ＮＳＳＡＩ＃１が第５１の情報を含めるＩＥに設定され、Ｓ－ＮＳＳＡＩ＃２がＡｌｌｏｗｅｄ　ＮＳＳＡＩ　ＩＥに設定された登録許可を受信する。同時に、ＵＥ２０は、第５１の情報に関連付けられた第５２の情報を受信する。ＵＥ２０は、ＴＡ＃３の外に移動した場合、Ｓ－ＮＳＳＡＩ＃１を利用できる。利用できるとは、登録手順において、登録要求にＳ－ＮＳＳＡＩ＃１を含めることができる（許可されている）という意味であってよいし、ＰＤＵセッション確立要求でＳ－ＮＳＳＡＩ＃１を利用できる（許可されている）という意味であってよい。 For example, one RA includes TA#1, TA#2, and TA#3, TA#1 and TA#2 support S-NSSAI#1, and TA#3 supports S-NSSAI# Let us assume a case where S-NSSAI #1 is not supported but S-NSSAI #2 is supported. When the UE 20 is located in TA #3 and sends a message to the AMF 30A with S-NSSAI #1 and S-NSSAI #2 included in the Requested NSSAI IE, the UE 20 recognizes that S-NSSAI #1 is the 51st is set to the IE that contains the information, and S-NSSAI#2 receives the registration permission set to the Allowed NSSAI IE. At the same time, the UE 20 receives the 52nd information associated with the 51st information. When the UE 20 moves outside TA #3, it can use S-NSSAI #1. "Available" may mean that S-NSSAI #1 can be included in the registration request (permitted) in the registration procedure, or that S-NSSAI #1 can be used in the PDU session establishment request ( may mean that it is permitted).
　言い換えると、ＵＥ２０がＴＡ＃３で受信した第５１の情報に関連付けられるｃａｕｓｅ値は、"Ｓ－ＮＳＳＡＩ　ｎｏｔ　ａｖａｉｌａｂｌｅ　ｉｎ　ｔｈｅ　ｃｕｒｒｅｎｔ　ｔｒａｃｋｉｎｇ　ａｒｅａ"すなわち粒度がＴＡであるため、当該ＴＡの外に出ればｃａｕｓｅ値の制限を解消できＳ－ＮＳＳＡＩ＃１を利用できる。具体的には、ＵＥは、ＮＳＳＡＩストレージのＲｅｊｅｃｔｅｄ　ＮＳＳＡＩに格納されている第５１の情報（Ｓ－ＮＳＳＡＩ＃１）をＮＳＳＡＩストレージのＲｅｊｅｃｔｅｄ　ＮＳＳＡＩから削除（ｄｅｌｅｔｅ／ｒｅｍｏｖｅ）してもよい。これによって、ＵＥ２０は以降のＮＡＳ手順でＳ－ＮＳＳＡＩ＃１を利用できる。具体的には、登録要求でＳ－ＮＳＳＡＩ＃１をＲｅｑｕｅｓｔｅｄ　ＮＳＳＡＩ　ＩＥに含めることができるし、ＰＤＵセッション確立のためのＵＬ　ＮＡＳ　ＴＲＡＮＳＰＯＲＴメッセージのＳ－ＮＳＳＡＩ　ＩＥにＳ－ＮＳＳＡＩ＃１を設定することができるという意味であってよい。 In other words, the cause value associated with the 51st information that the UE 20 received at TA #3 is "S-NSSAI not available in the current tracking area", that is, the granularity is TA, so if it goes outside the TA, it will cause Value restrictions can be resolved and S-NSSAI#1 can be used. Specifically, the UE may delete/remove the 51st information (S-NSSAI#1) stored in the Rejected NSSAI of the NSSAI storage from the Rejected NSSAI of the NSSAI storage. This allows the UE 20 to use S-NSSAI #1 in subsequent NAS procedures. Specifically, S-NSSAI #1 can be included in the Requested NSSAI IE in the registration request, and S-NSSAI #1 can be set in the S-NSSAI IE of the UL NAS TRANSPORT message for establishing a PDU session. It may mean that it is possible.
　図１１は、本発明の実施の形態におけるストレージ動作の例を示す図である。図１１に示されるように、ＴＡ１でＳ－ＮＳＳＡＩ＃１がサポートされ、ＴＡ２でＳ－ＮＳＳＡＩ＃１がサポートされないケースを想定する。ＵＥは、ＴＡ１に在圏しているときＮＳＳＡＡ（Network Slice-Specific Authentication and Authorization）を起動し、"Ｐｅｎｄｉｎｇ　ＮＳＳＡＩ（Ｓ－ＮＳＳＡＩ＃１）"をＡＭＦから受信する。続いて、ＵＥはＴＡ２に移動し、"Ｒｅｊｅｃｔｅｄ　ＮＳＳＡＩ　（Ｓ－ＮＳＳＡＩ＃１）　ｗｉｔｈ　ｃａｕｓｅ　ｐｅｒ　ＴＡ"をＡＭＦから受信する。当該ｃａｕｓｅ値は、現在のトラッキングエリアでは不可を示す。このとき、ＵＥにおけるＮＳＳＡＩストレージの挙動は、以下に示される動作であってもよい。 FIG. 11 is a diagram showing an example of storage operation in the embodiment of the present invention. As shown in FIG. 11, a case is assumed in which TA1 supports S-NSSAI #1 and TA2 does not support S-NSSAI #1. When located in TA1, the UE activates NSSAA (Network Slice-Specific Authentication and Authorization) and receives "Pending NSSAI (S-NSSAI #1)" from the AMF. Subsequently, the UE moves to TA2 and receives "Rejected NSSAI (S-NSSAI #1) with cause per TA" from the AMF. The cause value indicates that it is not possible in the current tracking area. At this time, the behavior of NSSAI storage in the UE may be as shown below.
　例えば、当該Ｓ－ＮＳＳＡＩ（図１１の例ではＳ－ＮＳＳＡＩ＃１）現在のトラッキングエリアで拒絶されたＳ－ＮＳＳＡＩにマッピングしてＮＳＳＡＩストレージに保持してもよい。すなわち、トラッキングエリアごとという粒度が新たに定義されてもよい。 For example, the S-NSSAI (S-NSSAI#1 in the example of FIG. 11) may be mapped to the S-NSSAI rejected in the current tracking area and held in the NSSAI storage. That is, the granularity of each tracking area may be newly defined.
　図１２は、本発明の実施の形態における端末移動時の例を示す図である。図１２に示されるように、Ｓ－ＮＳＳＡＩ＃１のサービスエリアが対応するトラッキングエリアは、ＴＡ１、ＴＡ２、ＴＡ３及びＴＡ４から構成され、Ｓ－ＮＳＳＡＩ＃２のサービスエリアが対応するトラッキングエリアは、ＴＡ５及びＴＡ６から構成されるものとする。図５に示されるように、ＵＥがＴＡ５で登録要求を行い、ネットワークからＳ－ＮＳＳＡＩ＃１への接続が利用できることを示す応答（Allowed NSSAI(S-NSSAI#1)）を受信し、ＵＥはＳ－ＮＳＳＡＩ＃２に接続してもよい。 FIG. 12 is a diagram showing an example when the terminal moves in the embodiment of the present invention. As shown in FIG. 12, the tracking area to which the service area of S-NSSAI#1 corresponds is composed of TA1, TA2, TA3, and TA4, and the tracking area to which the service area of S-NSSAI#2 corresponds is TA5. and TA6. As shown in FIG. 5, the UE makes a registration request at TA5, receives a response (Allowed NSSAI(S-NSSAI#1)) from the network indicating that a connection to S-NSSAI#1 is available, and the UE It may also be connected to S-NSSAI #2.
　ここで、ＵＥが同一登録エリア内のＴＡ４に移動した場合、ネットワークスライスのサービスとしてはＳ－ＮＳＳＡＩ＃１及びＳ－ＮＳＳＡＩ＃２が使用できるため、ネットワークスライスの選択を行ってもよい。すなわち、ＵＥはＳ－ＮＳＳＡＩ＃２からＳ－ＮＳＳＡＩ＃１に接続を変更してもよい。 Here, when the UE moves to TA4 within the same registration area, S-NSSAI #1 and S-NSSAI #2 can be used as network slice services, so network slice selection may be performed. That is, the UE may change the connection from S-NSSAI #2 to S-NSSAI #1.
　図１３は、本発明の実施の形態における端末移動時の例を説明するためのシーケンス図である。ステップＳ６０１において、ＡＭＦ３０Ａ及びＮＳＳＦ３０Ｃは、ネットワークスライスの再選択をトリガする。例えば、他ＡＳ（Access Stratum）からの通知に基づいてＵＥの移動をＡＩが推論することによりＡＭＦ３０Ａがトリガしてもよい。 FIG. 13 is a sequence diagram for explaining an example when the terminal moves in the embodiment of the present invention. In step S601, the AMF 30A and the NSSF 30C trigger reselection of a network slice. For example, the AMF 30A may be triggered by the AI inferring the movement of the UE based on a notification from another AS (Access Stratum).
　ステップＳ６０２において、ＡＭＦ３０Ａは、Ｎｎｓｓｆ＿ＮＳＳｅｌｅｃｔｉｏｎのＧＥＴ　ｒｅｑｕｅｓｔに、ネットワークスライスインスタンスの切り替え要求及びＳｅｌｅｃｔｅｄ　ＮＳＩＩＤ（Network slice instance ID）すなわち選択されていた又はｏｌｄＮＳＩＩＤを示す情報を含めてＮＳＳＦ３０Ｃに送信する。ＮＳＳＦ３０Ｃは、ネットワークスライスインスタンスの切り替え選択機能を備えるＮＦであってもよい。ネットワークスライスインスタンスの切り替え選択機能を備えるとは、ＡＭＦ３０Ａに対して切り替え先のＮＳＩＩＤを通知する機能を有することであってもよい。ＡＭＦ３０Ａは、Ｎｎｓｓｆ＿ＮＳＳｅｌｅｃｔｉｏｎのＧＥＴ　ｒｅｑｕｅｓｔに含まれるＡｔｔｒｉｂｕｔｅとして上記情報を送信してもよい。 In step S602, the AMF 30A sends a GET request of Nnssf_NSSelection including a network slice instance switching request and a Selected NSIID (Network slice instance ID), that is, information indicating the selected or oldNSIID, to the NSSF 30C. The NSSF 30C may be an NF that has a network slice instance switching and selection function. Having a network slice instance switching selection function may mean having a function of notifying the AMF 30A of the NSI ID to which switching is to be made. The AMF 30A may transmit the above information as an Attribute included in the GET request of Nnssf_NSSelection.
　続くステップＳ６０３において、ＮＳＳＦ３０Ｃは、ネットワークスライスを再選択する。続くステップＳ６０４において、ＮＳＳＦ３０Ｃは、Ｎｎｓｓｆ＿ＮＳＳｅｌｅｃｔｉｏｎの２００ＯＫをＡＭＦ３０Ａに送信する。当該メッセージには、切り替え先のネットワークスライスインスタンスの候補及び切り替え先のネットワークスライスインスタンスの候補の優先度が含まれてもよい。切り替え先のネットワークスライスインスタンスの候補は、ＮＳＳＩＤで通知されてもよい。切り替え先のネットワークスライスインスタンスの候補は、複数あってもよい。ネットワークスライスインスタンスの候補の優先度とは、切り替え先のネットワークスライスインスタンスの候補が複数ある場合、それぞれの候補に関連付けられている優先度であってもよい。当該優先度を示す情報を受信したＡＭＦ３０Ａは、優先度に基づいて切り替え先ネットワークスライスインスタンスの候補を決定する。 In the following step S603, the NSSF 30C reselects a network slice. In subsequent step S604, the NSSF 30C transmits 200OK of Nnssf_NSSelection to the AMF 30A. The message may include a switch destination network slice instance candidate and a priority of the switch destination network slice instance candidate. Candidates for switching destination network slice instances may be notified by NSSID. There may be multiple candidates for the network slice instance to switch to. The priority of network slice instance candidates may be the priority associated with each candidate when there are multiple network slice instance candidates to switch to. The AMF 30A that has received the information indicating the priority determines candidates for the switching destination network slice instance based on the priority.
　また、例えば、ＮＳＳＦ３０Ｃは、Ｎｎｓｓｆ＿ＮＳＳｅｌｅｃｔｉｏｎに、新ＮＳＳＩＤ、関連付けられるＮＳＳＡＩ、設定されたＮＳＳＡＩ、ａｌｌｏｗｅｄ　ＮＳＳＡＩを含めてＡＭＦ３０Ａに送信してもよい。 Also, for example, the NSSF 30C may include the new NSSID, the associated NSSAI, the set NSSAI, and the allowed NSSAI in Nnssf_NSSelection and transmit it to the AMF 30A.
　続くステップＳ６０５において、ＡＭＦ３０Ａは、ＣＯＮＦＩＧＲＡＴＩＯＮ　ＵＰＤＡＴＥ　ＣＯＭＭＡＮＤに"ｒｅｇｉｓｔｒａｔｉｏｎ　ｒｅｑｕｅｓｔｅｄ"を示す情報を含めてＵＥ２０に送信する。当該情報は、ＵＥ２０からの位置登録を促す。 In the following step S605, the AMF 30A transmits the CONFIGRATION UPDATE COMMAND including information indicating "registration requested" to the UE 20. The information prompts the UE 20 to register its location.
　続くステップＳ６０６において、ＵＥ２０は、登録要求をＡＭＦ３０Ａに送信する。続くステップＳ６０７において、ＡＭＦ３０Ａは、当該メッセージに応じてＵＥ２０から送信される登録要求に応じて、切り替え先のＮＳＩＩＤと切り替え先のＳ－ＮＳＳＡＩのマッピングを管理する。また、ＵＥ２０から送信される登録要求を受信するとき、ＡＭＦリロケーション（非特許文献２参照）が必要な場合は、ＡＭＦリロケーションを起動してもよい。続くステップＳ６０８において、ＡＭＦ３０Ａは、登録許可をＵＥ２０に送信する。 In the following step S606, the UE 20 transmits a registration request to the AMF 30A. In subsequent step S607, the AMF 30A manages the mapping of the switching destination NSIID and the switching destination S-NSSAI in response to the registration request transmitted from the UE 20 in response to the message. Further, when receiving a registration request transmitted from the UE 20, if AMF relocation (see Non-Patent Document 2) is required, AMF relocation may be activated. In subsequent step S608, the AMF 30A transmits registration permission to the UE 20.
　上述の実施例により、ネットワークスライスを提供する粒度を登録エリアごとからトラッキングエリアごとに変更し、ユーザが在圏するトラッキングエリアに基づいてネットワークスライスを提供することができる。 According to the embodiment described above, the granularity of providing network slices can be changed from each registered area to each tracking area, and network slices can be provided based on the tracking area where the user is located.
　すなわち、通信システムにおいて、ネットワークスライスを提供するサービスエリア設定の柔軟性を向上させることができる。 That is, in the communication system, it is possible to improve the flexibility of setting a service area for providing network slices.
　（装置構成）
　次に、これまでに説明した処理及び動作を実施する基地局１０、ネットワークノード３０及び端末２０の機能構成例を説明する。基地局１０、ネットワークノード３０及び端末２０は上述した実施例を実施する機能を含む。ただし、基地局１０、ネットワークノード３０及び端末２０はそれぞれ、実施例の中の一部の機能のみを備えることとしてもよい。 (Device configuration)
Next, an example of the functional configuration of the base station 10, network node 30, and terminal 20 that implement the processes and operations described above will be described. Base station 10, network node 30 and terminal 20 include functionality to implement the embodiments described above. However, the base station 10, network node 30, and terminal 20 may each have only some of the functions in the embodiment.
　＜基地局１０及びネットワークノード３０＞
　図１４は、基地局１０の機能構成の一例を示す図である。図１４に示されるように、基地局１０は、送信部１１０と、受信部１２０と、設定部１３０と、制御部１４０とを有する。図１４に示される機能構成は一例に過ぎない。本発明の実施の形態に係る動作を実施できるのであれば、機能区分及び機能部の名称はどのようなものでもよい。なお、ネットワークノード３０は、基地局１０と同様の機能構成を有してもよい。また、システムアーキテクチャ上で複数の異なる機能を有するネットワークノード３０は、機能ごとに分離された複数のネットワークノード３０から構成されてもよい。 <Base station 10 and network node 30>
FIG. 14 is a diagram showing an example of the functional configuration of the base station 10. As shown in FIG. 14, base station 10 includes a transmitting section 110, a receiving section 120, a setting section 130, and a control section 140. The functional configuration shown in FIG. 14 is only an example. As long as the operations according to the embodiments of the present invention can be carried out, the functional divisions and functional parts may have any names. Note that the network node 30 may have the same functional configuration as the base station 10. Further, the network node 30 having a plurality of different functions in the system architecture may be configured from a plurality of network nodes 30 separated for each function.
　送信部１１０は、端末２０又は他のネットワークノード３０に送信する信号を生成し、当該信号を有線又は無線で送信する機能を含む。受信部１２０は、端末２０又は他のネットワークノード３０から送信された各種の信号を受信し、受信した信号から、例えばより上位のレイヤの情報を取得する機能を含む。 The transmitting unit 110 includes a function of generating a signal to be transmitted to the terminal 20 or other network node 30, and transmitting the signal by wire or wirelessly. The receiving unit 120 includes a function of receiving various signals transmitted from the terminal 20 or other network nodes 30 and acquiring, for example, information on a higher layer from the received signals.
　設定部１３０は、予め設定される設定情報、及び、端末２０に送信する各種の設定情報を記憶装置に格納し、必要に応じて記憶装置から読み出す。設定情報の内容は、例えば、ネットワークスライスに係る設定等である。 The setting unit 130 stores preset setting information and various setting information to be sent to the terminal 20 in a storage device, and reads them from the storage device as necessary. The contents of the setting information include, for example, settings related to network slices.
　制御部１４０は、実施例において説明したように、ネットワークにおけるネットワークスライスに係る処理を行う。また、制御部１４０は、端末２０との通信に係る処理を行う。制御部１４０における信号送信に関する機能部を送信部１１０に含め、制御部１４０における信号受信に関する機能部を受信部１２０に含めてもよい。 As explained in the embodiment, the control unit 140 performs processing related to network slices in the network. Further, the control unit 140 performs processing related to communication with the terminal 20. A functional unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and a functional unit related to signal reception in the control unit 140 may be included in the receiving unit 120.
　＜端末２０＞
　図１５は、端末２０の機能構成の一例を示す図である。図１５に示されるように、端末２０は、送信部２１０と、受信部２２０と、設定部２３０と、制御部２４０とを有する。図１５に示される機能構成は一例に過ぎない。本発明の実施の形態に係る動作を実施できるのであれば、機能区分及び機能部の名称はどのようなものでもよい。 <Terminal 20>
FIG. 15 is a diagram showing an example of the functional configuration of the terminal 20. As shown in FIG. 15, the terminal 20 includes a transmitting section 210, a receiving section 220, a setting section 230, and a control section 240. The functional configuration shown in FIG. 15 is only an example. As long as the operations according to the embodiments of the present invention can be carried out, the functional divisions and functional parts may have any names.
　送信部２１０は、送信データから送信信号を作成し、当該送信信号を無線で送信する。受信部２２０は、各種の信号を無線受信し、受信した物理レイヤの信号からより上位のレイヤの信号を取得する。また、受信部２２０は、ネットワークノード３０から送信されるＮＲ－ＰＳＳ、ＮＲ－ＳＳＳ、ＮＲ－ＰＢＣＨ、ＤＬ／ＵＬ制御信号又は参照信号等を受信する機能を有する。 The transmitter 210 creates a transmission signal from the transmission data and wirelessly transmits the transmission signal. The receiving unit 220 wirelessly receives various signals and obtains higher layer signals from the received physical layer signals. Further, the receiving unit 220 has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL/UL control signal, reference signal, etc. transmitted from the network node 30.
　設定部２３０は、受信部２２０によりネットワークノード３０から受信した各種の設定情報を記憶装置に格納し、必要に応じて記憶装置から読み出す。また、設定部２３０は、予め設定される設定情報も格納する。設定情報の内容は、例えば、ネットワークスライスに係る設定等である。 The setting unit 230 stores various setting information received from the network node 30 by the receiving unit 220 in a storage device, and reads it from the storage device as necessary. The setting unit 230 also stores setting information that is set in advance. The contents of the setting information include, for example, settings related to network slices.
　制御部２４０は、実施例において説明したように、ネットワーク及びネットワークスライスへの接続制御に係る処理を行う。制御部２４０における信号送信に関する機能部を送信部２１０に含め、制御部２４０における信号受信に関する機能部を受信部２２０に含めてもよい。 As described in the embodiment, the control unit 240 performs processing related to connection control to the network and network slices. A functional unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and a functional unit related to signal reception in the control unit 240 may be included in the receiving unit 220.
　（ハードウェア構成）
　上記実施形態の説明に用いたブロック図（図１４及び図１５）は、機能単位のブロックを示している。これらの機能ブロック（構成部）は、ハードウェア及びソフトウェアの少なくとも一方の任意の組み合わせによって実現される。また、各機能ブロックの実現方法は特に限定されない。すなわち、各機能ブロックは、物理的又は論理的に結合した１つの装置を用いて実現されてもよいし、物理的又は論理的に分離した２つ以上の装置を直接的又は間接的に（例えば、有線、無線などを用いて）接続し、これら複数の装置を用いて実現されてもよい。機能ブロックは、上記１つの装置又は上記複数の装置にソフトウェアを組み合わせて実現されてもよい。 (Hardware configuration)
The block diagrams (FIGS. 14 and 15) used to explain the above embodiments show blocks in functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using one physically or logically coupled device, or may be realized using two or more physically or logically separated devices directly or indirectly (e.g. , wired, wireless, etc.) and may be realized using a plurality of these devices. The functional block may be realized by combining software with the one device or the plurality of devices.
　機能には、判断、決定、判定、計算、算出、処理、導出、調査、探索、確認、受信、送信、出力、アクセス、解決、選択、選定、確立、比較、想定、期待、見做し、報知（broadcasting）、通知（notifying）、通信（communicating）、転送（forwarding）、構成（configuring）、再構成（reconfiguring）、割り当て（allocating、mapping）、割り振り（assigning）などがあるが、これらに限られない。たとえば、送信を機能させる機能ブロック（構成部）は、送信部（transmitting　unit）や送信機（transmitter）と呼称される。いずれも、上述したとおり、実現方法は特に限定されない。 Functions include judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, These include, but are not limited to, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning. I can't do it. For example, a functional block (configuration unit) that performs transmission is called a transmitting unit or a transmitter. In either case, as described above, the implementation method is not particularly limited.
　例えば、本開示の一実施の形態におけるネットワークノード３０、端末２０等は、本開示の無線通信方法の処理を行うコンピュータとして機能してもよい。図１６は、本開示の一実施の形態に係る基地局１０及び端末２０のハードウェア構成の一例を示す図である。ネットワークノード３０は、基地局１０と同様のハードウェア構成を有してもよい。上述の基地局１０及び端末２０は、物理的には、プロセッサ１００１、記憶装置１００２、補助記憶装置１００３、通信装置１００４、入力装置１００５、出力装置１００６、バス１００７などを含むコンピュータ装置として構成されてもよい。 For example, the network node 30, terminal 20, etc. in an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. FIG. 16 is a diagram illustrating an example of the hardware configuration of the base station 10 and the terminal 20 according to an embodiment of the present disclosure. Network node 30 may have a similar hardware configuration to base station 10. The base station 10 and terminal 20 described above are physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc. Good too.
　なお、以下の説明では、「装置」という文言は、回路、デバイス、ユニット等に読み替えることができる。基地局１０及び端末２０のハードウェア構成は、図に示した各装置を１つ又は複数含むように構成されてもよいし、一部の装置を含まずに構成されてもよい。 Note that in the following description, the word "apparatus" can be read as a circuit, a device, a unit, etc. The hardware configuration of the base station 10 and the terminal 20 may be configured to include one or more of each device shown in the figure, or may be configured not to include some of the devices.
　基地局１０及び端末２０における各機能は、プロセッサ１００１、記憶装置１００２等のハードウェア上に所定のソフトウェア（プログラム）を読み込ませることによって、プロセッサ１００１が演算を行い、通信装置１００４による通信を制御したり、記憶装置１００２及び補助記憶装置１００３におけるデータの読み出し及び書き込みの少なくとも一方を制御したりすることによって実現される。 Each function in the base station 10 and the terminal 20 is performed by loading predetermined software (programs) onto hardware such as the processor 1001 and the storage device 1002, so that the processor 1001 performs calculations and controls communication by the communication device 1004. This is realized by controlling at least one of reading and writing data in the storage device 1002 and the auxiliary storage device 1003.
　プロセッサ１００１は、例えば、オペレーティングシステムを動作させてコンピュータ全体を制御する。プロセッサ１００１は、周辺装置とのインタフェース、制御装置、演算装置、レジスタ等を含む中央処理装置（ＣＰＵ：Central Processing Unit）で構成されてもよい。例えば、上述の制御部１４０、制御部２４０等は、プロセッサ１００１によって実現されてもよい。 The processor 1001, for example, operates an operating system to control the entire computer. The processor 1001 may be configured with a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, registers, and the like. For example, the above-described control unit 140, control unit 240, etc. may be implemented by the processor 1001.
　また、プロセッサ１００１は、プログラム（プログラムコード）、ソフトウェアモジュール又はデータ等を、補助記憶装置１００３及び通信装置１００４の少なくとも一方から記憶装置１００２に読み出し、これらに従って各種の処理を実行する。プログラムとしては、上述の実施の形態において説明した動作の少なくとも一部をコンピュータに実行させるプログラムが用いられる。例えば、図１４に示した基地局１０の制御部１４０は、記憶装置１００２に格納され、プロセッサ１００１で動作する制御プログラムによって実現されてもよい。また、例えば、図１５に示した端末２０の制御部２４０は、記憶装置１００２に格納され、プロセッサ１００１で動作する制御プログラムによって実現されてもよい。上述の各種処理は、１つのプロセッサ１００１によって実行される旨を説明してきたが、２以上のプロセッサ１００１により同時又は逐次に実行されてもよい。プロセッサ１００１は、１以上のチップによって実装されてもよい。なお、プログラムは、電気通信回線を介してネットワークから送信されてもよい。 Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 to the storage device 1002, and executes various processes in accordance with these. As the program, a program that causes a computer to execute at least part of the operations described in the above embodiments is used. For example, the control unit 140 of the base station 10 shown in FIG. 14 may be realized by a control program stored in the storage device 1002 and operated on the processor 1001. Further, for example, the control unit 240 of the terminal 20 shown in FIG. 15 may be realized by a control program stored in the storage device 1002 and operated on the processor 1001. Although the various processes described above have been described as being executed by one processor 1001, they may be executed by two or more processors 1001 simultaneously or sequentially. Processor 1001 may be implemented by one or more chips. Note that the program may be transmitted from a network via a telecommunications line.
　記憶装置１００２は、コンピュータ読み取り可能な記録媒体であり、例えば、ＲＯＭ（Read Only Memory）、ＥＰＲＯＭ（Erasable Programmable ROM）、ＥＥＰＲＯＭ（Electrically Erasable Programmable ROM）、ＲＡＭ（Random Access Memory）等の少なくとも１つによって構成されてもよい。記憶装置１００２は、レジスタ、キャッシュ、メインメモリ（主記憶装置）等と呼ばれてもよい。記憶装置１００２は、本開示の一実施の形態に係る通信方法を実施するために実行可能なプログラム（プログラムコード）、ソフトウェアモジュール等を保存することができる。 The storage device 1002 is a computer-readable recording medium, such as at least one of ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. may be configured. The storage device 1002 may be called a register, cache, main memory, or the like. The storage device 1002 can store executable programs (program codes), software modules, and the like to implement a communication method according to an embodiment of the present disclosure.
　補助記憶装置１００３は、コンピュータ読み取り可能な記録媒体であり、例えば、ＣＤ－ＲＯＭ（Compact Disc ROM）等の光ディスク、ハードディスクドライブ、フレキシブルディスク、光磁気ディスク（例えば、コンパクトディスク、デジタル多用途ディスク、Ｂｌｕ－ｒａｙ（登録商標）ディスク）、スマートカード、フラッシュメモリ（例えば、カード、スティック、キードライブ）、フロッピー（登録商標）ディスク、磁気ストリップ等の少なくとも１つによって構成されてもよい。上述の記憶媒体は、例えば、記憶装置１００２及び補助記憶装置１００３の少なくとも一方を含むデータベース、サーバその他の適切な媒体であってもよい。 The auxiliary storage device 1003 is a computer-readable recording medium, such as an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (for example, a compact disk, a digital versatile disk, a Blu-ray disk, etc.). -ray disk), smart card, flash memory (eg, card, stick, key drive), floppy disk, magnetic strip, etc. The above-mentioned storage medium may be, for example, a database including at least one of the storage device 1002 and the auxiliary storage device 1003, a server, or other suitable medium.
　通信装置１００４は、有線ネットワーク及び無線ネットワークの少なくとも一方を介してコンピュータ間の通信を行うためのハードウェア（送受信デバイス）であり、例えばネットワークデバイス、ネットワークコントローラ、ネットワークカード、通信モジュールなどともいう。通信装置１００４は、例えば周波数分割複信（ＦＤＤ：Frequency　Division　Duplex）及び時分割複信（ＴＤＤ：Time　Division　Duplex）の少なくとも一方を実現するために、高周波スイッチ、デュプレクサ、フィルタ、周波数シンセサイザなどを含んで構成されてもよい。例えば、送受信アンテナ、アンプ部、送受信部、伝送路インタフェース等は、通信装置１００４によって実現されてもよい。送受信部は、送信部と受信部とで、物理的に、または論理的に分離された実装がなされてもよい。 The communication device 1004 is hardware (transmission/reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc., for example. The communication device 1004 includes, for example, a high frequency switch, a duplexer, a filter, a frequency synthesizer, etc. in order to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). It may be composed of. For example, a transmitting/receiving antenna, an amplifier section, a transmitting/receiving section, a transmission line interface, etc. may be realized by the communication device 1004. The transmitting and receiving unit may be physically or logically separated into a transmitting unit and a receiving unit.
　入力装置１００５は、外部からの入力を受け付ける入力デバイス（例えば、キーボード、マウス、マイクロフォン、スイッチ、ボタン、センサ等）である。出力装置１００６は、外部への出力を実施する出力デバイス（例えば、ディスプレイ、スピーカー、LEDランプ等）である。なお、入力装置１００５及び出力装置１００６は、一体となった構成（例えば、タッチパネル）であってもよい。 The input device 1005 is an input device (eg, keyboard, mouse, microphone, switch, button, sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that performs output to the outside. Note that the input device 1005 and the output device 1006 may have an integrated configuration (for example, a touch panel).
　また、プロセッサ１００１及び記憶装置１００２等の各装置は、情報を通信するためのバス１００７によって接続される。バス１００７は、単一のバスを用いて構成されてもよいし、装置間ごとに異なるバスを用いて構成されてもよい。 Further, each device such as the processor 1001 and the storage device 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses for each device.
　また、基地局１０及び端末２０は、マイクロプロセッサ、デジタル信号プロセッサ（ＤＳＰ：Digital Signal Processor）、ＡＳＩＣ（Application Specific Integrated Circuit）、ＰＬＤ（Programmable Logic Device）、ＦＰＧＡ（Field Programmable Gate Array）等のハードウェアを含んで構成されてもよく、当該ハードウェアにより、各機能ブロックの一部又は全てが実現されてもよい。例えば、プロセッサ１００１は、これらのハードウェアの少なくとも１つを用いて実装されてもよい。 The base station 10 and the terminal 20 also include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), and a field programmable gate array (FPGA). A part or all of each functional block may be realized by the hardware. For example, processor 1001 may be implemented using at least one of these hardwares.
　図１７に車両２００１の構成例を示す。図１７に示すように、車両２００１は駆動部２００２、操舵部２００３、アクセルペダル２００４、ブレーキペダル２００５、シフトレバー２００６、前輪２００７、後輪２００８、車軸２００９、電子制御部２０１０、各種センサ２０２１～２０２９、情報サービス部２０１２と通信モジュール２０１３を備える。本開示において説明した各態様／実施形態は、車両２００１に搭載される通信装置に適用されてもよく、例えば、通信モジュール２０１３に適用されてもよい。 FIG. 17 shows an example of the configuration of the vehicle 2001. As shown in FIG. 17, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, a front wheel 2007, a rear wheel 2008, an axle 2009, an electronic control unit 2010, and various sensors 2021 to 2029. , an information service section 2012 and a communication module 2013. Each aspect/embodiment described in this disclosure may be applied to a communication device mounted on vehicle 2001, for example, may be applied to communication module 2013.
　駆動部２００２は例えば、エンジン、モータ、エンジンとモータのハイブリッドで構成される。操舵部２００３は、少なくともステアリングホイール（ハンドルとも呼ぶ）を含み、ユーザによって操作されるステアリングホイールの操作に基づいて前輪及び後輪の少なくとも一方を操舵するように構成される。 The drive unit 2002 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also referred to as a steering wheel), and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.
　電子制御部２０１０は、マイクロプロセッサ２０３１、メモリ（ROM、RAM）２０３２、通信ポート（ＩＯポート）２０３３で構成される。電子制御部２０１０には、車両２００１に備えられた各種センサ２０２１～２０２９からの信号が入力される。電子制御部２０１０は、ＥＣＵ（Electronic Control Unit）と呼んでも良い。 The electronic control unit 2010 is composed of a microprocessor 2031, memory (ROM, RAM) 2032, and communication port (IO port) 2033. Signals from various sensors 2021 to 2029 provided in the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).
　各種センサ２０２１～２０２９からの信号としては、モータの電流をセンシングする電流センサ２０２１からの電流信号、回転数センサ２０２２によって取得された前輪や後輪の回転数信号、空気圧センサ２０２３によって取得された前輪や後輪の空気圧信号、車速センサ２０２４によって取得された車速信号、加速度センサ２０２５によって取得された加速度信号、アクセルペダルセンサ２０２９によって取得されたアクセルペダルの踏み込み量信号、ブレーキペダルセンサ２０２６によって取得されたブレーキペダルの踏み込み量信号、シフトレバーセンサ２０２７によって取得されたシフトレバーの操作信号、物体検知センサ２０２８によって取得された障害物、車両、歩行者等を検出するための検出信号等がある。 Signals from various sensors 2021 to 2029 include a current signal from a current sensor 2021 that senses the motor current, a front wheel and rear wheel rotation speed signal obtained by a rotation speed sensor 2022, and a front wheel rotation speed signal obtained by an air pressure sensor 2023. and rear wheel air pressure signals, vehicle speed signals acquired by vehicle speed sensor 2024, acceleration signals acquired by acceleration sensor 2025, accelerator pedal depression amount signals acquired by accelerator pedal sensor 2029, and brake pedal sensor 2026. These include a brake pedal depression amount signal, a shift lever operation signal acquired by the shift lever sensor 2027, a detection signal for detecting obstacles, vehicles, pedestrians, etc. acquired by the object detection sensor 2028, and the like.
　情報サービス部２０１２は、カーナビゲーションシステム、オーディオシステム、スピーカ、テレビ、ラジオといった、運転情報、交通情報、エンターテイメント情報等の各種情報を提供（出力）するための各種機器と、これらの機器を制御する１つ以上のＥＣＵとから構成される。情報サービス部２０１２は、外部装置から通信モジュール２０１３等を介して取得した情報を利用して、車両２００１の乗員に各種マルチメディア情報及びマルチメディアサービスを提供する。情報サービス部２０１２は、外部からの入力を受け付ける入力デバイス（例えば、キーボード、マウス、マイクロフォン、スイッチ、ボタン、センサ、タッチパネルなど）を含んでもよいし、外部への出力を実施する出力デバイス（例えば、ディスプレイ、スピーカー、ＬＥＤランプ、タッチパネルなど）を含んでもよい。 The information service department 2012 controls various devices such as car navigation systems, audio systems, speakers, televisions, and radios that provide (output) various information such as driving information, traffic information, and entertainment information, and these devices. It is composed of one or more ECUs. The information service unit 2012 provides various multimedia information and multimedia services to the occupants of the vehicle 2001 using information acquired from an external device via the communication module 2013 and the like. The information service department 2012 may include an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.) that accepts input from the outside, and an output device that performs output to the outside (for example, display, speaker, LED lamp, touch panel, etc.).
　運転支援システム部２０３０は、ミリ波レーダ、ＬｉＤＡＲ（Light Detection and Ranging）、カメラ、測位ロケータ（例えば、ＧＮＳＳ等）、地図情報（例えば、高精細（ＨＤ）マップ、自動運転車（ＡＶ）マップ等）、ジャイロシステム（例えば、ＩＭＵ（Inertial Measurement Unit）、ＩＮＳ（Inertial Navigation System）等）、ＡＩ（Artificial Intelligence）チップ、ＡＩプロセッサといった、事故を未然に防止したりドライバの運転負荷を軽減したりするための機能を提供するための各種機器と、これらの機器を制御する１つ以上のＥＣＵとから構成される。また、運転支援システム部２０３０は、通信モジュール２０１３を介して各種情報を送受信し、運転支援機能又は自動運転機能を実現する。 The driving support system unit 2030 includes a millimeter wave radar, LiDAR (Light Detection and Ranging), a camera, a positioning locator (for example, GNSS, etc.), map information (for example, a high-definition (HD) map, an autonomous vehicle (AV) map, etc.) ), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors that prevent accidents and reduce the driver's driving burden. The system is comprised of various devices that provide functions for the purpose and one or more ECUs that control these devices. Further, the driving support system unit 2030 transmits and receives various information via the communication module 2013, and realizes a driving support function or an automatic driving function.
　通信モジュール２０１３は通信ポートを介して、マイクロプロセッサ２０３１および車両２００１の構成要素と通信することができる。例えば、通信モジュール２０１３は通信ポート２０３３を介して、車両２００１に備えられた駆動部２００２、操舵部２００３、アクセルペダル２００４、ブレーキペダル２００５、シフトレバー２００６、前輪２００７、後輪２００８、車軸２００９、電子制御部２０１０内のマイクロプロセッサ２０３１及びメモリ（ＲＯＭ、ＲＡＭ）２０３２、センサ２０２１～２９との間でデータを送受信する。 Communication module 2013 can communicate with microprocessor 2031 and components of vehicle 2001 via a communication port. For example, the communication module 2013 communicates with the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, electronic Data is transmitted and received between the microprocessor 2031, memory (ROM, RAM) 2032, and sensors 2021 to 29 in the control unit 2010.
　通信モジュール２０１３は、電子制御部２０１０のマイクロプロセッサ２０３１によって制御可能であり、外部装置と通信を行うことが可能な通信デバイスである。例えば、外部装置との間で無線通信を介して各種情報の送受信を行う。通信モジュール２０１３は、電子制御部２０１０の内部と外部のどちらにあってもよい。外部装置は、例えば、基地局、移動局等であってもよい。 The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with external devices. For example, various information is transmitted and received with an external device via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, or the like.
　通信モジュール２０１３は、電子制御部２０１０に入力された上述の各種センサ２０２１－２０２８からの信号、当該信号に基づいて得られる情報、及び情報サービス部２０１２を介して得られる外部（ユーザ）からの入力に基づく情報、の少なくとも１つを、無線通信を介して外部装置へ送信してもよい。電子制御部２０１０、各種センサ２０２１－２０２８、情報サービス部２０１２などは、入力を受け付ける入力部と呼ばれてもよい。例えば、通信モジュール２０１３によって送信されるＰＵＳＣＨは、上記入力に基づく情報を含んでもよい。 The communication module 2013 receives signals from the various sensors 2021 to 2028 described above that are input to the electronic control unit 2010, information obtained based on the signals, and input from the outside (user) obtained via the information service unit 2012. At least one of the information based on the information may be transmitted to an external device via wireless communication. The electronic control unit 2010, various sensors 2021-2028, information service unit 2012, etc. may be called an input unit that receives input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above input.
　通信モジュール２０１３は、外部装置から送信されてきた種々の情報（交通情報、信号情報、車間情報等）を受信し、車両２００１に備えられた情報サービス部２０１２へ表示する。情報サービス部２０１２は、情報を出力する（例えば、通信モジュール２０１３によって受信されるＰＤＳＣＨ（又は当該ＰＤＳＣＨから復号されるデータ／情報）に基づいてディスプレイ、スピーカーなどの機器に情報を出力する）出力部と呼ばれてもよい。また、通信モジュール２０１３は、外部装置から受信した種々の情報をマイクロプロセッサ２０３１によって利用可能なメモリ２０３２へ記憶する。メモリ２０３２に記憶された情報に基づいて、マイクロプロセッサ２０３１が車両２００１に備えられた駆動部２００２、操舵部２００３、アクセルペダル２００４、ブレーキペダル２００５、シフトレバー２００６、前輪２００７、後輪２００８、車軸２００９、センサ２０２１～２０２９等の制御を行ってもよい。 The communication module 2013 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device, and displays it on the information service section 2012 provided in the vehicle 2001. The information service unit 2012 is an output unit that outputs information (for example, outputs information to devices such as a display and a speaker based on the PDSCH (or data/information decoded from the PDSCH) received by the communication module 2013). may be called. Communication module 2013 also stores various information received from external devices into memory 2032 that can be used by microprocessor 2031 . Based on the information stored in the memory 2032, the microprocessor 2031 controls the drive section 2002, steering section 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheel 2007, rear wheel 2008, and axle 2009 provided in the vehicle 2001. , sensors 2021 to 2029, etc. may be controlled.
　（実施の形態のまとめ）
　以上、説明したように、本発明の実施の形態によれば、ネットワークスライスを提供するトラッキングエリアで構成されるＴＡＩ（Tracking Area Identity）リストをサポートすることを示す情報及び使用を要求するネットワークスライスを示す情報を含む登録要求を端末から受信する受信部と、前記登録要求に基づいて、前記使用を要求するネットワークスライスに係る情報を含む登録許可を生成する制御部と、前記登録許可を前記端末に送信する送信部とを有するネットワークノードが提供される。 (Summary of embodiments)
As described above, according to the embodiment of the present invention, information indicating that a TAI (Tracking Area Identity) list consisting of tracking areas that provide network slices is supported and network slices that request use are provided. a receiving unit that receives a registration request including information indicating the network slice from the terminal; a control unit that generates a registration permission including information related to the network slice requested to be used based on the registration request; A network node is provided having a transmitter for transmitting.
　上記の構成により、ネットワークスライスを提供する粒度を登録エリアごとからトラッキングエリアごとに変更し、ユーザが在圏するトラッキングエリアに基づいてネットワークスライスを提供することができる。すなわち、通信システムにおいて、ネットワークスライスを提供するサービスエリア設定の柔軟性を向上させることができる。 With the above configuration, the granularity of providing network slices can be changed from each registered area to each tracking area, and network slices can be provided based on the tracking area where the user is located. That is, in a communication system, flexibility in setting a service area for providing network slices can be improved.
　前記制御部は、前記登録許可に、前記使用を要求するネットワークスライスを提供するＴＡＩリストを含めてもよい。当該構成により、ネットワークスライスを提供終了するとき、対応するサービスエリアにおいて、必要に応じてＰＤＵセッションを維持又は解放し、ユーザへ提供するサービス品質を向上させることができる。 The control unit may include, in the registration permission, a TAI list that provides the network slice requested for use. With this configuration, when provision of a network slice is terminated, PDU sessions can be maintained or released as necessary in the corresponding service area, thereby improving the quality of service provided to users.
　前記制御部は、前記登録許可に、使用できるトラッキングエリアの通知を伴うネットワークスライスを示す情報を含めてもよい。当該構成により、ネットワークスライスを提供終了するとき、対応するサービスエリアにおいて、必要に応じてＰＤＵセッションを維持又は解放し、ユーザへ提供するサービス品質を向上させることができる。 The control unit may include information indicating a network slice with notification of a usable tracking area in the registration permission. With this configuration, when provision of a network slice is terminated, PDU sessions can be maintained or released as necessary in the corresponding service area, thereby improving the quality of service provided to users.
前記制御部は、前記登録許可に、現在のトラッキングエリアでは使用できないネットワークスライスを示す情報を含めてもよい。当該構成により、ネットワークスライスを提供終了するとき、対応するサービスエリアにおいて、必要に応じてＰＤＵセッションを維持又は解放し、ユーザへ提供するサービス品質を向上させることができる。 The control unit may include information indicating a network slice that cannot be used in the current tracking area in the registration permission. With this configuration, when provision of a network slice is terminated, PDU sessions can be maintained or released as necessary in the corresponding service area, thereby improving the quality of service provided to users.
　前記制御部は、前記登録許可に、前記使用を要求するネットワークスライスが使用できるトラッキングエリアを示す情報を含めてもよい。当該構成により、ネットワークスライスを提供終了するとき、対応するサービスエリアにおいて、必要に応じてＰＤＵセッションを維持又は解放し、ユーザへ提供するサービス品質を向上させることができる。 The control unit may include information indicating a tracking area that can be used by the network slice requesting use in the registration permission. With this configuration, when provision of a network slice is terminated, PDU sessions can be maintained or released as necessary in the corresponding service area, thereby improving the quality of service provided to users.
前記制御部は、前記登録許可に、前記使用を要求するネットワークスライスが現在のトラッキングエリアでは使用できないことを示す情報を含めてもよい。当該構成により、ネットワークスライスを提供終了するとき、対応するサービスエリアにおいて、必要に応じてＰＤＵセッションを維持又は解放し、ユーザへ提供するサービス品質を向上させることができる。 The control unit may include information indicating that the network slice requested for use cannot be used in the current tracking area, in the registration permission. With this configuration, when provision of a network slice is terminated, PDU sessions can be maintained or released as necessary in the corresponding service area, thereby improving the quality of service provided to users.
　また、本発明の実施の形態によれば、ネットワークスライスを提供するトラッキングエリアで構成されるＴＡＩ（Tracking Area Identity）リストをサポートすることを示す情報及び使用を要求するネットワークスライスを示す情報を含む登録要求を端末から受信する受信手順と、前記登録要求に基づいて、前記使用を要求するネットワークスライスに係る情報を含む登録許可を生成する制御手順と、前記登録許可を前記端末に送信する送信手順とネットワークノードが実行する通信方法が提供される。 Further, according to an embodiment of the present invention, a registration including information indicating that a TAI (Tracking Area Identity) list consisting of tracking areas providing network slices is supported and information indicating a network slice requested to be used. a receiving procedure for receiving a request from a terminal; a control procedure for generating a registration permission including information related to the network slice requested for use based on the registration request; and a sending procedure for transmitting the registration permission to the terminal. A communication method performed by a network node is provided.
　上記の構成により、ネットワークスライスを提供する粒度を登録エリアごとからトラッキングエリアごとに変更し、ユーザが在圏するトラッキングエリアに基づいてネットワークスライスを提供することができる。すなわち、通信システムにおいて、ネットワークスライスを提供するサービスエリア設定の柔軟性を向上させることができる。 With the above configuration, the granularity of providing network slices can be changed from each registered area to each tracking area, and network slices can be provided based on the tracking area where the user is located. That is, in a communication system, flexibility in setting a service area for providing network slices can be improved.
　（実施形態の補足）
　以上、本発明の実施の形態を説明してきたが、開示される発明はそのような実施形態に限定されず、当業者は様々な変形例、修正例、代替例、置換例等を理解するであろう。発明の理解を促すため具体的な数値例を用いて説明がなされたが、特に断りのない限り、それらの数値は単なる一例に過ぎず適切な如何なる値が使用されてもよい。上記の説明における項目の区分けは本発明に本質的ではなく、２以上の項目に記載された事項が必要に応じて組み合わせて使用されてよいし、ある項目に記載された事項が、別の項目に記載された事項に（矛盾しない限り）適用されてよい。機能ブロック図における機能部又は処理部の境界は必ずしも物理的な部品の境界に対応するとは限らない。複数の機能部の動作が物理的には１つの部品で行われてもよいし、あるいは１つの機能部の動作が物理的には複数の部品により行われてもよい。実施の形態で述べた処理手順については、矛盾の無い限り処理の順序を入れ替えてもよい。処理説明の便宜上、ネットワークノード３０及び端末２０は機能的なブロック図を用いて説明されたが、そのような装置はハードウェアで、ソフトウェアで又はそれらの組み合わせで実現されてもよい。本発明の実施の形態に従ってネットワークノード３０が有するプロセッサにより動作するソフトウェア及び本発明の実施の形態に従って端末２０が有するプロセッサにより動作するソフトウェアはそれぞれ、ランダムアクセスメモリ（ＲＡＭ）、フラッシュメモリ、読み取り専用メモリ（ＲＯＭ）、ＥＰＲＯＭ、ＥＥＰＲＯＭ、レジスタ、ハードディスク（ＨＤＤ）、リムーバブルディスク、ＣＤ－ＲＯＭ、データベース、サーバその他の適切な如何なる記憶媒体に保存されてもよい。 (Supplementary information on the embodiment)
Although the embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, modifications, alternatives, replacements, etc. Probably. Although the invention has been explained using specific numerical examples to facilitate understanding of the invention, unless otherwise specified, these numerical values are merely examples, and any appropriate values may be used. The classification of items in the above explanation is not essential to the present invention, and matters described in two or more items may be used in combination as necessary, and matters described in one item may be used in another item. may be applied to the matters described in (unless inconsistent). Boundaries of functional units or processing units in a functional block diagram do not necessarily correspond to boundaries of physical parts. The operations of a plurality of functional sections may be physically performed by one component, or the operations of one functional section may be physically performed by a plurality of components. Regarding the processing procedures described in the embodiments, the order of processing may be changed as long as there is no contradiction. Although the network node 30 and the terminal 20 have been described using functional block diagrams for convenience of process description, such devices may be implemented in hardware, software, or a combination thereof. The software that runs on the processor of the network node 30 according to the embodiment of the present invention and the software that runs on the processor that the terminal 20 has according to the embodiment of the present invention are random access memory (RAM), flash memory, read-only memory, respectively. (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.
　また、情報の通知は、本開示で説明した態様／実施形態に限られず、他の方法を用いて行われてもよい。例えば、情報の通知は、物理レイヤシグナリング（例えば、ＤＣＩ（Downlink Control Information）、ＵＣＩ（Uplink Control Information））、上位レイヤシグナリング（例えば、ＲＲＣ（Radio Resource Control）シグナリング、ＭＡＣ（Medium Access Control）シグナリング）、報知情報（ＭＩＢ（Master Information Block）、ＳＩＢ（System Information Block））、その他の信号又はこれらの組み合わせによって実施されてもよい。また、ＲＲＣシグナリングは、ＲＲＣメッセージと呼ばれてもよく、例えば、ＲＲＣ接続セットアップ（RRC Connection Setup）メッセージ、ＲＲＣ接続再構成（RRC Connection Reconfiguration）メッセージ等であってもよい。 Furthermore, the notification of information is not limited to the aspects/embodiments described in this disclosure, and may be performed using other methods. For example, the notification of information may be physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling). , broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or a combination thereof. Further, RRC signaling may be called an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.
　本開示において説明した各態様／実施形態は、ＬＴＥ（Long　Term　Evolution）、ＬＴＥ－Ａ（LTE-Advanced）、ＳＵＰＥＲ　３Ｇ、ＩＭＴ－Ａｄｖａｎｃｅｄ、４Ｇ（4th　generation　mobile　communication　system）、５Ｇ（5th　generation　mobile　communication　system）、ＦＲＡ（Future　Radio　Access）、ＮＲ（new　Radio）、Ｗ－ＣＤＭＡ（登録商標）、ＧＳＭ（登録商標）、ＣＤＭＡ２０００、ＵＭＢ（Ultra　Mobile　Broadband）、ＩＥＥＥ　８０２．１１（Ｗｉ－Ｆｉ（登録商標））、ＩＥＥＥ　８０２．１６（ＷｉＭＡＸ（登録商標））、ＩＥＥＥ　８０２．２０、ＵＷＢ（Ultra-WideBand）、Ｂｌｕｅｔｏｏｔｈ（登録商標）、その他の適切なシステムを利用するシステム及びこれらに基づいて拡張された次世代システムの少なくとも一つに適用されてもよい。また、複数のシステムが組み合わされて（例えば、ＬＴＥ及びＬＴＥ－Ａの少なくとも一方と５Ｇとの組み合わせ等）適用されてもよい。 Each aspect/embodiment described in this disclosure is LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system). system), FRA (Future Radio Access), NR (new Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark) )), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth (registered trademark), and other appropriate systems and systems expanded based on these. It may be applied to at least one next generation system. Furthermore, a combination of a plurality of systems may be applied (for example, a combination of at least one of LTE and LTE-A and 5G).
　本開示において説明した各態様／実施形態は、ＬＴＥ（Long　Term　Evolution）、ＬＴＥ－Ａ（LTE-Advanced）、ＳＵＰＥＲ　３Ｇ、ＩＭＴ－Ａｄｖａｎｃｅｄ、４Ｇ（4th　generation　mobile　communication　system）、５Ｇ（5th　generation　mobile　communication　system）、6th　generation　mobile　communication　system（６Ｇ）、xth　generation　mobile　communication　system（ｘＧ）（ｘＧ（ｘは、例えば整数、小数））、ＦＲＡ（Future　Radio　Access）、ＮＲ（new　Radio）、New　radio　access（ＮＸ）、Future　generation　radio　access（ＦＸ）、Ｗ－ＣＤＭＡ（登録商標）、ＧＳＭ（登録商標）、ＣＤＭＡ２０００、ＵＭＢ（Ultra　Mobile　Broadband）、ＩＥＥＥ　８０２．１１（Ｗｉ－Ｆｉ（登録商標））、ＩＥＥＥ　８０２．１６（ＷｉＭＡＸ（登録商標））、ＩＥＥＥ　８０２．２０、ＵＷＢ（Ultra-WideBand）、Ｂｌｕｅｔｏｏｔｈ（登録商標）、その他の適切なシステムを利用するシステム及びこれらに基づいて拡張、修正、作成、規定された次世代システムの少なくとも一つに適用されてもよい。また、複数のシステムが組み合わされて（例えば、ＬＴＥ及びＬＴＥ－Ａの少なくとも一方と５Ｇとの組み合わせ等）適用されてもよい。 Each aspect/embodiment described in this disclosure is LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system). system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is an integer or decimal number, for example)), FRA (Future Radio Access), NR (new Radio), New radio access ( NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802 Systems that utilize .16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth (registered trademark), and other appropriate systems, and that are extended, modified, created, and defined based on these. The present invention may be applied to at least one of the next generation systems. Furthermore, a combination of a plurality of systems may be applied (for example, a combination of at least one of LTE and LTE-A and 5G).
　本明細書で説明した各態様／実施形態の処理手順、シーケンス、フローチャート等は、矛盾の無い限り、順序を入れ替えてもよい。例えば、本開示において説明した方法については、例示的な順序を用いて様々なステップの要素を提示しており、提示した特定の順序に限定されない。 The order of the processing procedures, sequences, flowcharts, etc. of each aspect/embodiment described in this specification may be changed as long as there is no contradiction. For example, the methods described in this disclosure use an example order to present elements of the various steps and are not limited to the particular order presented.
　本明細書においてネットワークノード３０によって行われるとした特定動作は、場合によってはその上位ノード（upper node）によって行われることもある。ネットワークノード３０を有する１つ又は複数のネットワークノード（network nodes）からなるネットワークにおいて、端末２０との通信のために行われる様々な動作は、ネットワークノード３０及びネットワークノード３０以外の他のネットワークノード（例えば、ＭＭＥ又はＳ－ＧＷ等が考えられるが、これらに限られない）の少なくとも１つによって行われ得ることは明らかである。上記においてネットワークノード３０以外の他のネットワークノードが１つである場合を例示したが、他のネットワークノードは、複数の他のネットワークノードの組み合わせ（例えば、ＭＭＥ及びＳ－ＧＷ）であってもよい。 In this specification, a specific operation performed by the network node 30 may be performed by its upper node in some cases. In a network consisting of one or more network nodes including network node 30, various operations performed for communication with terminal 20 are performed by network node 30 and other network nodes other than network node 30 ( It is clear that this can be done by at least one of the following: for example, MME or S-GW (possible, but not limited to). Although the case where there is one network node other than the network node 30 is illustrated above, the other network node may be a combination of multiple other network nodes (for example, MME and S-GW). .
　本開示において説明した情報又は信号等は、上位レイヤ（又は下位レイヤ）から下位レイヤ（又は上位レイヤ）へ出力され得る。複数のネットワークノードを介して入出力されてもよい。 The information, signals, etc. described in this disclosure can be output from an upper layer (or lower layer) to a lower layer (or upper layer). It may be input/output via multiple network nodes.
　入出力された情報等は特定の場所（例えば、メモリ）に保存されてもよいし、管理テーブルを用いて管理してもよい。入出力される情報等は、上書き、更新、又は追記され得る。出力された情報等は削除されてもよい。入力された情報等は他の装置へ送信されてもよい。 The input/output information may be stored in a specific location (for example, memory) or may be managed using a management table. Information etc. to be input/output may be overwritten, updated, or additionally written. The output information etc. may be deleted. The input information etc. may be transmitted to other devices.
　本開示における判定は、１ビットで表される値（０か１か）によって行われてもよいし、真偽値（Boolean：true又はfalse）によって行われてもよいし、数値の比較（例えば、所定の値との比較）によって行われてもよい。 The determination in the present disclosure may be performed based on a value represented by 1 bit (0 or 1), a truth value (Boolean: true or false), or a comparison of numerical values (e.g. , comparison with a predetermined value).
　ソフトウェアは、ソフトウェア、ファームウェア、ミドルウェア、マイクロコード、ハードウェア記述言語と呼ばれるか、他の名称で呼ばれるかを問わず、命令、命令セット、コード、コードセグメント、プログラムコード、プログラム、サブプログラム、ソフトウェアモジュール、アプリケーション、ソフトウェアアプリケーション、ソフトウェアパッケージ、ルーチン、サブルーチン、オブジェクト、実行可能ファイル、実行スレッド、手順、機能などを意味するよう広く解釈されるべきである。 Software includes instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, whether referred to as software, firmware, middleware, microcode, hardware description language, or by any other name. , should be broadly construed to mean an application, software application, software package, routine, subroutine, object, executable, thread of execution, procedure, function, etc.
　また、ソフトウェア、命令、情報などは、伝送媒体を介して送受信されてもよい。例えば、ソフトウェアが、有線技術（同軸ケーブル、光ファイバケーブル、ツイストペア、デジタル加入者回線（ＤＳＬ：Digital　Subscriber　Line）など）及び無線技術（赤外線、マイクロ波など）の少なくとも一方を使用してウェブサイト、サーバ、又は他のリモートソースから送信される場合、これらの有線技術及び無線技術の少なくとも一方は、伝送媒体の定義内に含まれる。 Additionally, software, instructions, information, etc. may be sent and received via a transmission medium. For example, if the software uses wired technology (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.) and/or wireless technology (infrared, microwave, etc.) to create a website, When transmitted from a server or other remote source, these wired and/or wireless technologies are included within the definition of transmission medium.
　本開示において説明した情報、信号などは、様々な異なる技術のいずれかを使用して表されてもよい。例えば、上記の説明全体に渡って言及され得るデータ、命令、コマンド、情報、信号、ビット、シンボル、チップなどは、電圧、電流、電磁波、磁界若しくは磁性粒子、光場若しくは光子、又はこれらの任意の組み合わせによって表されてもよい。 The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc., which may be referred to throughout the above description, may refer to voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these. It may also be represented by a combination of
　なお、本開示において説明した用語及び本開示の理解に必要な用語については、同一の又は類似する意味を有する用語と置き換えてもよい。例えば、チャネル及びシンボルの少なくとも一方は信号（シグナリング）であってもよい。また、信号はメッセージであってもよい。また、コンポーネントキャリア（ＣＣ：Component　Carrier）は、キャリア周波数、セル、周波数キャリアなどと呼ばれてもよい。 Note that terms explained in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of the channel and the symbol may be a signal. Also, the signal may be a message. Further, a component carrier (CC) may also be called a carrier frequency, a cell, a frequency carrier, or the like.
　本開示において使用する「システム」及び「ネットワーク」という用語は、互換的に使用される。 As used in this disclosure, the terms "system" and "network" are used interchangeably.
　また、本開示において説明した情報、パラメータなどは、絶対値を用いて表されてもよいし、所定の値からの相対値を用いて表されてもよいし、対応する別の情報を用いて表されてもよい。例えば、無線リソースはインデックスによって指示されるものであってもよい。 In addition, the information, parameters, etc. described in this disclosure may be expressed using absolute values, relative values from a predetermined value, or using other corresponding information. may be expressed. For example, radio resources may be indicated by an index.
　上述したパラメータに使用する名称はいかなる点においても限定的な名称ではない。さらに、これらのパラメータを使用する数式等は、本開示で明示的に開示したものと異なる場合もある。様々なチャネル（例えば、ＰＵＣＣＨ、ＰＤＣＣＨなど）及び情報要素は、あらゆる好適な名称によって識別できるので、これらの様々なチャネル及び情報要素に割り当てている様々な名称は、いかなる点においても限定的な名称ではない。 The names used for the parameters mentioned above are not restrictive in any respect. Furthermore, the mathematical formulas etc. using these parameters may differ from those explicitly disclosed in this disclosure. Since the various channels (e.g. PUCCH, PDCCH, etc.) and information elements may be identified by any suitable designation, the various names assigned to these various channels and information elements are in no way exclusive designations. isn't it.
　本開示においては、「基地局（ＢＳ：Base　Station）」、「無線基地局」、「基地局装置」、「固定局（fixed　station）」、「ＮｏｄｅＢ」、「ｅＮｏｄｅＢ（ｅＮＢ）」、「ｇＮｏｄｅＢ（ｇＮＢ）」、「アクセスポイント（access　point）」、「送信ポイント（transmission　point）」、「受信ポイント（reception　point）」、「送受信ポイント（transmission/reception　point）」、「セル」、「セクタ」、「セルグループ」、「キャリア」、「コンポーネントキャリア」などの用語は、互換的に使用され得る。基地局は、マクロセル、スモールセル、フェムトセル、ピコセルなどの用語で呼ばれる場合もある。 In this disclosure, "Base Station (BS)," "wireless base station," "base station device," "fixed station," "NodeB," "eNodeB (eNB)," and "gNodeB (gNB),” “access point,” “transmission point,” “reception point,” “transmission/reception point,” “cell,” “sector” , "cell group," "carrier," "component carrier," and the like may be used interchangeably. A base station is sometimes referred to by terms such as macrocell, small cell, femtocell, and picocell.
　基地局は、１つ又は複数（例えば、３つ）のセルを収容することができる。基地局が複数のセルを収容する場合、基地局のカバレッジエリア全体は複数のより小さいエリアに区分でき、各々のより小さいエリアは、基地局サブシステム（例えば、屋内用の小型基地局（ＲＲＨ：Ｒｅｍｏｔｅ　Ｒａｄｉｏ　Ｈｅａｄ））によって通信サービスを提供することもできる。「セル」又は「セクタ」という用語は、このカバレッジにおいて通信サービスを行う基地局及び基地局サブシステムの少なくとも一方のカバレッジエリアの一部又は全体を指す。 A base station can accommodate one or more (eg, three) cells. If a base station accommodates multiple cells, the overall coverage area of the base station can be partitioned into multiple smaller areas, and each smaller area is divided into multiple subsystems (e.g., small indoor base stations (RRHs)). Communication services can also be provided by Remote Radio Head). The term "cell" or "sector" refers to part or all of the coverage area of a base station and/or base station subsystem that provides communication services in this coverage.
　本開示において、基地局が端末に情報を送信することは、基地局が端末に対して、情報に基づく制御・動作を指示することと読み替えられてもよい。 In the present disclosure, the base station transmitting information to the terminal may be read as the base station instructing the terminal to control/operate based on the information.
　本開示においては、「移動局（ＭＳ：Mobile　Station）」、「ユーザ端末（user　terminal）」、「ユーザ装置（ＵＥ：User　Equipment）」、「端末」などの用語は、互換的に使用され得る。 In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably. .
　移動局は、当業者によって、加入者局、モバイルユニット、加入者ユニット、ワイヤレスユニット、リモートユニット、モバイルデバイス、ワイヤレスデバイス、ワイヤレス通信デバイス、リモートデバイス、モバイル加入者局、アクセス端末、モバイル端末、ワイヤレス端末、リモート端末、ハンドセット、ユーザエージェント、モバイルクライアント、クライアント、又はいくつかの他の適切な用語で呼ばれる場合もある。 A mobile station is defined by a person skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless It may also be referred to as a terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.
　基地局及び移動局の少なくとも一方は、送信装置、受信装置、通信装置などと呼ばれてもよい。なお、基地局及び移動局の少なくとも一方は、移動体に搭載されたデバイス、移動体自体などであってもよい。当該移動体は、移動可能な物体をいい、移動速度は任意である。また移動体が停止している場合も当然含む。当該移動体は、例えば、車両、輸送車両、自動車、自動二輪車、自転車、コネクテッドカー、ショベルカー、ブルドーザー、ホイールローダー、ダンプトラック、フォークリフト、列車、バス、リヤカー、人力車、船舶（ship and other watercraft）、飛行機、ロケット、人工衛星、ドローン（登録商標）、マルチコプター、クアッドコプター、気球、およびこれらに搭載される物を含み、またこれらに限らない。また、当該移動体は、運行指令に基づいて自律走行する移動体であってもよい。乗り物（例えば、車、飛行機など）であってもよいし、無人で動く移動体（例えば、ドローン、自動運転車など）であってもよいし、ロボット（有人型又は無人型）であってもよい。なお、基地局及び移動局の少なくとも一方は、必ずしも通信動作時に移動しない装置も含む。例えば、基地局及び移動局の少なくとも一方は、センサなどのＩｏＴ（Internet of Things）機器であってもよい。 At least one of a base station and a mobile station may be called a transmitting device, a receiving device, a communication device, etc. Note that at least one of the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, or the like. The moving body refers to a movable object, and the moving speed is arbitrary. Naturally, this also includes cases where the moving object is stopped. The mobile objects include, for example, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, carts, rickshaws, ships and other watercraft. , including, but not limited to, airplanes, rockets, artificial satellites, drones (registered trademarks), multicopters, quadcopters, balloons, and objects mounted thereon. Furthermore, the mobile object may be a mobile object that autonomously travels based on a travel command. It may be a vehicle (e.g. car, airplane, etc.), an unmanned moving object (e.g. drone, self-driving car, etc.), or a robot (manned or unmanned). good. Note that at least one of the base station and the mobile station includes devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.
　また、本開示における基地局は、ユーザ端末で読み替えてもよい。例えば、基地局及びユーザ端末間の通信を、複数の端末２０間の通信（例えば、Ｄ２Ｄ（Device-to-Device）、Ｖ２Ｘ（Vehicle-to-Everything）などと呼ばれてもよい）に置き換えた構成について、本開示の各態様／実施形態を適用してもよい。この場合、上述のネットワークノード３０が有する機能を端末２０が有する構成としてもよい。また、「上り」及び「下り」などの文言は、端末間通信に対応する文言（例えば、「サイド（side）」）で読み替えられてもよい。例えば、上りチャネル、下りチャネルなどは、サイドチャネルで読み替えられてもよい。 Additionally, the base station in the present disclosure may be replaced by a user terminal. For example, communication between a base station and a user terminal is replaced with communication between a plurality of terminals 20 (for example, it may be called D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). Regarding the configuration, each aspect/embodiment of the present disclosure may be applied. In this case, the terminal 20 may have the functions that the network node 30 described above has. Further, words such as "up" and "down" may be replaced with words corresponding to inter-terminal communication (for example, "side"). For example, uplink channels, downlink channels, etc. may be replaced with side channels.
　同様に、本開示におけるユーザ端末は、基地局で読み替えてもよい。この場合、上述のユーザ端末が有する機能を基地局が有する構成としてもよい。 Similarly, the user terminal in the present disclosure may be replaced with a base station. In this case, the base station may have the functions that the user terminal described above has.
　本開示で使用する「判断(determining)」、「決定(determining)」という用語は、多種多様な動作を包含する場合がある。「判断」、「決定」は、例えば、判定(judging)、計算(calculating)、算出(computing)、処理(processing)、導出(deriving)、調査(investigating)、探索(looking　up、search、inquiry)（例えば、テーブル、データベース又は別のデータ構造での探索）、確認(ascertaining)した事を「判断」「決定」したとみなす事などを含み得る。また、「判断」、「決定」は、受信(receiving)（例えば、情報を受信すること）、送信(transmitting)(例えば、情報を送信すること)、入力(input)、出力(output)、アクセス(accessing)（例えば、メモリ中のデータにアクセスすること）した事を「判断」「決定」したとみなす事などを含み得る。また、「判断」、「決定」は、解決(resolving)、選択(selecting)、選定(choosing)、確立(establishing)、比較(comparing)などした事を「判断」「決定」したとみなす事を含み得る。つまり、「判断」「決定」は、何らかの動作を「判断」「決定」したとみなす事を含み得る。また、「判断（決定）」は、「想定する（assuming）」、「期待する（expecting）」、「みなす（considering）」などで読み替えられてもよい。 As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of operations. "Judgment" and "decision" include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, search, and inquiry. (e.g., searching in a table, database, or other data structure), and regarding an ascertaining as a "judgment" or "decision." In addition, "judgment" and "decision" refer to receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, and access. (accessing) (e.g., accessing data in memory) may include considering something as a "judgment" or "decision." In addition, "judgment" and "decision" refer to resolving, selecting, choosing, establishing, comparing, etc. as "judgment" and "decision". may be included. In other words, "judgment" and "decision" may include regarding some action as having been "judged" or "determined." Further, "judgment (decision)" may be read as "assuming", "expecting", "considering", etc.
　「接続された(connected)」、「結合された(coupled)」という用語、又はこれらのあらゆる変形は、２又はそれ以上の要素間の直接的又は間接的なあらゆる接続又は結合を意味し、互いに「接続」又は「結合」された２つの要素間に１又はそれ以上の中間要素が存在することを含むことができる。要素間の結合又は接続は、物理的なものであっても、論理的なものであっても、或いはこれらの組み合わせであってもよい。例えば、「接続」は「アクセス」で読み替えられてもよい。本開示で使用する場合、２つの要素は、１又はそれ以上の電線、ケーブル及びプリント電気接続の少なくとも一つを用いて、並びにいくつかの非限定的かつ非包括的な例として、無線周波数領域、マイクロ波領域及び光（可視及び不可視の両方）領域の波長を有する電磁エネルギーなどを用いて、互いに「接続」又は「結合」されると考えることができる。 The terms "connected", "coupled", or any variations thereof, refer to any connection or coupling, direct or indirect, between two or more elements and to each other. It may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled." The bonds or connections between elements may be physical, logical, or a combination thereof. For example, "connection" may be replaced with "access." As used in this disclosure, two elements may include one or more electrical wires, cables, and/or printed electrical connections, as well as in the radio frequency domain, as some non-limiting and non-inclusive examples. , electromagnetic energy having wavelengths in the microwave and optical (both visible and non-visible) ranges.
　参照信号は、ＲＳ（Reference　Signal）と略称することもでき、適用される標準によってパイロット（Pilot）と呼ばれてもよい。 The reference signal can also be abbreviated as RS (Reference Signal), and may be called a pilot depending on the applied standard.
　本開示において使用する「に基づいて」という記載は、別段に明記されていない限り、「のみに基づいて」を意味しない。言い換えれば、「に基づいて」という記載は、「のみに基づいて」と「に少なくとも基づいて」の両方を意味する。 As used in this disclosure, the phrase "based on" does not mean "based solely on" unless explicitly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."
　本開示において使用する「第１の」、「第２の」などの呼称を使用した要素へのいかなる参照も、それらの要素の量又は順序を全般的に限定しない。これらの呼称は、２つ以上の要素間を区別する便利な方法として本開示において使用され得る。したがって、第１及び第２の要素への参照は、２つの要素のみが採用され得ること、又は何らかの形で第１の要素が第２の要素に先行しなければならないことを意味しない。 As used in this disclosure, any reference to elements using the designations "first," "second," etc. does not generally limit the amount or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Thus, reference to a first and second element does not imply that only two elements may be employed or that the first element must precede the second element in any way.
　上記の各装置の構成における「手段」を、「部」、「回路」、「デバイス」等に置き換えてもよい。 "Means" in the configurations of each of the above devices may be replaced with "unit", "circuit", "device", etc.
　本開示において、「含む（include）」、「含んでいる（including）」及びそれらの変形が使用されている場合、これらの用語は、用語「備える（comprising）」と同様に、包括的であることが意図される。さらに、本開示において使用されている用語「又は（or）」は、排他的論理和ではないことが意図される。 Where "include", "including" and variations thereof are used in this disclosure, these terms, like the term "comprising," are inclusive. It is intended that Furthermore, the term "or" as used in this disclosure is not intended to be exclusive or.
　本開示において、例えば、英語でのa, an及びtheのように、翻訳により冠詞が追加された場合、本開示は、これらの冠詞の後に続く名詞が複数形であることを含んでもよい。 In the present disclosure, when articles are added by translation, such as a, an, and the in English, the present disclosure may include that the nouns following these articles are plural.
　本開示において、「ＡとＢが異なる」という用語は、「ＡとＢが互いに異なる」ことを意味してもよい。なお、当該用語は、「ＡとＢがそれぞれＣと異なる」ことを意味してもよい。「離れる」、「結合される」などの用語も、「異なる」と同様に解釈されてもよい。 In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." Note that the term may also mean that "A and B are each different from C". Terms such as "separate" and "coupled" may also be interpreted similarly to "different."
　本開示において説明した各態様／実施形態は単独で用いてもよいし、組み合わせて用いてもよいし、実行に伴って切り替えて用いてもよい。また、所定の情報の通知（例えば、「Ｘであること」の通知）は、明示的に行うものに限られず、暗黙的（例えば、当該所定の情報の通知を行わない）ことによって行われてもよい。 Each aspect/embodiment described in this disclosure may be used alone, in combination, or may be switched and used in accordance with execution. In addition, notification of prescribed information (for example, notification of "X") is not limited to being done explicitly, but may also be done implicitly (for example, not notifying the prescribed information). Good too.
　なお、本開示において、Ｓ－ＮＳＳＡＩは、ネットワークスライスを示す情報の一例である。 Note that in this disclosure, S-NSSAI is an example of information indicating a network slice.
　以上、本開示について詳細に説明したが、当業者にとっては、本開示が本開示中に説明した実施形態に限定されるものではないということは明らかである。本開示は、請求の範囲の記載により定まる本開示の趣旨及び範囲を逸脱することなく修正及び変更態様として実施することができる。したがって、本開示の記載は、例示説明を目的とするものであり、本開示に対して何ら制限的な意味を有するものではない。 Although the present disclosure has been described in detail above, it is clear for those skilled in the art that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure can be implemented as modifications and variations without departing from the spirit and scope of the present disclosure as determined by the claims. Therefore, the description of the present disclosure is for the purpose of illustrative explanation and is not intended to have any limiting meaning on the present disclosure.
１０　　　　基地局
１１０　　　送信部
１２０　　　受信部
１３０　　　設定部
１４０　　　制御部
２０　　　　端末
２１０　　　送信部
２２０　　　受信部
２３０　　　設定部
２４０　　　制御部
３０　　　　ネットワークノード
１００１　　プロセッサ
１００２　　記憶装置
１００３　　補助記憶装置
１００４　　通信装置
１００５　　入力装置
１００６　　出力装置
２００１　　車両
２００２　　駆動部
２００３　　操舵部
２００４　　アクセルペダル
２００５　　ブレーキペダル
２００６　　シフトレバー
２００７　　前輪
２００８　　後輪
２００９　　車軸
２０１０　　電子制御部
２０１２　　情報サービス部
２０１３　　通信モジュール
２０２１　　電流センサ
２０２２　　回転数センサ
２０２３　　空気圧センサ
２０２４　　車速センサ
２０２５　　加速度センサ
２０２６　　ブレーキペダルセンサ
２０２７　　シフトレバーセンサ
２０２８　　物体検出センサ
２０２９　　アクセルペダルセンサ
２０３０　　運転支援システム部
２０３１　　マイクロプロセッサ
２０３２　　メモリ（ＲＯＭ，ＲＡＭ）
２０３３　　通信ポート（ＩＯポート） 10 Base station 110 Transmitting section 120 Receiving section 130 Setting section 140 Control section 20 Terminal 210 Transmitting section 220 Receiving section 230 Setting section 240 Control section 30 Network node 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive section 2003 Steering section 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Front wheel 2008 Rear wheel 2009 Axle 2010 Electronic control section 2012 Information service section 2013 Communication module 2021 Current sensor 2022 Rotational speed sensor 2023 Air pressure sensor 2024 Vehicle speed sensor 202 5 Acceleration Sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driving support system section 2031 Microprocessor 2032 Memory (ROM, RAM)
2033 Communication port (IO port)

Claims (7)

  1. 　ネットワークスライスを提供するトラッキングエリアで構成されるＴＡＩ（Tracking Area Identity）リストをサポートすることを示す情報及び使用を要求するネットワークスライスを示す情報を含む登録要求を端末から受信する受信部と、
    　前記登録要求に基づいて、前記使用を要求するネットワークスライスに係る情報を含む登録許可を生成する制御部と、
    　前記登録許可を前記端末に送信する送信部とを有するネットワークノード。     a receiving unit that receives from a terminal a registration request that includes information indicating that a TAI (Tracking Area Identity) list consisting of tracking areas that provide network slices is supported and information indicating a network slice that is requested to be used;
    a control unit that generates a registration permission including information related to the network slice requested for use based on the registration request;
    a transmitter configured to transmit the registration permission to the terminal.
  2. 　前記制御部は、前記登録許可に、前記使用を要求するネットワークスライスを提供するＴＡＩリストを含める請求項１記載のネットワークノード。 The network node according to claim 1, wherein the control unit includes, in the registration permission, a TAI list that provides the network slice requested for use.
  3. 　前記制御部は、前記登録許可に、使用できるトラッキングエリアの通知を伴うネットワークスライスを示す情報を含める請求項１記載のネットワークノード。 The network node according to claim 1, wherein the control unit includes information indicating a network slice with notification of a usable tracking area in the registration permission.
  4. 　前記制御部は、前記登録許可に、現在のトラッキングエリアでは使用できないネットワークスライスを示す情報を含める請求項１記載のネットワークノード。 The network node according to claim 1, wherein the control unit includes information indicating a network slice that cannot be used in the current tracking area in the registration permission.
  5. 　前記制御部は、前記登録許可に、前記使用を要求するネットワークスライスが使用できるトラッキングエリアを示す情報を含める請求項４記載のネットワークノード。 The network node according to claim 4, wherein the control unit includes, in the registration permission, information indicating a tracking area that can be used by the network slice requesting use.
  6. 　前記制御部は、前記登録許可に、前記使用を要求するネットワークスライスが現在のトラッキングエリアでは使用できないことを示す情報を含める請求項４記載のネットワークノード。 The network node according to claim 4, wherein the control unit includes, in the registration permission, information indicating that the network slice requested for use cannot be used in the current tracking area.
  7. 　ネットワークスライスを提供するトラッキングエリアで構成されるＴＡＩ（Tracking Area Identity）リストをサポートすることを示す情報及び使用を要求するネットワークスライスを示す情報を含む登録要求を端末から受信する受信手順と、
    　前記登録要求に基づいて、前記使用を要求するネットワークスライスに係る情報を含む登録許可を生成する制御手順と、
    　前記登録許可を前記端末に送信する送信手順とネットワークノードが実行する通信方法。     a reception procedure of receiving from a terminal a registration request including information indicating that a TAI (Tracking Area Identity) list consisting of tracking areas providing network slices is supported and information indicating a network slice requested to be used;
    a control procedure for generating a registration permission including information regarding the network slice requested for use based on the registration request;
    A transmission procedure for transmitting the registration permission to the terminal and a communication method executed by a network node.
PCT/JP2022/019538 2022-05-02 2022-05-02 Network node and communication method WO2023214456A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2022/019538 WO2023214456A1 (en) 2022-05-02 2022-05-02 Network node and communication method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2022/019538 WO2023214456A1 (en) 2022-05-02 2022-05-02 Network node and communication method

Publications (1)

Publication Number Publication Date
WO2023214456A1 true WO2023214456A1 (en) 2023-11-09

Family

ID=88646400

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2022/019538 WO2023214456A1 (en) 2022-05-02 2022-05-02 Network node and communication method

Country Status (1)

Country Link
WO (1) WO2023214456A1 (en)

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
INTERDIGITAL INC.: "TR Objective #2: New Solution: Enabling Flexible RAs with Slice Service Area", 3GPP DRAFT; S2-2202945, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Electronic Meeting; 20220406 - 20220412, 29 March 2022 (2022-03-29), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052133757 *
NEC , NTT DOCOMO: "Solution: KI#3 Key Issue #3: Temporary network slices", 3GPP DRAFT; S2-2203091, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. E-Meeting; 20220406 - 20220412, 13 April 2022 (2022-04-13), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052136053 *
NTT DOCOMO: "New Solution: KI#5: Improved support of RAs including TAs supporting Rejected S-NSSAIs", 3GPP DRAFT; S2-2204790, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. E-Meeting; 20220516 - 20220520, 20 May 2022 (2022-05-20), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052160276 *

Similar Documents

Publication Publication Date Title
WO2023214456A1 (en) Network node and communication method
WO2024034073A1 (en) Terminal and communication method
WO2023195370A1 (en) Network node and communication method
WO2023218670A1 (en) Network node and communication method
WO2024038488A1 (en) Terminal and communication method
WO2023218671A1 (en) Network node and communication method
WO2023223511A1 (en) Network node and communication method
WO2023218509A1 (en) Network node, wireless communication system, and communication method
WO2023223512A1 (en) Network node and communication method
WO2024028992A1 (en) Terminal and network node
WO2024004156A1 (en) Network node, base station, and communication method
WO2023067815A1 (en) Network node and communication method
WO2024062583A1 (en) Network node and communication method
WO2023067814A1 (en) Network node and communication method
WO2023119386A1 (en) Network node
WO2023119385A1 (en) Network node
WO2024057550A1 (en) Network node, communication system, and communication method
WO2023175969A1 (en) Network device and radio base station
WO2024057549A1 (en) Network node and communication method
WO2024034074A1 (en) Network node, core network system, and control method
WO2024080000A1 (en) Terminal, base station, and communication method
WO2024034075A1 (en) Base station, terminal, network node, and communication method
WO2023195111A1 (en) Network node and communication method
WO2024038483A1 (en) Network node and synchronization control method
WO2023188038A1 (en) Radio base station and radio communication method

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22940817

Country of ref document: EP

Kind code of ref document: A1