WO2024028992A1 - Terminal et nœud de réseau - Google Patents

Terminal et nœud de réseau Download PDF

Info

Publication number
WO2024028992A1
WO2024028992A1 PCT/JP2022/029711 JP2022029711W WO2024028992A1 WO 2024028992 A1 WO2024028992 A1 WO 2024028992A1 JP 2022029711 W JP2022029711 W JP 2022029711W WO 2024028992 A1 WO2024028992 A1 WO 2024028992A1
Authority
WO
WIPO (PCT)
Prior art keywords
timer
nssai
network slice
network
information
Prior art date
Application number
PCT/JP2022/029711
Other languages
English (en)
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/029711 priority Critical patent/WO2024028992A1/fr
Publication of WO2024028992A1 publication Critical patent/WO2024028992A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service

Definitions

  • the present invention relates to terminals and network nodes in communication systems.
  • 3GPP registered trademark
  • 3rd Generation Partnership Project 3rd Generation Partnership Project
  • 5G Fifth Generation Partnership Project
  • 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.
  • implementation of a limited lifetime network slicing service is being considered.
  • detailed operations of the network and terminals have not been specified in operating time-limited network slices.
  • the present invention has been made in view of the above points, and an object of the present invention is to provide a time-limited network slice service in a communication system.
  • the receiving unit receives information identifying a network slice and a timer value associated with the network slice from a core network; a control unit that starts a timer for setting a value, and the control unit is configured to send a NAS (Non-Access Stratum) message to a core network using information identifying the network slice when the timer expires.
  • NAS Non-Access Stratum
  • a time-limited network slice service can be provided 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. 2 is a sequence diagram for explaining an example (1) of operations related to network slices in the embodiment of the present invention.
  • FIG. 3 is a flowchart for explaining an example (1-1) of terminal operation related to network slices in the embodiment of the present invention.
  • FIG. FIG. 3 is a flowchart for explaining an example (1-2) of terminal operation related to network slices in the embodiment of the present invention.
  • FIG. 12 is a flowchart for explaining an example (1-3) of terminal operation related to network slices in the embodiment of the present invention. 12 is a flowchart for explaining an example (1-4) of terminal operations related to network slices in the embodiment of the present invention.
  • FIG. 12 is a flowchart for explaining an example (1-5) of terminal operations related to network slices in the embodiment of the present invention.
  • FIG. 3 is a flowchart for explaining an example (1-1) of network operation related to network slices in the embodiment of the present invention.
  • FIG. FIG. 3 is a flowchart for explaining an example (1-2) of network operation related to network slices in the embodiment of the present invention.
  • FIG. 12 is a flowchart for explaining an example (1-3) of network operations related to network slices in the embodiment of the present invention.
  • 12 is a flowchart for explaining an example (1-4) of network operations related to network slices in the embodiment of the present invention.
  • 12 is a flowchart for explaining an example (1-5) of network operation related to a network slice in the embodiment of the present invention.
  • FIG. 12 is a flowchart for explaining an example (1-6) of network operation related to a network slice in the embodiment of the present invention.
  • FIG. 7 is a sequence diagram for explaining an example (2) of operations related to network slicing in the embodiment of the present invention.
  • 12 is a flowchart for explaining an example (2-1) of terminal operation related to network slices in the embodiment of the present invention.
  • 12 is a flowchart for explaining an example (2-2) of terminal operation related to a network slice when a Configured NSSAI is received in the embodiment of the present invention.
  • 12 is a flowchart for explaining an example (2-2) of terminal operation related to network slice when receiving Allowed NSSAI in the embodiment of the present invention.
  • 12 is a flowchart for explaining an example (2-2) of terminal operation related to network slice when receiving a conditional Allowed NSSAI in the embodiment of the present invention.
  • 12 is a flowchart for explaining an example (2-2) of terminal operation related to a network slice that receives a configuration update command in which a registration request is set according to the embodiment of the present invention.
  • 12 is a flowchart for explaining an example (2-3) of terminal operation related to network slice in the embodiment of the present invention.
  • 12 is a flowchart for explaining an example (2-4) of terminal operation related to network slices in the embodiment of the present invention.
  • 12 is a flowchart for explaining an example (2-1) of network operation related to network slices in the embodiment of the present invention.
  • 12 is a flowchart for explaining an example (2-2) of network operations related to network slices in the embodiment of the present invention. 12 is a flowchart for explaining an example (2-3) of network operation related to network slices in the embodiment of the present invention.
  • FIG. 7 is a sequence diagram for explaining an example (3) of operations related to network slices in the embodiment of the present invention. 12 is a flowchart for explaining an example (3-1) of terminal operation related to network slices in the embodiment of the present invention. 12 is a flowchart for explaining an example (3-2) of terminal operation related to network slices in the 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.
  • 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 that has 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.
  • implementation of a limited lifetime network slicing service is being considered.
  • detailed operations of the network and terminals have not been specified in operating time-limited network slices.
  • Examples of methods for realizing time-limited network slices include a timer-based method and a URSP (UE Route Selection Policy) method.
  • URSP UE Route Selection Policy
  • the UE may receive an S-NSSAI (Single-NSSAI) that identifies a time-limited network slice from the core network as a Configured NSSAI.
  • S-NSSAI Single-NSSAI
  • the configuration update command may include alternative network slice information that the network notifies the UE when the timer of the timed network slice expires.
  • alternative network slice information that the network notifies the UE when the timer of the timed network slice expires.
  • information indicating an alternative S-NSSAI(s) indicating the time-limited network slice may be included.
  • the network node that includes the alternative network slice information may be AMF, UDM, or NSSF. Note that the network node that includes the alternative network slice information is not limited to this.
  • 5GS mobility management messages or 5GS session management messages may be referred to as NAS messages to simplify the description.
  • the 5GS mobility management messages may be a REGISTRATION REQUEST message or a UL NAS TRANSPORT message.
  • the 5GS session management messages may be a PDU SESSION ESTABLISHMENT REQUEST message.
  • FIG. 3 is a sequence diagram for explaining an example (1) of operations related to network slicing in the embodiment of the present invention.
  • the AMF 30A transmits Registration Accept to the UE 20.
  • Registration Accept includes Configured NSSAI and associated timer T1.
  • the UE 20 stores the Configured NSSAI in the NSSAI storage.
  • the Configured NSSAI and the associated timer T1 may be set in the UE by a pre-configuration or configuration update command instead of the Registration Accept message.
  • the timer T1 may be a timer value.
  • step S13 the UE 20 transmits Registration Complete to the AMF 30A.
  • step S14a and S14b the UE 20 and AMF 30A start a timer T1.
  • step S15 the UE 20 and the AMF 30A use the network slice identified by the Configured NSSAI until the timer T1 expires.
  • the timing of starting the timer count in step S14a and step S14b may be determined. Further, in step S14a and step S14b, the behavior when the S-NSSAI is NSSAA dependent (subject to NSSAA (Network Slice-Specific Authentication and Authorization)) may be determined. Further, regarding the timer count, the behavior may be determined depending on the timer value. Further, when the timer expires, not only the network slice is terminated, but also an alternative network slice may be notified. When notifying an alternative network slice, simultaneous registration requests from multiple UEs to the alternative network slice may be avoided. Furthermore, the behavior when a new timer value is received while the timer is activated may be determined. Further, the operation after the timer count expires may be determined. It may also determine the behavior of the wireless network when the time-limited network slice expires.
  • NSSAA Network Slice-Specific Authentication and Authorization
  • FIG. 4 is a flowchart for explaining an example (1-1) of terminal operation related to network slice in the embodiment of the present invention.
  • the UE 20 receives the Configured NSSAI (S-NSSAI) and the associated timer T1.
  • the Configured NSSAI (S-NSSAI(s)) and the associated timer T1 may be received or configured in a registration procedure, preconfiguration, or configuration update command.
  • the UE 20 starts a timer T1.
  • the UE 20 may transmit a NAS message if the timer T1 has not expired, or stop the timer T1 and start the timer T2 if a new timer T2 associated with the S-NSSAI is received. You may.
  • step S104 when the timer T1 expires, the UE 20 may suppress the transmission of the NAS message using the S-NSSAI associated with the timer T1, or save the S-NSSAI as an Allowed NSSAI. If the S-NSSAI is saved as an Allowed NSSAI, the S-NSSAI may be deleted from the Allowed NSSAI, or if the S-NSSAI is saved as an Allowed NSSAI, the S-NSSAI may be moved to the Rejected NSSAI in the NSSAI storage. Note that the NAS message using the S-NSSAI may be a NAS message that includes the S-NSSAI.
  • FIG. 5 is a flowchart for explaining an example (1-2) of terminal operation related to network slice in the embodiment of the present invention.
  • the UE 20 receives the Configured NSSAI (S-NSSAI) and the associated timer T1.
  • the Configured NSSAI (S-NSSAI(s)) and the associated timer T1 may be received or configured in a registration procedure, preconfiguration, or configuration update command.
  • the UE 20 does not need to start the timer T1.
  • the UE 20 receives the Allowed NSSAI.
  • the Allowed NSSAI may be received or set using a registration procedure or a settings update command.
  • step S113 if the S-NSSAI based on the Configured NSSAI is the Allowed NSSAI, the UE 20 may store the S-NSSAI in the Allowed NSSAI of the NSSAI storage and start the timer T1. Further, when the UE 20 takes the time from the time when it receives the Configured NSSAI to the time when it receives the Allowed NSSAI or stores the S-NSSAI in the Allowed NSSAI as t, and the start value of the timer T1 is t1, The value t1-t may be used as the starting value of the timer T1.
  • the UE 20 may delete the S-NSSAI from the Allowed NSSAI, or delete the S-NSSAI from the Rejected NSSAI of the NSSAI storage. You may move to
  • step S114 the UE 20 may transmit a NAS message if the timer T1 has not expired, or stop the timer T1 and start the timer T2 if a new timer T2 associated with the S-NSSAI is received. You may.
  • step S115 when the timer T1 expires, the UE 20 may suppress the transmission of the NAS message using the S-NSSAI to which the timer T1 is associated, or may save the S-NSSAI as an Allowed NSSAI.
  • the S-NSSAI may be deleted from the Allowed NSSAI, or if the S-NSSAI is saved as an Allowed NSSAI, the S-NSSAI may be moved to the Rejected NSSAI in the NSSAI storage.
  • the NAS message using the S-NSSAI may be a NAS message that includes the S-NSSAI.
  • FIG. 6 is a flowchart for explaining an example (1-3) of terminal operation related to network slice in the embodiment of the present invention.
  • the UE 20 receives the Configured NSSAI (S-NSSAI) and the associated timer T1.
  • the Configured NSSAI (S-NSSAI(s)) and the associated timer T1 may be received or configured in a registration procedure, preconfiguration, or configuration update command.
  • the UE 20 may ignore the timer T1 if the timer value of the timer T1 is "0" or “Deactivated", or if the timer is counting, the UE 20 may stop the timer and set the relevant S-NSSAI. It may be assumed that the time-limiting nature of the identified network slice has been removed, stopped, or lifted. Furthermore, if the timer value of timer T1 is "Activated", the UE 20 may restart the counting of the timer T1, or if there is a timer whose timer counting is stopped, the UE 20 may subtract the elapsed time from the time when the timer was stopped.
  • the remaining timer value may be set in the timer and counting may be started, or if there is a timer whose timer counting is stopped, the remaining timer value at the time of stopping may be set in the timer and counting may be started. Further, when the timer value of the timer T1 is a value other than 0, the UE 20 may perform the operation shown in FIG. 4 or FIG. 5.
  • FIG. 7 is a flowchart for explaining an example (1-4) of terminal operation related to network slice in the embodiment of the present invention.
  • the UE 20 receives the Configured NSSAI (S-NSSAI) and the associated timer T1.
  • the Configured NSSAI (S-NSSAI(s)) and associated timer T1 may be received or configured in a registration procedure, preconfiguration, or configuration update command.
  • step S132 if the timer T1 is associated with one or more S-NSSAIs, the UE 20 may start counting the timer T1 in association with multiple S-NSSAIs at the same time. Also, for example, when timer T1 is specified as "all" instead of being associated with a specific S-NSSAI, timer T1 sets the same timer value for all S-NSSAIs included in the Configured NSSAI. may be associated.
  • FIG. 8 is a flowchart for explaining an example (1-5) of terminal operation related to network slice in the embodiment of the present invention.
  • the UE 20 receives the Configured NSSAI (S-NSSAI) and the associated timer T1.
  • the Configured NSSAI (S-NSSAI(s)) and associated timer T1 may be received or configured in a registration procedure, preconfiguration, or configuration update command.
  • the UE 20 starts a timer T1.
  • timer T1 expires.
  • the UE 20 transmits a NAS message using the default NSSAI to the core network.
  • FIG. 9 is a flowchart for explaining an example (1-1) of network operation related to network slice in the embodiment of the present invention.
  • step S1001 if one network slice (identified by NSI) can be identified by multiple S-NSSAIs, and if a time limit (with expiration date setting) is set for the network slice, the network slice is The associated timer expires.
  • the timer may be a timer started by the network, and if there are multiple UEs connected to the network using the network slice, the timer count may be started with a different timer value for each UE.
  • the AMF 30A transmits to the UE a new Configured NSSAI in which all S-NSSAIs identifying the network slice registered in the subscriber information of the UE 20 are deleted.
  • the timing of transmitting a new Configured NSSAI to the UE may be based on a timer with a different timer value for each UE. By using a timer with a different timer value for each UE, when the timer expires, a new Configured NSSAI can be transmitted at different timing for each UE.
  • FIG. 10 is a flowchart for explaining an example (1-2) of network operation related to network slice in the embodiment of the present invention.
  • step S1011 if one network slice (identified by NSI (Network Slice Instance)) can be identified by multiple S-NSSAIs, and if a time limit (with an expiration date set) is set for the S-NSSAIs , the timer associated with the S-NSSAI expires.
  • the timer may be a timer started by the network, and if there are multiple UEs connected to the network using the S-NSSAI, the timer count may be started with a different timer value for each UE. .
  • the AMF 30A transmits to the UE a notification that the S-NSSAI is a Rejected NSSAI, and a Configured NSSAI or Allowed NSSAI that includes an alternative S-NSSAI of the network slice identified by the S-NSSAI.
  • the timing of transmitting the alternative S-NSSAI to the UE may be based on a timer with a different timer value for each UE. By starting a timer with a different timer value for each UE, when the timer expires, a substitute S-NSSAI can be transmitted to the UE at a different timing for each UE.
  • FIG. 11 is a flowchart for explaining an example (1-3) of network operation related to network slice in the embodiment of the present invention.
  • step S1021 if multiple network slices (identified by NSI) can be identified with one S-NSSAI, and if a time limit (with expiration date setting) is set for the network slice, it is associated with the network slice. The specified timer expires.
  • the AMF 30A transmits a notification indicating that the S-NSSAI is a Rejected NSSAI. Furthermore, the mapping between network slices and S-NSSAI held in the core network is updated. For example, among the network slices identified by the S-NSSAI, mapping with a network slice whose timer has expired may be canceled and mapping may be switched to a network slice whose timer has not expired.
  • FIG. 12 is a flowchart for explaining an example (1-4) of network operation related to network slice in the embodiment of the present invention.
  • step S1031 if multiple network slices (identified by NSI) can be identified with one S-NSSAI, and if a time limit (with expiration date setting) is set for the S-NSSAI, the S-NSSAI The timer associated with NSSAI expires.
  • the timer may be a timer started by the network, and if there are multiple UEs connected to the network using the S-NSSAI, the timer count may be started with a different timer value for each UE. .
  • the AMF 30A transmits to the UE a new Configured NSSAI in which the S-NSSAI that identifies the network slice registered in the UE's subscriber information is deleted.
  • the timing of transmitting the new Configured NSSAI to the UE may be based on a timer with a different timer value for each UE. By using a timer with a different timer value for each UE, when the timer expires, a new Configured NSSAI can be transmitted at different timing for each UE.
  • FIG. 13 is a flowchart for explaining an example (1-5) of network operations related to network slices in the embodiment of the present invention.
  • step S1041 cell #A, cell #B, and cell #C are configured in a certain TA, and a network slice identified by S-NSSAI #1 and a network slice identified by S-NSSAI #2 are configured in the TA. be done. Radio resources are allocated to S-NSSAI #1 and S-NSSAI #2 in cell #A and cell #B in a prioritized or dedicated manner. Radio resources are shared with S-NSSAI #1 and S-NSSAI #2 in cell #C.
  • the wireless network terminates the time-limited network slice identified by S-NSSAI#2. from the core network or management function.
  • the wireless network determines the allocation of wireless resources based on the notification or the information. For example, S-NSSAI #2 may be deleted from shared radio resource usage in cell #C.
  • the management function may be a function that performs service management and/or orchestration.
  • RRM radio resource management
  • the member list includes a PLMNid and/or S-NSSAI, and may be associated with a preferential/exclusive or shared resource allocation group.
  • S-NSSAI #2 associated with the shared resource allocation group of the RRM policy is deleted from the member list of the RRM policy.
  • FIG. 14 is a flowchart for explaining an example (1-6) of network operations related to network slices in the embodiment of the present invention.
  • step S1051 cell #A, cell #B, and cell #C are configured in a certain TA, and a network slice identified by S-NSSAI #1 and a network slice identified by S-NSSAI #2 are configured in the TA. be done.
  • Radio resources are allocated to S-NSSAI #1 and S-NSSAI #2 in cell #A and cell #B in a prioritized or dedicated manner.
  • Wireless resources are allocated to S-NSSAI #1 and S-NSSAI #2 in cell #C in a shared manner.
  • step S1052 when the time-limited network slice identified by S-NSSAI #2 is terminated, the core network terminates the time-limited network slice identified by S-NSSAI #2. to the management function.
  • the management function determines radio resource allocation based on the notification or the information. For example, S-NSSAI #2 may be deleted from shared radio resource usage in cell #C. Note that the management function may be a function that performs service management and/or orchestration.
  • allocation of preferential/dedicated or shared radio resources managed by the RRM policy may be performed based on a member list (rRMPolicyMemberList).
  • the member list includes a PLMNid and/or S-NSSAI, and may be associated with a preferential/exclusive or shared resource allocation group.
  • S-NSSAI #2 associated with the shared resource allocation group of the RRM policy is deleted from the member list of the RRM policy. You can.
  • the management function may configure radio resources of the wireless network based on the RRM policy.
  • FIG. 15 is a sequence diagram for explaining an example (2) of operation related to network slicing in the embodiment of the present invention.
  • the UE 20 transmits a Registration Request to the AMF 30A.
  • the AMF 30A sends to the UE 20 a Registration Accept that includes one or more conditional S-NSSAIs and an associated validity timer as a conditionally allowed NSSAI. Send.
  • conditional here we refer to the conditional "Allowed" NSSAI, but this does not mean that whether it is Allowed (whether or not use is permitted) is based on the associated conditions. good.
  • conditional may mean that it can be used if a condition is met.
  • condition may indicate whether or not a network slice can be used at a specific time (or time frame).
  • conditional Allowed NSSAI and the associated validity timer may be configured in the UE by a preconfiguration or configuration update command instead of the Registration Accept message.
  • conditionally Allowed NSSAI may be an Extended Allowed NSSAI, a Pending NSSAI, or a conditional S-N that is neither Allowed NSSAI nor Pending NSSAI nor Rejected NSSAI.
  • Dedicated NSSAI to hold SSAI It may be.
  • step S23 the UE 20 starts the validity timer when receiving the Allowed NSSAI including the validity timer for S-NSSAI corresponding to a certain temporary network slice.
  • step S24 when the validity timer expires, the UE 20 deletes the S-NSSAI from the Allowed NSSAI list and releases the PDU session associated with the S-NSSAI.
  • the UE behavior upon receiving the conditional Allowed NSSAI may be determined. Further, regarding the timer count, the activation behavior may be determined according to the timer value. Further, the operation may be determined when a new timer value is received while the timer is activated. Further, the operation after the timer count expires may be determined. Additionally, wireless network behavior upon expiration of a time-limited network slice may be determined.
  • FIG. 16 is a flowchart for explaining an example (2-1) of terminal operation related to network slice in the embodiment of the present invention.
  • the UE 20 receives an S-NSSAI identifying a time-limited network slice from the core network as a conditionally Allowed NSSAI. Further, the S-NSSAI may be associated with a timer indicating time-limitedness or validity.
  • the S-NSSAI as the conditionally Allowed NSSAI that the UE 20 receives does not have to be received while being included in the Allowed NSSAI IE (Information Element).
  • the UE 20 may receive a dedicated IE that includes the S-NSSAI of the conditionally Allowed NSSAI, which is different from the Allowed NSSAI IE.
  • the dedicated IE includes one or more conditional S-NSSAIs and may further have an associated timer to indicate time-limiting or validity.
  • the S-NSSAI of the conditionally Allowed NSSAI that the UE 20 receives may be the S-NSSAI of HPLMN.
  • the S-NSSAI with which the timer is associated may be one or more mapped S-NSSAIs of the Conditional Allowed NSSAI (HPLMN's S-NSSAI) rather than the Allowed NSSAI (Serving S-NSSAI). It's fine.
  • the dedicated IE that includes the conditional Allowed NSSAI is configured to connect the Allowed NSSAI and/or one or more mapped S-NSSAIs of the Allowed NSSAI (HPLMN's S-NSSAI) and the one or more mapped S-NSSAIs of the Allowed NSSAI. It may consist of a combination of timers associated with the S-NSSAI.
  • one conditional Allowed NSSAI (one conditional S-NSSAI) has multiple mapped S-NSSAIs (HPLMN's S-NSSAI), and the time limits of the multiple mapped S-NSSAIs are the same. If so, the core network may configure a dedicated IE by associating the plurality of mapped S-NSSAIs with one timer.
  • the core network may configure a dedicated IE by associating the mapped S-NSSAI for each timer.
  • step S202 the UE 20 starts the timer.
  • step S203 the UE 20 may transmit a NAS message if the timer has not expired, or may stop the timer and start a new timer if it receives a new timer associated with the S-NSSAI. Good too.
  • step S204 the UE 20 may suppress transmission of the NAS message if the validity timer expires.
  • FIG. 17A is a flowchart illustrating an example (2-2) of terminal operation related to network slice upon receiving Configured NSSAI in the embodiment of the present invention.
  • the S-NSSAI may be maintained or stored in NSSAI storage.
  • step S211A the UE 20 holds the conditionally Allowed NSSAI in the NSSAI storage.
  • step S212A when the UE 20 receives a new Configured NSSAI, if one or more S-NSSAI held as a conditionally Allowed NSSAI is included in the received Configured NSSAI, the UE 20 may be removed from the conditionally Allowed NSSAI. Furthermore, at the same time, the timer associated with the one or more S-NSSAIs may also be deleted.
  • FIG. 17B is a flowchart for explaining an example (2-2) of terminal operation related to network slice when receiving Allowed NSSAI in the embodiment of the present invention.
  • the S-NSSAI may be maintained or stored in NSSAI storage.
  • step S211B the UE 20 holds the conditionally Allowed NSSAI in the NSSAI storage. Furthermore, the UE 20 holds one or more conditional S-NSSAIs included in the conditional Allowed NSSAI as Allowed NSSAIs.
  • step S212B the UE 20 may hold the S-NSSAI as a conditionally allowed NSSAI in the NSSAI storage until the timer associated with the one or more S-NSSAIs that are held as the conditionally allowed NSSAI expires. When the timer expires, the UE 20 may delete the one or more conditional S-NSSAIs from the Allowed NSSAIs.
  • FIG. 17C is a flowchart illustrating an example (2-2) of terminal operation related to network slicing when a conditional Allowed NSSAI is received in the embodiment of the present invention.
  • the S-NSSAI may be maintained or stored in NSSAI storage.
  • step S211C the UE 20 holds the conditionally Allowed NSSAI in the NSSAI storage. Furthermore, the UE 20 receives one or more new conditional Allowed NSSAIs and a timer associated with the conditional Allowed NSSAIs.
  • the UE 20 may replace any held conditional Allowed NSSAI with the received conditional Allowed NSSAI. More specifically, the UE 20 selects all (any) conditional Allowed NSSAIs of the PLMN, SNPN (Standalone Non-Public Network), or equivalent PLMN (Standalone Non-Public Network) to which the UE 20 is connected, among the conditional Allowed NSSAIs it holds.
  • the Allowed NSSAI may be replaced with the conditional Allowed NSSAI of the PLMN, SNPN (Standalone Non-Public Network), or equivalent PLMN (equivalent) that received the Allowed NSSAI.
  • step S213C the UE 20 may delete any timer associated with the conditional Allowed NSSAI replaced in step S212C. Furthermore, the UE 20 may maintain a timer associated with the received conditional Allowed NSSAI.
  • FIG. 17D is a flowchart for explaining an example (2-2) of terminal operation related to a network slice that has received a configuration update command in which a registration request has been set according to the embodiment of the present invention.
  • the S-NSSAI may be maintained or stored in NSSAI storage.
  • step S211D the UE 20 holds a conditional Allowed NSSAI and a timer associated with the conditional Allowed NSSAI.
  • step S212D the UE 20 receives the configuration update command.
  • the Configuration update indication IE included in the configuration update command is set to "registration requested" but does not include configuration update information regarding the network slice, all (any) conditional Allowed NSSAI held and the timer associated with the conditional Allowed NSSAI.
  • FIG. 18 is a flowchart for explaining an example (2-3) of terminal operation related to network slicing in the embodiment of the present invention.
  • the UE 20 receives an S-NSSAI identifying a time-limited network slice from the core network as a conditionally Allowed NSSAI. Additionally, a validity timer may be associated with the S-NSSAI.
  • the UE 20 may ignore the validity timer if the timer value of the validity timer is "0" or "Deactivated", or if the timer is counting, the UE 20 stops the validity timer and It may be assumed that the time-limiting nature of the network slice identified by the S-NSSAI has been removed, stopped, or lifted. Further, when the timer value of the validity timer is "Activated", the UE 20 may restart counting of the validity timer, or if there is a validity timer whose timer count is stopped, the UE 20 may restart counting of the validity timer.
  • the UE 20 may perform the operations shown in FIG. 16 or FIGS. 17A to 17D.
  • FIG. 19 is a flowchart for explaining an example (2-4) of terminal operation related to network slicing in the embodiment of the present invention.
  • the UE 20 receives an S-NSSAI identifying a time-limited network slice from the core network as a conditionally Allowed NSSAI. Additionally, a validity timer may be associated with the S-NSSAI.
  • the UE 20 starts a validity timer.
  • the validity timer expires.
  • the UE 20 transmits a NAS message using the default NSSAI to the core network.
  • the default S-NSSAI does not need to be associated with a timer associated with a time-limited network slice. Note that the behavior of the UE 20 when the timer associated with the time-limited network slice expires does not need to be limited to this.
  • FIG. 20 is a flowchart for explaining an example (2-1) of network operation related to network slice in the embodiment of the present invention.
  • step S2001 if the AMF 30A does not receive from the UE 20 the UE capability indicating that it supports the time-limited network slice usage function in the registration request, the AMF 30A performs any one or more of the following operations 1) to 4). You may.
  • the AMF 30A when the AMF 30A receives from the UE 20 a UE capability indicating that it supports the time-limited network slice usage function in the registration request, it allows the UE to use the time-limited network slice.
  • the notification to the UE may be made in response to the registration request (registration permission), or may be made in the form of a settings update command.
  • the operation shown in FIG. 20 shows the behavior when using time-limited network slices as an option for operator network operation, assuming that the UE 20 supports the relevant capability. In all cases, when using time-limited network slices, This does not indicate that the UE's support for this capability is mandatory.
  • FIG. 21 is a flowchart for explaining an example (2-2) of network operation related to network slice in the embodiment of the present invention.
  • step S2011 cell #A, cell #B, and cell #C are configured in a certain TA, and a network slice identified by S-NSSAI #1 and a network slice identified by S-NSSAI #2 are configured in the TA. be done.
  • Radio resources are allocated to S-NSSAI #1 and S-NSSAI #2 in cell #A and cell #B in a prioritized or dedicated manner.
  • Wireless resources are allocated to S-NSSAI #1 and S-NSSAI #2 in cell #C in a shared manner.
  • step S2012 when the time-limited network slice identified by S-NSSAI #2 is terminated, the wireless network sends a notification or information regarding the termination of the time-limited network slice identified by S-NSSAI #2.
  • the management function may be a function that performs service management and/or orchestration.
  • step S2013 the wireless network determines the allocation of wireless resources based on the notification or the information. For example, S-NSSAI #2 may be deleted from shared radio resource usage in cell #C.
  • allocation of preferential/dedicated or shared radio resources managed by the RRM policy may be performed based on a member list (rRMPolicyMemberList).
  • the member list includes a PLMNid and/or S-NSSAI, and may be associated with a preferential/exclusive or shared resource allocation group.
  • S-NSSAI #2 associated with the shared resource allocation group of the RRM policy is deleted from the member list of the RRM policy. You can.
  • the above-mentioned RRM policy management may be performed by the management function with the wireless network as the management target, or may be performed by the wireless network itself.
  • FIG. 22 is a flowchart for explaining an example (2-3) of network operations related to network slices in the embodiment of the present invention.
  • step S2021 cell #A, cell #B, and cell #C are configured in a certain TA, and a network slice identified by S-NSSAI #1 and a network slice identified by S-NSSAI #2 are configured in the TA. be done.
  • Radio resources are allocated to S-NSSAI #1 and S-NSSAI #2 in cell #A and cell #B in a prioritized or dedicated manner.
  • Wireless resources are allocated to S-NSSAI #1 and S-NSSAI #2 in cell #C in a shared manner.
  • step S2022 when the time-limited network slice identified by S-NSSAI #2 is terminated, the core network sends a notification or information regarding the termination of the time-limited network slice identified by S-NSSAI #2. Send to management function.
  • the management function may be a function that performs service management and/or orchestration.
  • step S2023 the management function determines the allocation of radio resources based on the notification or the information. For example, S-NSSAI #2 may be deleted from shared radio resource usage in cell #C.
  • allocation of preferential/dedicated or shared radio resources managed by the RRM policy may be performed based on a member list (rRMPolicyMemberList).
  • the member list includes a PLMNid and/or S-NSSAI, and may be associated with a preferential/exclusive or shared resource allocation group.
  • S-NSSAI #2 associated with the shared resource allocation group of the RRM policy is deleted from the member list of the RRM policy. You can.
  • the management function may configure radio resources of the wireless network based on the RRM policy.
  • FIG. 23 is a sequence diagram for explaining an example (3) of operation related to network slicing in the embodiment of the present invention.
  • the UE 20 determines whether to perform a PDU session establishment procedure based on the URSP (UE Route Selection Policy). If the execution determination is true, the process advances to step S32 and the PDU session establishment procedure is executed. If the implementation determination is false, the PDU session establishment procedure is not performed.
  • URSP UE Route Selection Policy
  • the URSP Time Window cannot be set to time-limited. It has been difficult to combine network slicing with normal traffic control. Therefore, a plurality of Time Windows may be set for one network slice.
  • FIG. 24 is a flowchart for explaining an example (3-1) of terminal operation related to network slice in the embodiment of the present invention.
  • the UE 20 determines whether the Slice Validation Indication of the RSD (Route Selection Descriptor) of the URSP is true or false. If Slice Validation Indication is true, the process advances to step S302; if it is false, the process advances to step S303.
  • RSD Radio Selection Descriptor
  • step S302 the UE 20 determines whether the current time is within the Time Window time frame of the Route Selection Validation Criteria (route selection validation conditions). If it is within the time frame (YES in S302), the process advances to step S303, and if it is outside the time frame (NO in S302), the flow is ended. In step S303, the UE 20 transmits a PDU session establishment request to the network.
  • Route Selection Validation Criteria route selection validation conditions
  • the UE 20 that performs the operation shown in FIG. 24 may decide whether to perform the PDU session establishment procedure during the PDU session establishment procedure or when the validity of the rule defined by the URSP changes. Alternatively, changes in the effectiveness of the rules defined by the URSP may be constantly monitored.
  • the Time W of the Route Selection Validation Criteria is Check the indow information.
  • the Time Window information is composed of information indicating a start time and a stop time (for convenience, the period from the start time to the stop time is referred to as a time frame). If the time for transmitting the PDU session establishment request is within the Time Window, the UE 20 may transmit the PDU session establishment request.
  • the UE 20 may determine in advance that the execution determination of the PDU session establishment procedure is false if the current time has passed the time frame defined by the Time Window information of the Route Selection Validation Criteria of the RSD of the URSP. In other words, the UE 20 recognizes that the validity of the rules defined by the URSP has changed as the time frame defined by the Time Window information of the Route Selection Validation Criteria of the RSD of the URSP has passed, and performs the PDU session establishment procedure in advance. The determination may be determined as false. Note that the UE 20 that has determined that the execution determination of the PDU session establishment procedure is false may notify the upper layer that the PDU session cannot be established using the network slice.
  • the UE may monitor at any timing whether the current time has passed the time frame defined by the Time Window information of the Route Selection Validation Criteria of the RSD of the URSP.
  • the UE 20 that has determined that the execution determination of the PDU session establishment procedure is false may notify the upper layer that the PDU session cannot be established using the network slice.
  • FIG. 25 is a flowchart for explaining an example (3-2) of terminal operation related to network slicing in the embodiment of the present invention.
  • the UE 20 determines whether the current time is within the time frame of the Time Window of the Slice Selection Validation Criteria (slice selection validation conditions) of the RSD of the URSP. If it is within the time frame (YES in S311), the process advances to step S312, and if it is outside the time frame (NO in S311), the flow is ended.
  • the UE 20 transmits a PDU session establishment request to the network.
  • the UE 20 that performs the operation shown in FIG. 25 may decide whether to perform the PDU session establishment procedure during the PDU session establishment procedure or when the validity of the rule defined by the URSP changes. Alternatively, changes in the effectiveness of the rules defined by the URSP may be constantly monitored.
  • the UE 20 when it transmits a PDU session establishment request to the core network, it checks the Time Window information of the Slice Selection Validation Criteria of the RSD of the URSP.
  • the Time Window information is composed of information indicating a start time and a stop time (for convenience, the period from the start time to the stop time is referred to as a time frame). If the time for transmitting the PDU session establishment request is within the Time Window, the UE 20 may transmit the PDU session establishment request.
  • the Slice Selection Validation Criteria may be information set in the URSP separately from the Route Selection Validation Criteria. Time Window information is set in the Slice Selection Validation Criteria, and may be used, for example, to determine the implementation of a PDU session establishment procedure using a timed network slice.
  • the UE 20 may determine in advance that the execution determination of the PDU session establishment procedure is false if the current time has passed the time frame defined by the Time Window information of the Slice Selection Validation Criteria of the RSD of the URSP. In other words, the UE 20 recognizes that the validity of the rules defined by the URSP has changed as the time frame defined by the Time Window information of the URSP's RSD Slice Selection Validation Criteria has passed, and performs the PDU session establishment procedure in advance. The determination may be determined as false. Note that the UE 20 that has determined that the execution determination of the PDU session establishment procedure is false may notify the upper layer that the PDU session cannot be established using the network slice.
  • the UE may monitor at any timing whether the current time has passed the time frame defined by the Time Window information of the Slice Selection Validation Criteria of the RSD of the URSP.
  • the UE may monitor at any timing whether the current time has passed the time frame defined by the Time Window information of the Slice Selection Validation Criteria of the RSD of the URSP.
  • the UE may notify the upper layer that the PDU session cannot be established using the network slice.
  • URSP is a policy used by the UE to determine how to route traffic.
  • the UE 20 may check the URSP when establishing a new PDU session, or may check the URSP for routing an established PDU session.
  • the URSP may include the above-mentioned Time Window information.
  • the core network can provide timed network slices to the UE based on a timer or URSP.
  • a time-limited network slice service can be provided in a communication system.
  • 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. 26 is a diagram illustrating 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. 26 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. 27 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. 27 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.
  • 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. 28 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. 26 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. 27 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, for example, a network device, network controller, network card, communication module, etc.
  • 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 transmitter/receiver may be physically or logically separated into a transmitter and a receiver.
  • 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. 29 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.
  • a receiving unit that receives information identifying a network slice and a timer value associated with the network slice from a core network, information identifying the network slice, and a timer value associated with the network slice.
  • a controller that starts a timer for setting the timer value when the timer value is received;
  • a terminal is provided that suppresses transmission of NAS (Non-Access Stratum) messages.
  • the core network can provide timed network slices to the UE based on a timer or URSP. That is, a time-limited network slice service can be provided in a communication system.
  • the control unit If the control unit receives another timer value associated with the same network slice as the network slice while the timer is operating, the control unit stops the timer and starts a timer that sets the other timer value. You can. With this configuration, the core network can provide timed network slices to the UE based on a timer or URSP.
  • the receiving unit further receives information identifying a permitted network slice, including information identifying the network slice, and the control unit determines when the information identifying the network slice and the timer value are received.
  • a timer may be started for setting a value obtained by subtracting an elapsed time from the time when the information identifying the permitted network slice is received from the timer value.
  • the receiving unit may receive information identifying a network slice to replace the network slice when the timer expires, and the control unit may execute a registration request procedure using the replacement network slice. good.
  • the core network can provide timed network slices to the UE based on a timer or URSP.
  • the control unit determines whether the current time is included in a time frame included in the information for routing traffic, and if the current time is included in the time frame, executes a PDU (Protocol Data Unit) session establishment procedure. You may.
  • the core network can provide timed network slices to the UE based on a timer or URSP.
  • the transmitting unit transmits information identifying a network slice and a timer value associated with the network slice to a terminal; and a control unit that starts a timer that sets the timer value, and the transmitter includes information identifying a network slice to replace the network slice and information for identifying the network slice to replace the network slice when the timer expires.
  • a network node is provided that transmits associated timer values to different terminals at different times.
  • the core network can provide timed network slices to the UE based on a timer or URSP. That is, a time-limited network slice service can be provided in a communication system.
  • 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 or S-GW possibly, but not limited to
  • 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 body 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.
  • 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 2025 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)

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un terminal comprenant : une unité de réception qui reçoit, d'un réseau central, des informations permettant d'identifier une tranche de réseau et une valeur de minuterie associée à la tranche de réseau ; et une unité de commande qui démarre, lors de la réception de la valeur de minuterie et des informations permettant d'identifier la tranche de réseau, une minuterie réglée sur la valeur de minuterie. L'unité de commande supprime la transmission des messages de strate de non-accès (NAS) au réseau central en utilisant les informations d'identification de la tranche de réseau si la minuterie a expiré.
PCT/JP2022/029711 2022-08-02 2022-08-02 Terminal et nœud de réseau WO2024028992A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2022/029711 WO2024028992A1 (fr) 2022-08-02 2022-08-02 Terminal et nœud de réseau

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2022/029711 WO2024028992A1 (fr) 2022-08-02 2022-08-02 Terminal et nœud de réseau

Publications (1)

Publication Number Publication Date
WO2024028992A1 true WO2024028992A1 (fr) 2024-02-08

Family

ID=89848730

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2022/029711 WO2024028992A1 (fr) 2022-08-02 2022-08-02 Terminal et nœud de réseau

Country Status (1)

Country Link
WO (1) WO2024028992A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2021508217A (ja) * 2018-02-16 2021-02-25 日本電気株式会社 Ｎｇ−ｒａｎノード、ｕｅ、ｎｇ−ｒａｎノードの方法、及びｕｅの方法

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2021508217A (ja) * 2018-02-16 2021-02-25 日本電気株式会社 Ｎｇ−ｒａｎノード、ｕｅ、ｎｇ−ｒａｎノードの方法、及びｕｅの方法
JP2021180523A (ja) * 2018-02-16 2021-11-18 日本電気株式会社 Ｎｏｎ−３ＧＰＰ ＩｎｔｅｒＷｏｒｋｉｎｇ Ｆｕｎｃｔｉｏｎノード、ＵＥ、Ｎｏｎ−３ＧＰＰ ＩｎｔｅｒＷｏｒｋｉｎｇ Ｆｕｎｃｔｉｏｎノードの方法、及びＵＥの方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: "Discussion on Slice-Specific Secondary Authentication and Authorization", 3GPP TSG CT WG1 #114 C1-190236, 14 January 2019 (2019-01-14), XP051572927 *

Similar Documents

Publication Publication Date Title
WO2024028992A1 (fr) Terminal et nœud de réseau
WO2024034073A1 (fr) Terminal et procédé de communication
WO2023195370A1 (fr) Nœud de réseau et procédé de communication
WO2023218670A1 (fr) Nœud de réseau et procédé de communication
WO2023067814A1 (fr) Nœud de réseau et procédé de communication
WO2024034074A1 (fr) Nœud de réseau, système de réseau central et procédé de commande
WO2023218671A1 (fr) Nœud de réseau et procédé de communication
WO2024134850A1 (fr) Noeud de réseau et procédé de communication
WO2023214456A1 (fr) Nœud de réseau, et procédé de communication
WO2023223511A1 (fr) Nœud de réseau et procédé de communication
WO2023067815A1 (fr) Nœud de réseau et procédé de communication
WO2024038488A1 (fr) Terminal et procédé de communication
WO2023218509A1 (fr) Nœud de réseau, système de communication sans fil, et procédé de communication
WO2024034075A1 (fr) Station de base, terminal, nœud de réseau et procédé de communication
WO2023175969A1 (fr) Dispositif de réseau et station de base radio
WO2023223512A1 (fr) Nœud de réseau et procédé de communication
WO2023119386A1 (fr) Nœud de réseau
WO2024034022A1 (fr) Terminal, nœud de réseau, et procédé de communication
WO2024057550A1 (fr) Nœud réseau, système de communication, et procédé de communication
WO2024004156A1 (fr) Nœud de réseau, station de base et procédé de communication
WO2023188038A1 (fr) Station radio fixe et procédé de radiocommunication
WO2024062583A1 (fr) Nœud de réseau et procédé de communication
WO2024034135A1 (fr) Nœud de réseau et procédé d'autorisation
WO2023119385A1 (fr) Nœud de réseau
WO2024057549A1 (fr) Nœud de réseau et procédé de communication

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: 22953981

Country of ref document: EP

Kind code of ref document: A1