WO2022025666A1 - 네트워크 슬라이스의 동시 사용 방법 및 장치 - Google Patents

네트워크 슬라이스의 동시 사용 방법 및 장치 Download PDF

Info

Publication number
WO2022025666A1
WO2022025666A1 PCT/KR2021/009879 KR2021009879W WO2022025666A1 WO 2022025666 A1 WO2022025666 A1 WO 2022025666A1 KR 2021009879 W KR2021009879 W KR 2021009879W WO 2022025666 A1 WO2022025666 A1 WO 2022025666A1
Authority
WO
WIPO (PCT)
Prior art keywords
network slice
terminal
network
information
nssai
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/KR2021/009879
Other languages
English (en)
French (fr)
Korean (ko)
Inventor
이호연
정상수
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Samsung Electronics Co Ltd
Original Assignee
Samsung Electronics Co Ltd
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 Samsung Electronics Co Ltd filed Critical Samsung Electronics Co Ltd
Priority to JP2023506133A priority Critical patent/JP7766077B2/ja
Priority to CN202180058469.9A priority patent/CN116058010A/zh
Priority to EP21851581.5A priority patent/EP4175367A4/en
Priority to US18/018,382 priority patent/US20230300731A1/en
Publication of WO2022025666A1 publication Critical patent/WO2022025666A1/ko
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/005—Multiple registrations, e.g. multihoming
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18—Service support devices; Network management devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/02—Inter-networking arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/04—Registration at HLR or HSS [Home Subscriber Server]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/06—Registration at serving network Location Register, VLR or user mobility server
    • H04W8/065—Registration at serving network Location Register, VLR or user mobility server involving selection of the user mobility server
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data

Definitions

  • This disclosure relates generally to wireless communication systems, and more particularly, to an apparatus and method for providing network slicing in a wireless communication system or a mobile communication system.
  • the 5G communication system or the pre-5G communication system is called a 4G network after (Beyond 4G Network) communication system or an LTE system after (Post LTE) system.
  • the 5G communication system defined by 3GPP is called the New Radio (NR) system.
  • the 5G communication system is being considered for implementation in a very high frequency (mmWave) band (eg, such as a 60 gigabyte (60 GHz) band).
  • mmWave very high frequency
  • FD-MIMO Full Dimensional MIMO
  • array antenna, analog beam-forming, and large scale antenna techniques have been discussed and applied to the NR system.
  • an evolved small cell in the 5G communication system, an evolved small cell, an advanced small cell, a cloud radio access network (cloud radio access network: cloud RAN), an ultra-dense network (ultra-dense network) , Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, Coordinated Multi-Points (CoMP), and reception interference cancellation Technology development is underway.
  • cloud radio access network cloud radio access network: cloud RAN
  • ultra-dense network ultra-dense network
  • D2D Device to Device communication
  • wireless backhaul moving network
  • cooperative communication Coordinated Multi-Points (CoMP)
  • CoMP Coordinated Multi-Points
  • ACM advanced coding modulation
  • FQAM Hybrid FSK and QAM Modulation
  • SWSC Small Cell Superposition Coding
  • FBMC Fan Bank Multi Carrier
  • NOMA non-orthogonal multiple access
  • SCMA sparse code multiple access
  • IoT Internet of Things
  • IoE Internet of Everything
  • M2M Machine Type Communication
  • MTC Machine Type Communication
  • IoT an intelligent IT (Internet Technology) service that collects and analyzes data generated from connected objects and creates new values in human life can be provided.
  • IoT is a field of smart home, smart building, smart city, smart car or connected car, smart grid, health care, smart home appliance, advanced medical service, etc. can be applied to
  • 5G communication such as sensor network, machine to machine communication (M2M), and machine type communication (MTC) is being implemented by techniques such as beam forming, MIMO, and array antenna.
  • M2M machine to machine communication
  • MTC machine type communication
  • cloud RAN cloud radio access network
  • the present disclosure provides a network slice function in a wireless communication system between a 5G network system structure (eg, 5G core (5GC) and an evolved packet system (EPS) network system)
  • 5G network system structure eg, 5G core (5GC) and an evolved packet system (EPS) network system
  • EPS evolved packet system
  • EPC evolved packet core
  • a method performed by an access and mobility function (AMF) entity includes, from a terminal, a registration request message including first information about a requested network slice. Receiving, wherein the first information indicates at least one network slice related to a packet data network (PDN) connection established by the terminal in a first network; determining, by the terminal, an allowed network slice available in a second network, based on the first information; and transmitting, to the terminal, a registration accept message including second information indicating the allowed network slice.
  • PDN packet data network
  • the method performed by the terminal includes, to an access and mobility function (AMF) entity, a registration request message including first information about the requested network slice. transmitting, wherein the first information indicates at least one network slice related to a packet data network (PDN) connection established by the terminal in a first network; and receiving, by the terminal from the AMF, a registration accept message including second information that is available in a second network and indicates an allowed network slice determined based on the first information.
  • AMF access and mobility function
  • An access and mobility function (AMF) entity for solving the above-described problem includes a transceiver configured to transmit and receive a signal; and a control unit, wherein the control unit: receives, from the terminal, a registration request message including first information about the requested network slice, wherein the first information is established by the terminal in the first network Indicate at least one network slice related to a packet data network (PDN) connection, and based on the first information, the terminal determines an allowed network slice available in a second network, and to the terminal, the allowed network slice is determined. It is configured to transmit a registration accept message including second information indicating the network slice.
  • PDN packet data network
  • a terminal for solving the above-described problems includes a transceiver configured to transmit and receive a signal; and a control unit, wherein the control unit: transmits, to an access and mobility function (AMF) entity, a registration request message including first information about the requested network slice, wherein the first information is the terminal Indicate at least one network slice related to a packet data network (PDN) connection established in the first network, and from the AMF, the terminal is available in the second network and allowed to be determined based on the first information configured to receive a registration accept message including second information indicating a network slice.
  • AMF access and mobility function
  • FIG. 1 is a diagram illustrating a configuration of a network slice IE related to an embodiment of the present disclosure.
  • FIG. 2 is a diagram illustrating a structure of network slice interworking related to an embodiment of the present disclosure.
  • FIG. 3 is a diagram illustrating a network slice selection method according to an embodiment of the present disclosure.
  • FIG. 4 is a diagram illustrating a network slice selection method according to an embodiment of the present disclosure.
  • FIG. 5 is a diagram illustrating a network slice management method according to an embodiment of the present disclosure.
  • FIG. 6 is a diagram illustrating a structure of a terminal according to an embodiment of the present disclosure.
  • FIG. 7 is a diagram illustrating a structure of a network function (NF) according to an embodiment of the present disclosure.
  • FIG. 8 is a diagram illustrating a structure of a base station according to an embodiment of the present disclosure.
  • each block of the flowchart diagrams and combinations of the flowchart diagrams may be performed by computer program instructions.
  • These computer program instructions may be embodied in a processor of a general purpose computer, special purpose computer, or other programmable data processing equipment, such that the instructions performed by the processor of the computer or other programmable data processing equipment are not described in the flowchart block(s). It creates a means to perform functions.
  • These computer program instructions may also be stored in a computer-usable or computer-readable memory that may direct a computer or other programmable data processing equipment to implement a function in a particular manner, and thus the computer-usable or computer-readable memory.
  • the instructions stored in the flow chart block(s) produce an article of manufacture containing instruction means for performing the function described in the flowchart block(s).
  • the computer program instructions may also be mounted on a computer or other programmable data processing equipment, such that a series of operational steps are performed on the computer or other programmable data processing equipment to create a computer-executed process to create a computer or other programmable data processing equipment. It is also possible that instructions for performing the processing equipment provide steps for performing the functions described in the flowchart block(s).
  • each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s). It should also be noted that in some alternative implementations it is also possible for the functions recited in blocks to occur out of order. For example, two blocks shown one after another may be performed substantially simultaneously, or the blocks may sometimes be performed in the reverse order according to a corresponding function.
  • ' ⁇ unit' used in this embodiment means software or hardware components such as field programmable gate array (FPGA) or ASIC (application specific integrated circuit), and ' ⁇ unit' refers to what roles carry out
  • '-part' is not limited to software or hardware.
  • ' ⁇ ' may be configured to reside on an addressable storage medium or may be configured to refresh one or more processors. Accordingly, as an example, ' ⁇ ' indicates components such as software components, object-oriented software components, class components, and task components, and processes, functions, properties, and procedures. , subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables.
  • components and ' ⁇ units' may be combined into a smaller number of components and ' ⁇ units' or further separated into additional components and ' ⁇ units'.
  • components and ' ⁇ units' may be implemented to play one or more CPUs in a device or secure multimedia card.
  • the present disclosure discloses an apparatus and method for providing interworking of a network slice (or network slicing) in a wireless communication system. Specifically, a technology for interworking between a 5G network system structure that provides a network slice function in a wireless communication system and an EPS network system will be described through the present disclosure.
  • Reference terms and the like are exemplified for convenience of description. Accordingly, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meanings may be used.
  • the 3GPP standard standardized the 5G network system architecture and procedures.
  • Mobile operators can provide various services in the 5G network.
  • mobile communication operators need to satisfy different service requirements for each service (eg, delay time, communication range, data rate, bandwidth, reliability, etc.).
  • the mobile communication operator may configure a network slice and allocate network resources suitable for a specific service for each network slice or for each set of network slices.
  • the network resource may mean NF or logical resources provided by the NF or radio resource allocation of a base station.
  • a mobile communication operator may configure network slice A to provide mobile broadband service, configure network slice B to provide vehicle communication service, and configure network slice C to provide IoT service. That is, in this 5G network, a corresponding service can be efficiently provided to a terminal through a network slice specialized for the characteristics of each service.
  • FIG. 1 is a diagram illustrating a configuration of a network slice IE related to an embodiment of the present disclosure.
  • S-NSSAI Single-Network Slice Selection Assistance Information
  • 3GPP may be used as a delimiter for classifying network slices.
  • 1 shows an example of such an S-NSSAI IE (Information Element) configuration.
  • SST Slice/Service Type, 116 used in HPLMN (Home PLMN: Home Public Land Mobile Network)
  • SD Silicon Differentiator, 118 used in HPLMN
  • SST (112) used in serving PLMN.
  • SD 114 used in the serving PLMN.
  • the S-NSSAI IE may further include a field 110 indicating the length of content included in the S-NSSAI IE.
  • the SST(112) used by the serving PLMN may be the same as the SST(116) used by the HPLMN, and the SD(114) used by the serving PLMN is the SD used by the HPLMN. (118).
  • the SST 112 used in the serving PLMN may be the SST used in the VPLMN (Visited PLMN), and the SD 114 used in the serving PLMN may be the SD used in the VPLMN.
  • Each SST and SD value constituting one S-NSSAI may or may not have a value depending on the situation.
  • Network slice selection assistance information may consist of one or more S-NSSAIs.
  • NSSAI may consist of one or more S-NSSAIs.
  • Examples of NSSAI include Configured NSSAI stored in the terminal, Requested NSSAI requested by the terminal, NF of the 5G core network (eg, access and mobility function (AMF), session management function (SMF), user plane function (UPF) ), PCF (policy control function), UDM (user data management), UDR (user data repository), NSSF (network slice selection function), etc.) Subscribed NSSAI and the like may be included, but this is only an example, and the example of NSSAI is not limited to the above.
  • AMF access and mobility function
  • SMF session management function
  • UPF user plane function
  • PCF policy control function
  • UDM user data management
  • UDR user data repository
  • NSSF network slice selection function
  • a mobile operator can operate a 5G network and an EPS (or LTE-based network or called a 4G network) network together.
  • the mobile communication terminal can access the 5G network and use the service, and then move to the EPS network.
  • the mobile communication terminal may access the EPS network and use the service, then move to the 5G network.
  • This may be referred to as 5GC (5G core)-EPC interworking, 5GS (5G system)-EPS interworking, or 4G-5G interworking.
  • the present disclosure proposes an example of a method of interworking (ie, 5GS-EPS interworking) or 5GC-EPC interworking between a 5G network system structure providing a network slice function and an EPS network system.
  • the present disclosure defines a network operation and terminal operation that establishes a session connection in EPS so that a terminal using a communication service can continuously use the service even if it moves to 5GS.
  • FIG. 2 is a diagram illustrating a structure of network slice interworking related to an embodiment of the present disclosure.
  • 5GS may be composed of a New Radio (NR) base station (radio access node (NG-RAN) or next generation node B (gNB)), AMF, SMF, UPF, PCF, NSSF, UDM, and UDR.
  • NR New Radio
  • NG-RAN radio access node
  • gNB next generation node B
  • EPS is an E-UTRA base station (E-UTRAN (Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network), or eNB (evolved node B)), MME (mobility management entity), SGW (serving gateway), PGW (packet) It may be composed of a data network gateway, composed of a user plane (PGW-U) and a control plane (PGW-C)), a policy and charging rule function (PCRF), and a home subscriber server (HSS).
  • AMF and MME are NF (Network Function) for managing radio network access and mobility for the terminal.
  • the SMF, SGW, and PGW are NFs that manage a session for the terminal, and the session information includes QoS (Quality of Service) information, charging information, and packet processing information.
  • UPF and PGW are NFs that handle user traffic (eg, user plane traffic), and are controlled by SMF and SGW.
  • PCF and PCRF are NFs that manage operator policy and/or PLMN policy for providing a service in a wireless communication system.
  • the PCF may be divided into a PCF in charge of an access and mobility (AM) policy and a UE policy, and a PCF in charge of a session management (SM) policy.
  • AM access and mobility
  • SM session management
  • the PCF in charge of AM/UE policy and the PCF in charge of SM policy may be logically or physically separate NFs or logically or physically one NF.
  • UDM and HSS are NFs for storing and managing subscriber information (UE subscription) of the terminal.
  • UDR is an NF or database (Database, DB) that stores and manages data.
  • the UDR may store subscription information of the terminal and may provide the subscription information of the terminal to the UDM.
  • the UDR may store operator policy information and provide operator policy information to the PCF.
  • the NSSF may be an NF that selects a network slice instance serving a terminal or determines an NSSAI.
  • UDM of 5GS and HSS of EPS may be configured as one combo node (referred to as UDM+HSS).
  • SMF of 5GS and PGW-C of EPS may be configured as one combo node (referred to as SMF+PGW-C).
  • the UDM+HSS node may store subscriber information of the terminal.
  • UPF of 5GS and PGW-U of EPS may be configured as one combo node (referred to as UPF+PGW-C).
  • the UE may use the EPS network service by accessing the MME of the EPS through the E-UTRA base station.
  • the terminal can use the 5GS network service by accessing the AMF of 5GS through the NR base station.
  • one NF or network entity can support different network systems at the same time, and these NFs, network nodes or network entities are described above for combo nodes, combo NFs, combined nodes, combined NFs, and interworking. (interworking) node, interworking NF, etc. may be called.
  • NFs simultaneously supporting different network systems may be indicated by using a “+” sign or a “/” sign.
  • SMF and PGW-C when SMF and PGW-C are configured as one combo node, they may be expressed as PGW-C/SMF, PGW-C+SMF, SMF/PGW-C, or SMF+PGW-C.
  • the order in which the two names are connected has no effect on the function or role of the combo node.
  • a network slice refers to a logical network that provides specific network capability and network characteristic.
  • a mobile network operator may operate one or more network slices.
  • a mobile communication operator may support S-NSSAI A, S-NSSAI B, and S-NSSAI C.
  • the mobile communication operator the operator policy (operator policy), SLA (Service Level Agreement) with a third party service provider ( 3rd party service provider), the characteristics of the network slice, the service supported by the network slice, network deployment (deployment) ) and UE subscription information, a concept of simultaneous use of the network slice supported by a mobile communication operator may be defined.
  • a mobile operator may define that S-NSSAI A and S-NSSAI C can be used at the same time, but S-NSSAI A and S-NSSAI B cannot be used at the same time.
  • the mobile operator may define that S-NSSAI A cannot be used with any other network slice.
  • the mobile operator may define that S-NSSAI A can be used with all network slices.
  • a mobile communication service provider may define that S-NSSAI with the same SST can be used together.
  • a mobile communication operator may define that S-NSSAI with the same SD can be used together.
  • the operator policy defining the simultaneous usability of the network slice described above is referred to as a Simultaneous Use of the Network Slice (SUNS) policy (policy or rule) or SUNS information.
  • the SUNS information may include group information in which the S-NSSAI and the S-NSSAI are linked. More than one S-NSSAI associated with the same group may be used together at the same time. For example, one or more S-NSSAIs associated with the same group may be simultaneously included in Allowed NSSAIs.
  • the SUNS information may be included in the terminal subscription information.
  • NF may support at least one of the following functions in order to provide simultaneous usability of network slices.
  • One NF may support all of the functions below, or multiple NFs may be distributed to support the functions below.
  • One or more specific NFs may have a SUNS policy set.
  • the NF may receive a SUNS policy from another NF.
  • Any NF may store and manage network slice information (eg, S-NSSAI) associated with a session (protocol data unit (PDU) Session or packet data network (PDN) connection) established by the UE.
  • S-NSSAI network slice information
  • PDU protocol data unit
  • PDN packet data network
  • Any NF may determine the network slice (eg, S-NSSAI) of the session (PDU Session or PDN connection) requested by the UE.
  • the NF is at least one of terminal subscription information, terminal request information (eg, APN, etc.), network slice information associated with another session established by the terminal (eg, S-NSSAI), and SUNS policy. Based on the network slice (eg, S-NSSAI) may be determined.
  • Any NF may transmit network slice information (eg, S-NSSAI) determined by a specific NF including itself to other NFs (eg, SMF+PGW-C, etc.).
  • network slice information eg, S-NSSAI
  • FIG. 3 is a diagram illustrating a network slice selection method according to an embodiment of the present disclosure.
  • FIG 3 illustrates a session connection procedure in EPC according to an embodiment of the present disclosure.
  • FIG. 3 an NF operation according to an embodiment of the present disclosure for providing simultaneous usability of a network slice during a session connection procedure is described.
  • the terminal 300 may access the MME 302 of the EPS through the E-UTRA base station 301 , E-UTRAN or eNB to establish a PDN connection and use the EPS network service.
  • the terminal 300 connects to the 4G wireless network (E-UTRAN, 301) and then performs a registration (Attach) process for receiving a 4G service or a process for creating a PDN connection if already registered.
  • the terminal 300 may merge and perform an operation for establishing a PDN connection during the attach process.
  • the terminal 300 may include desired access point name (APN) information in a non-access stratum (NAS) request message sent to the MME 302 to classify a service that is a target of session creation.
  • the terminal 300 may include, in the NAS request message sent to the MME 302 , information (capability indication) indicating whether the terminal supports the simultaneous use function of the network slice.
  • the MME 302 performs a process for creating a session according to the information received from the terminal 300 .
  • the MME 302 selects a GW (eg, SGW, PGW) to process the session in consideration of the APN and other parameters received from the UE, and the MME 302 selects the SMF+PGW-C (for convenience of explanation). , then expressed as SMF, and transmits a request message for session creation to 303 , and this request message for session creation may be delivered to the SMF 303 through the SGW (not shown).
  • the Create Session Request message transmitted by the MME 302 may include an APN and a subscriber ID (International Mobile Subscriber Identity (IMSI)) of the terminal.
  • IMSI International Mobile Subscriber Identity
  • the MME 302 receives information indicating whether the terminal 300 supports the simultaneous use function of the network slice (eg, capability indication), Create Session transmitted by the MME 302
  • the Request message may include information (eg, capability indication) indicating whether the terminal 300 supports the simultaneous use function of the network slice.
  • the SMF 303 may receive necessary information such as policy or subscription information from a specific NF in order to process the PDN connectivity request message received from the terminal 300 through the MME 302 .
  • the SMF 303 may receive a policy from PCF+PCRF, and may also receive subscription information from UDM+HSS.
  • the policy received by the SMF 303 from PCF+PCRF or subscription information received from UDM+HSS may include various information related to network slices.
  • the policy or subscription information received by the SMF 303 may include information (capability indication) indicating whether the terminal 300 supports the simultaneous use function of the network slice.
  • the policy or subscription information received by the SMF 303 may include subscription slices subscribed to by the terminal 300 (subscribed S-NSSAIs). Also, for example, the policy or subscription information received by the SMF 303 may include S-NSSAI and/or APN (data network name (DNN)) information for which a simultaneous use function of a network slice is required.
  • the S-NSSAI information required for the simultaneous use function of the network slice may refer to the SUNS policy (information) described above.
  • the policy or subscription information received by the SMF 303 may include network slice (eg, S-NSSAI) information associated with another session established by the terminal 100 .
  • the SMF 303 based on at least one of information received from the terminal 300 , a policy received from PCF+PCRF, subscription information received from UDM+HSS, and setting information stored in the SMF 303 . , it is possible to determine whether to apply the simultaneous use function of network slices. This may be limitedly applied to specific subscribers, or may be limitedly applied to a specific S-NSSAI or APN.
  • the information received from the terminal 300 and/or the subscription information received from the UDM+HSS may include information indicating that the terminal 300 supports the simultaneous use function of the network slice (capability indication).
  • the SMF 303 may decide to apply the simultaneous use function of the network slice.
  • the information received from the terminal 300 and/or the subscription information received from UDM+HSS includes S-NSSAI and/or APN (DNN) information that requires a simultaneous use function of a network slice.
  • the SMF 303 may decide to apply the simultaneous use function of the network slice.
  • the SMF 303 is an NF 304 for network slice interworking management, which is called Interworking NF in this disclosure, but the name may be Network Slice Quota Management Function, or the like, or NSSF among NFs that have previously provided other functions, PCF, UDM, UDR, etc. may include the corresponding function) to call a request service for selecting a network slice (S-NSSAI) for PDN connection establishment.
  • the SMF 303 may transmit a slice selection request message to the Interworking NF 304 .
  • the SMF 303 may support the function of the Interworking NF described above in the present disclosure.
  • the request message transmitted by the SMF 303 to the Interworking NF 304 may include at least one of one or more S-NSSAI, an ID of a subscriber, and an APN.
  • One or more S-NSSAIs included in the request message sent by the SMF 303 may be one or more S-NSSAIs that the SMF 303 can support.
  • one or more S-NSSAIs included in the request message sent by the SMF 303 may be S-NSSAIs supported by the SMF 303 among subscribed S-NSSAIs of the UE.
  • the request message sent by the SMF 303 to the Interworking NF 304 may include a SUNS policy.
  • the request message sent by the SMF 303 to the Interworking NF 304 may include network slice (eg, S-NSSAI) information associated with another session established by the UE.
  • the interworking NF 304 may process the request message received from the SMF 303 in step 316 .
  • the Interworking NF 304 may determine whether support for the S-NSSAI requested by the SMF 303 is possible, and may select one or more S-NSSAI.
  • a SUNS policy for such determination may be preset.
  • the Interworking NF 304 may receive the SUNS policy from the SMF 303 .
  • the Interworking NF 304 may receive and/or manage S-NSSAI information associated with a session (PDU session or PDN connection) established by the UE.
  • the Interworking NF 304 may store and manage S-NSSAI information associated with a session (PDU session or PDN connection) established by the UE.
  • S-NSSAI information associated with a session (PDU session or PDN connection) established by the UE may be stored in a separate NF or storage (eg, UDM or UDR, 305).
  • a procedure for the Interworking NF 304 to receive information from a separate NF or Storage 305 is described in steps 320 to 322.
  • the Interworking NF 304 may receive S-NSSAI information associated with a session (PDU session or PDN connection) established by the UE from the SMF 303 .
  • Interworking NF 304 may select an S-NSSAI based on a SUNS policy and S-NSSAI information of a session established by the terminal.
  • S-NSSAI A and S-NSSAI C can be used simultaneously (for example, S-NSSAI A and S-NSSAI C are associated with the same group), S-NSSAI A and S-NSSAI B is unavailable at the same time (eg, when S-NSSAI A and S-NSSAI B are associated with different groups, respectively), and another session established by the terminal 300 is associated with S-NSSAI A, , when the SMF 303 can support S-NSSAI B and S-NSSAI C, the Interworking NF 304 may select S-NSSAI C available simultaneously with S-NSSAI A.
  • the Interworking NF 304 does not select the S-NSSAI or the default S-NSSAI You can choose.
  • S-NSSAI A and S-NSSAI C can be used simultaneously (for example, S-NSSAI A and S-NSSAI C are associated with the same group), S-NSSAI A and S-NSSAI B is unavailable at the same time (eg, when S-NSSAI A and S-NSSAI B are associated with different groups, respectively), and another session established by the terminal 300 is associated with S-NSSAI A, , when SMF 303 can support S-NSSAI B, Interworking NF 304, S-NSSAI B supported by SMF 303 is unavailable at the same time as S-NSSAI A, so no S-NSSAI You can choose not to select it or choose the default S-NSSAI.
  • the selected default S-NSSAI may be a default S-NSSAI belonging to the same group as S-NSSAI A associated with another session established by the terminal.
  • the Interworking NF 304 provides the corresponding function.
  • a request message for obtaining status information is transmitted to the NF 305 , and the message may include a subscriber ID of the terminal.
  • the NF 305 may transmit slice information (S-NSSAI) associated with the session established by the terminal referred to as a subscriber ID to the interworking NF 304 .
  • the interworking NF 304 may transmit a request message to the UDM. If necessary, the UDM may store slice-related state information (S-NSSAI information associated with a session established by the UE) in the UDR. According to another embodiment, when the NF 305 providing the storage function is a UDR, the interworking NF 304 may transmit a request message to the UDR, which may be transmitted to the UDR through the UDM.
  • S-NSSAI information slice-related state information associated with a session established by the UE
  • the interworking NF 304 may transmit the slice information (ie, S-NSSAI) selected in step 318 to the SMF 303 .
  • the interworking NF 304 may include the plurality of S-NSSAIs in the response message. can Alternatively, the Interworking NF 304 may include one S-NSSAI selected according to any criterion among a plurality of S-NSSAIs in the response message.
  • the Interworking NF 304 may not include any S-NSSAI in the response message.
  • the Interworking NF 304 may include an error message (reject message, error cause, etc.) indicating that the S-NSSAI selection has failed in the response message.
  • the SMF 303 may finally determine the S-NSSAI to be delivered to the terminal based on the information received from the interworking NF 304 in step 324. If the message received in step 324 includes a plurality of S-NSSAIs, the SMF 303 may select one S-NSSAI from among the received plurality of S-NSSAIs according to any criterion. For example, the SMF 303 may select one S-NSSAI supported by the SMF 303 from among a plurality of received S-NSSAIs.
  • step 324 If, in step 324, no S-NSSAI has been received or information indicating that S-NSSAI selection has failed, or if there is no S-NSSAI supportable by the SMF 303 among the received plurality of S-NSSAIs, The SMF 303 may determine that there is no selectable S-NSSAI. Accordingly, the SMF 303 may decide to reject the session request. In this case, the response message transmitted in steps 328 to 330 may be a reject message. Alternatively, the SMF 303 may select an arbitrary S-NSSAI (eg, default S-NSSAI, S-NSSAI supported by SMF, etc.).
  • S-NSSAI eg, default S-NSSAI, S-NSSAI supported by SMF, etc.
  • step 328 the SMF 303 transmits a Create Session Response message to the MME 302, and at this time, includes the selected S-NSSAI in Protocol Configuration Options (PCO). This message may be forwarded from the SMF 303 to the MME 302 through the SGW.
  • PCO Protocol Configuration Options
  • step 330 the MME 302 sends an acceptance message indicating that Attach or session creation is permitted to the terminal 300 , and at this time, the MME 302 includes the previously received PCO and transmits it to the terminal 300 .
  • the terminal 300 finally receives the S-NSSAI, and this information may be used for a registration process and other session processing when the terminal 300 moves to 5G in the future.
  • the terminal 300 moving to 5G in the future may transmit the requested NSSAI including the S-NSSAI associated with the session established in the EPC to the AMF of 5G in order to continuously use the session established in the EPC in 5G.
  • the S-NSSAI included in the Requested NSSAI may consist of simultaneously available network slices. have.
  • the mobile operator may decide not to apply the slice simultaneous use policy (SUNS) when the terminal accesses the EPC according to the mobile operator policy.
  • the UDM according to the embodiment of the present invention applies the slice simultaneous use policy (ie, the SUNS policy) according to when the terminal subscription information request message is generated, received, or generated or from which NF is generated, received, or generated. can be decided For example, when the terminal subscription information request message is generated, received, or generated during the 5G registration procedure, the UDM may decide to apply the simultaneous use policy (ie, the SUNS policy).
  • the UDM may decide not to apply the concurrent use policy (ie, the SUNS policy).
  • a determination may be determined based on at least one of NF information (eg, NF ID, NF type, etc.) for sending a terminal subscription information request message, definitions of different types of request messages, and indicators included in the request message. .
  • NF information eg, NF ID, NF type, etc.
  • the subscription information received by the SMF from the UDM in step 314 may not include the SUNS information.
  • the UDM may determine the subscribed S-NSSAI according to the operator policy.
  • subscribed S-NSSAIs transmitted by the UDM to the SMF may include only S-NSSAIs belonging to the same group.
  • the UDM may determine the S-NSSAI associated with the group to which the default S-NSSAI belongs as subscribed S-NSSAIs and transmit it to the SMF.
  • the S-NSSAI associated with all PDN connections established by the UE in the EPC may all belong to the same group.
  • the subscribed S-NSSAIs transmitted by the UDM to the SMF may include S-NSSAIs belonging to different groups.
  • the S-NSSAI associated with the PDN connection established by the UE in the EPC may belong to different groups.
  • FIG. 4 is a diagram illustrating a network slice selection method according to an embodiment of the present disclosure.
  • FIG. 4 illustrates a session connection procedure in EPC according to an embodiment of the present disclosure.
  • a terminal operation according to an embodiment of the present disclosure for providing simultaneous usability of a network slice among the session connection procedure shown in FIG. 4 will be described.
  • the terminal 300 may access the MME 302 of the EPS through the E-UTRA base station 301 to establish a PDN connection and use the EPS network service.
  • a SUNS policy may be preset in the terminal 300 according to an embodiment of the present disclosure.
  • the terminal 300 may receive and store the SUNS policy from the NF (AMF, PCF, UDM, etc.).
  • the SUNS policy may be information included in a UE policy (eg, UE Route Selection Policy (URSP)) or configured NSSAI.
  • URSP UE Route Selection Policy
  • the SUNS policy may be information independent of URSP or Configured NSSAI.
  • the terminal 300 may manage S-NSSAI information associated with a session (PDU session, PDN connection) established by the terminal.
  • the terminal 300 may select an S-NSSAI of a session to be newly established based on the SUNS policy and S-NSSAI information of the session established by the terminal.
  • the terminal 300 may determine that a session to be newly established may be provided through S-NSSAI B or S-NSSAI C based on a terminal policy (eg, URSP).
  • a terminal policy eg, URSP
  • S-NSSAI A, S-NSSAI B, and S-NSSAI C are included in the Configured NSSAI stored by the terminal 300, and S-NSSAI A and S-NSSAI C can be used simultaneously, and S- NSSAI A and S-NSSAI B cannot be used at the same time, and when another session established by the terminal 300 is associated with S-NSSAI A, the terminal 300 is S-NSSAI C available simultaneously with S-NSSAI A can be selected.
  • the terminal 300 may not select the S-NSSAI or may select the default S-NSSAI.
  • the terminal 300 may determine that a session to be newly established can be provided through S-NSSAI B, based on the terminal policy (eg, URSP).
  • the terminal policy eg, URSP
  • S-NSSAI A and S-NSSAI B are included in the Configured NSSAI stored by the terminal 300, and S-NSSAI A and S-NSSAI B cannot be used at the same time, and the terminal 300 has established
  • the terminal 300 does not select any S-NSSAI or can select the default S-NSSAI as S-NSSAI B is unavailable at the same time as S-NSSAI A have.
  • the terminal 300 connects to the 4G wireless network (E-UTRAN or eNB, 301) and then performs a registration (Attach) process to receive a 4G service, or a process for creating a PDN connection if already registered. .
  • the terminal 300 may merge and perform an operation for establishing a PDN connection during the attach process.
  • the terminal 300 includes the desired APN in the NAS request message sent to the MME 302 to identify the service that is the target of the session creation, and includes the S-NSSAI selected by the terminal 300 in step 410 together with the APN. can do it
  • the terminal 300 may include, in the NAS request message sent to the MME 302 , information (capability indication) indicating whether the terminal supports the simultaneous use function of the network slice.
  • the MME 302 performs a process for creating a session according to the information received from the terminal 300 .
  • the MME 302 selects a GW (eg, SGW, PGW) to process the session in consideration of the APN and other parameters, and the MME 302 is SMF+PGW-C (for convenience of explanation, later as SMF) Expressing, 304) transmits a request message for session creation.
  • the session creation request message transmitted by the MME 302 may be transferred to the SMF 304 through the SGW (not shown).
  • the Create Session Request message transmitted by the MME 302 may include an APN and a subscriber ID (IMSI) of the terminal.
  • IMSI subscriber ID
  • the Create Session Request message transmitted by the terminal may include the S-NSSAI selected by the terminal, information indicating whether to support the simultaneous use function of the network slice of the terminal 300 (eg, capability indication information), and the like.
  • the SMF 303 may receive necessary information such as policy or subscription information from a specific NF in order to process the PDN connectivity request message received from the terminal 300 through the MME 302 .
  • the SMF 303 may receive a policy from PCF+PCRF, and may also receive subscription information from UDM+HSS.
  • the policy received by the SMF 303 from PCF+PCRF or subscription information received from UDM+HSS may include various information related to network slices.
  • the policy or subscription information received by the SMF 303 may include information (capability indication) indicating whether the terminal 300 supports the simultaneous use function of the network slice.
  • the policy or subscription information received by the SMF 303 may include subscription slices subscribed to by the terminal 300 (subscribed S-NSSAIs). Also, for example, the policy or subscription information received by the SMF 303 may include S-NSSAI and/or APN (DNN) information for which a simultaneous use function of a network slice is required.
  • the S-NSSAI information for which the simultaneous use function of the network slice is required may mean a SUNS policy (or SUNS information).
  • the SMF 303 based on at least one of information received from the terminal 300, a policy received from PCF+PCRF, subscription information received from UDM+HSS, and setting information stored in the SMF 303. , it is possible to determine whether to apply the simultaneous use function of network slices. This may be limitedly applied to specific subscribers, or may be limitedly applied to a specific S-NSSAI or APN.
  • the information received from the terminal 300 and/or the subscription information received from the UDM+HSS may include information indicating that the terminal 300 supports the simultaneous use function of the network slice (capability indication).
  • the SMF 303 may decide to apply the simultaneous use function of the network slice.
  • the information received from the terminal 300 and/or the subscription information received from UDM+HSS includes S-NSSAI and/or APN (DNN) information that requires a simultaneous use function of a network slice.
  • the SMF 303 may decide to apply the simultaneous use function of the network slice.
  • the SMF 303 may finally determine the S-NSSAI to be delivered to the terminal based on the information received from the terminal 300, the subscription information received from the UDM, and the configuration information stored in the SMF 303. have.
  • the SMF 303 may check whether the S-NSSAI received from the terminal 300 is included in the subscription information (subscribed S-NSSAIs) received from the UDM. In addition, the SMF 303 may check whether the S-NSSAI received from the terminal 300 is an S-NSSAI that the SMF 303 can support.
  • the SMF 303 receives the S received from the terminal 300 - You may decide to use NSSAI.
  • the SMF 303 is the terminal 300 It may decide not to use the S-NSSAI received from Accordingly, the SMF 303 may decide to reject the session request. In this case, the response message transmitted in steps 420 to 422 may be a reject message. Alternatively, the SMF 303 may select an arbitrary S-NSSAI (eg, default S-NSSAI, S-NSSAI supported by SMF, etc.).
  • step 420 the SMF 303 transmits the Create Session Response to the MME 302, and at this time, the S-NSSAI selected by the SMF 303 is included in the PCO.
  • This message sent by the SMF 303 may be delivered to the MME 302 through the SGW.
  • step 422 the MME (302) sends an acceptance message to the terminal notifying that Attach or session creation is permitted, and at this time, the previously received PCO is included and transmitted.
  • the terminal 300 will finally receive the S-NSSAI, and this information may be used for the registration process and other session processing when the terminal 300 moves to 5G in the future.
  • the terminal 300 moving to 5G in the future may transmit the requested NSSAI including the S-NSSAI associated with the session established in the EPC to the AMF of 5G in order to continuously use the session established in the EPC in 5G.
  • the S-NSSAI included in the Requested NSSAI may consist of simultaneously available network slices. have.
  • 5 is a diagram illustrating a network slice management method according to an embodiment of the present disclosure. 5 illustrates a procedure for moving from EPC to 5GC according to an embodiment of the present disclosure.
  • FIG. 5 an NF operation according to an embodiment of the present disclosure for providing simultaneous usability of network slices during a registration procedure is described.
  • the terminal 300 may continuously use the session established in the EPC after moving it to the 5GC.
  • the terminal 300 can use the service by creating a PDN connection after accessing 4G.
  • one session ie, PDN connection
  • one session is associated with one Slice ID (S-NSSAI)
  • the terminal 300 has a Slice ID (S-NSSAI) associated with each session (ie, PDN connection).
  • S-NSSAI Slice ID
  • the first session established by the UE in the EPC may be associated with the first Slice ID
  • the second session may be associated with the second Slice ID.
  • the terminal 300 moving to 5GC may transmit a Registration Request message to the AMF 500 in order to access 5G.
  • the Registration Request message may include Requested NSSAI.
  • the Requested NSSAI included in the Registration Request message transmitted by the terminal may include a Slice ID associated with the PDN connection established by the terminal 300 in the EPC.
  • the Requested NSSAI may include a first Slice ID and a second Slice ID.
  • a SUNS policy may be preset in the terminal 300 .
  • the terminal 300 may receive and store the SUNS policy from the NF (AMF, PCF, UDM, etc.).
  • the SUNS policy may be information included in a terminal policy (UE policy, for example, UE Route Selection Policy (URSP)) or configured NSSAI.
  • UE policy for example, UE Route Selection Policy (URSP)
  • URSP UE Route Selection Policy
  • the SUNS policy may be information independent of URSP or Configured NSSAI.
  • the terminal 300 may configure a Requested NSSAI based on the SUNS information.
  • the terminal 300 sends the first Slice ID to the Requested NSSAI.
  • the second Slice ID may be included.
  • the terminal 300 includes the first Slice ID and Only one Slice ID among the second Slice IDs may be included.
  • the SUNS policy may not be preset in the terminal 300 .
  • the terminal 300 may configure the Requested NSSAI based on priority information for each slice. For example, the terminal 300 may determine the slice priority between the first Slice ID associated with the first session established in the EPC and the second Slice ID associated with the second session.
  • the terminal 300 may include the first Slice ID, the second Slice ID, and priority information of each Slice ID in the Requested NSSAI.
  • the terminal 300 may configure the order of Slice IDs included in the Requested NSSAI according to the priority.
  • the AMF 500 may determine an allowed slice (Allowed NSSAI) that the terminal 300 can use by accessing 5G in consideration of the simultaneously available network slice policy. In addition, the AMF 500 may determine the Allowed NSSAI through the NSSF (not shown) during this process.
  • a SUNS policy may be set in the AMF 500 or NSSF according to an embodiment of the present disclosure.
  • the AMF or NSSF may receive a SUNS policy from another NF (eg, PCF, UDM, AMF, etc.).
  • another NF eg, PCF, UDM, AMF, etc.
  • the AMF 500 provides PDN connection information (including S-NSSAI information associated with the PDN connection) established by the UE in the EPC from another NF (eg, MME, SMF, UDM, etc.) can be obtained
  • the AMF 500 or NSSF is at least one of Requested NSSAI, SUNS policy, PDN connection information established by the UE in the EPC, UE subscription information, slice priority, and S-NSSAI information supported by SMF Based on , Allowed NSSAI may be determined.
  • the AMF 500 or the NSSF may determine whether the first Slice ID and the second Slice ID included in the Requested NSSAI are simultaneously available network slices, based on the SUNS policy.
  • the AMF or the NSSF may include the first Slice ID and the second Slice ID in the Allowed NSSAI.
  • the AMF or the NSSF may include only one Slice ID of the first Slice ID and the second Slice ID in the Allowed NSSAI.
  • slice priority may be considered.
  • the AMF or the NSSF may determine to include a slice with a high priority among network slices that cannot be used simultaneously in the Allowed NSSAI.
  • the slice priority may be determined based on a network policy and/or information transmitted by the terminal (eg, the order of Slice IDs included in the Requested NSSAI).
  • the AMF or the NSSF may perform the slice change.
  • the AMF or NSSF may determine to change the second Slice ID to a third Slice ID that can be used simultaneously with the first Slice ID.
  • the third Slice ID may be a slice that is available simultaneously with the first Slice ID among UE-subscribed slices (subscribed S-NSSAIs).
  • the third Slice ID may be a slice supported by the SMF serving the second session.
  • slice priority when AMF or NSSF performs slice change, slice priority may be considered.
  • the AMF or the NSSF may determine to first change a slice having a lower priority among network slices that cannot be used simultaneously.
  • the slice priority may be determined based on a network policy and/or information transmitted by the terminal (eg, the order of Slice IDs included in the Requested NSSAI).
  • the AMF or NSSF may include the first Slice ID and the third Slice ID (a slice ID replaced with the second Slice ID) in the Allowed NSSAI.
  • the AMF 500 may transmit a Registration Accept message to the terminal 300 .
  • the Registration Accept message may include Allowed NSSAI determined in step 522.
  • the AMF 500 may include information notifying that the slice change has occurred in the Registration Accept message.
  • the terminal 300 finally receives the S-NSSAI included in the Allowed NSSAI, and when the slice ID replacement occurs, the session information may be updated according to the replacement.
  • the following shows an example of the configuration of Requested NSSAI and Allowed NSSAI according to an embodiment of the present disclosure. For description, it is assumed that the second Slice ID associated with the second session is replaced with the third Slice ID.
  • the first Slice ID and the second Slice ID included in the Requested NSSAI are SST (112) and SD (114, optional) of the serving PLMN shown in FIG. 1 .
  • the first Slice ID and the third Slice ID included in the Allowed NSSAI are the SST 112 of the serving PLMN and the SD (114, optional) of the serving PLMN shown in FIG. 1 .
  • the second slice ID is the mapped SST 116 and the mapped SD 118 shown in FIG. 2 , which are optional.
  • the UE 300 that transmits the Requested NSSAI and receives the Allowed NSSAI receives the SST 112 and the serving PLMN of the serving PLMN in the Allowed NSSAI without changing the first Slice ID associated with the first session. It can be seen that there is no change in the S-NSSAI associated with the first session, confirming that the SD (114, optional) is included.
  • the second Slice ID associated with the second session is included in the Allowed NSSAI as mapped SST (116) and mapped SD (118, optional), and the slice mapped with the second Slice ID is the third It can be confirmed that the slice ID is used, and the S-NSSAI associated with the second session is changed from the second slice ID to the third slice ID.
  • the terminal 300 may evaluate or re-evaluate whether the service/application using the second session may use the third Slice ID based on the URSP stored in the terminal. If the second session may use the third Slice ID, the terminal 300 may update S-NSSAI information associated with the second session to the third Slice ID. If the second session cannot use the third Slice ID, the terminal 300 may request release of the second session connection.
  • the terminal 300 If there is an S-NSSAI included in the Requested NSSAI requested by the terminal 300 but not included in the Allowed NSSAI received by the terminal 300, the terminal 300 knows that the S-NSSAI is no longer available. can Accordingly, the terminal 300 may release or terminate the PDU session (or PDN connection) associated with the corresponding S-NSSAI.
  • FIG. 6 is a diagram illustrating a structure of a terminal according to an embodiment of the present disclosure.
  • the terminal may include a transceiver 610 , a terminal control unit 620 , and a storage unit 630 .
  • the terminal controller 820 may be defined as a circuit or an application-specific integrated circuit or at least one processor.
  • the transceiver 610 may transmit and receive signals to and from the base station, other terminals, and network entities.
  • the transceiver may, for example, receive system information transmitted from a base station, or transmit/receive data based on a synchronization signal, a reference signal, and/or control information.
  • the terminal control unit 620 may control the overall operation of the terminal according to the embodiment proposed in the present disclosure.
  • the terminal control unit 620 may control the signal flow between blocks to perform an operation according to the above-described drawings and flowcharts.
  • the terminal control unit 620 operates according to a control signal from the base station and may send and receive messages or signals with the base station, other terminals, and/or network entities.
  • the storage unit 630 may store at least one of information transmitted and received through the transmission/reception unit 610 and information generated through the terminal control unit 620 .
  • NF of FIG. 7 is a diagram illustrating a structure of a network function (NF) according to an embodiment of the present disclosure.
  • NF of FIG. 7 may include an NF instance.
  • the NF shown in FIG. 7 may mean an entity supporting the various network functions described above, for example, a mobility management entity (MME), an access and mobility function (AMF), a session management function (SMF), an interworking NF, It may mean at least one of user data management (UDM), user data repository (UDR), and policy control function (PCF), and is not limited to a specific NF.
  • MME mobility management entity
  • AMF access and mobility function
  • SMF session management function
  • PCF policy control function
  • NF may be provided in the form of an instance, and when provided as an instance, NF exists in the form of software code, and in a physical computing system, for example, a specific computing system existing on a core network, NF Since it may mean an executable state by being allocated physical and/or logical resources from the computing system to perform the function of .
  • the NF may include a transceiver 710 , an NF control unit 720 , and a storage unit 730 .
  • the transceiver 710 may transmit/receive signals to and from other network entities.
  • the transceiver may send and receive signaling for transmitting/receiving control information and data to, for example, another network entity (NF) or a base station.
  • NF network entity
  • the NF control unit 720 may control the overall operation of the NF according to the embodiment proposed in the present disclosure.
  • the NF control unit 720 may control the signal flow between blocks to perform an operation according to the above-described drawings and flowcharts.
  • the NF control unit 720 operates according to signaling received from other network entities or base stations, and may send and receive messages or signals with the terminal, the base station, and/or other network entities.
  • the storage unit 730 may store at least one of information transmitted/received through the transceiver unit 710 and information generated through the NF control unit 720 .
  • FIG. 8 is a diagram illustrating a structure of a base station according to an embodiment of the present disclosure.
  • the base station may include a transceiver 810 , a base station controller 820 , and a storage 830 .
  • the base station controller 820 may be defined as a circuit or an application-specific integrated circuit or at least one processor.
  • the transceiver 810 may transmit/receive a signal to/from a terminal and a network entity.
  • the transceiver may transmit, for example, system information, a synchronization signal or a reference signal, or control information and data to the terminal, and may send and receive messages and signaling for providing a service to the network entity and the terminal.
  • the base station controller 820 may control the overall operation of the base station according to the embodiment proposed in the present disclosure.
  • the base station controller may control the signal flow between blocks to perform an operation according to the above-described drawings and flowcharts.
  • the base station control unit may send and receive messages or signals with the terminal and/or the network entity.
  • the storage unit 830 may store at least one of information transmitted and received through the transceiver 810 and information generated through the base station control unit 820 .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)
PCT/KR2021/009879 2020-07-30 2021-07-29 네트워크 슬라이스의 동시 사용 방법 및 장치 Ceased WO2022025666A1 (ko)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2023506133A JP7766077B2 (ja) 2020-07-30 2021-07-29 ネットワークスライスの同時使用方法及び装置
CN202180058469.9A CN116058010A (zh) 2020-07-30 2021-07-29 用于同时使用网络切片的方法和设备
EP21851581.5A EP4175367A4 (en) 2020-07-30 2021-07-29 METHOD AND APPARATUS FOR THE SIMULTANEOUS USE OF NETWORK SLICES
US18/018,382 US20230300731A1 (en) 2020-07-30 2021-07-29 Method and device for simultaneously using network slices

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR10-2020-0095181 2020-07-30
KR1020200095181A KR20220015104A (ko) 2020-07-30 2020-07-30 네트워크 슬라이스의 동시 사용 방법 및 장치

Publications (1)

Publication Number Publication Date
WO2022025666A1 true WO2022025666A1 (ko) 2022-02-03

Family

ID=80035836

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2021/009879 Ceased WO2022025666A1 (ko) 2020-07-30 2021-07-29 네트워크 슬라이스의 동시 사용 방법 및 장치

Country Status (6)

Country Link
US (1) US20230300731A1 (https=)
EP (1) EP4175367A4 (https=)
JP (1) JP7766077B2 (https=)
KR (1) KR20220015104A (https=)
CN (1) CN116058010A (https=)
WO (1) WO2022025666A1 (https=)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023184193A1 (zh) * 2022-03-29 2023-10-05 Oppo广东移动通信有限公司 无线通信方法、装置、设备、存储介质及程序产品

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3967078A1 (en) * 2019-05-10 2022-03-16 Nokia Technologies Oy Apparatus, method, and computer program
EP4114054B1 (en) * 2020-03-31 2025-12-24 Samsung Electronics Co., Ltd. Method and apparatus for supporting inter-system mobility in wireless communication system
WO2022064336A1 (en) * 2020-09-25 2022-03-31 Telefonaktiebolaget Lm Ericsson (Publ) Network slice quotas in the presence of interworking
EP4289415A4 (en) 2021-02-08 2025-01-01 IMGT Co, Ltd. COMPOSITION FOR PENETRATION OF THE BLOOD-BRAIN BARRIER WITH SONOSENSITIVE LIPOSOMES AS ACTIVE INGREDIENTS

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20190082897A (ko) * 2016-11-18 2019-07-10 엘지전자 주식회사 무선 통신 시스템에서의 네트워크 노드 선택 방법 및 이를 위한 장치
WO2019245921A1 (en) * 2018-06-22 2019-12-26 Idac Holdings, Inc. Handling mutually exclusive network slices
KR20200003195A (ko) * 2017-06-17 2020-01-08 엘지전자 주식회사 무선 통신 시스템에서 단말의 등록 방법 및 이를 위한 장치
WO2020080044A1 (ja) * 2018-10-16 2020-04-23 ソニー株式会社 通信制御装置、通信装置、通信制御方法、通信方法、通信制御プログラム、通信プログラム、及び通信システム
KR20200068668A (ko) * 2017-10-19 2020-06-15 퀄컴 인코포레이티드 네트워크 슬라이싱과 이볼브드 패킷 코어 접속성 사이의 상호작용을 인에이블하기 위한 메커니즘

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018157439A1 (zh) 2017-03-01 2018-09-07 华为技术有限公司 业务处理的方法和设备
CN113784333B (zh) * 2017-10-16 2022-05-24 华为技术有限公司 一种移动性管理的方法、装置及系统
US10660016B2 (en) * 2017-11-08 2020-05-19 Ofinno, Llc Location based coexistence rules for network slices in a telecommunication network
CN109951884B (zh) * 2017-11-17 2020-06-16 华为技术有限公司 会话建立方法和装置
EP3589037A1 (en) 2018-06-29 2020-01-01 Industrial Technology Research Institute Method and user equipment for accessing network slices which are not mutually exclusive
CN109246813B (zh) * 2018-07-16 2020-03-31 中兴通讯股份有限公司 一种网络切片互斥关系处理方法、设备及系统
KR102667414B1 (ko) * 2018-08-13 2024-05-21 삼성전자주식회사 무선 통신 시스템에서 네트워크 슬라이스의 상호 배타적 접속 방법
US11076347B2 (en) * 2018-10-01 2021-07-27 Zte Corporation Coexistent slicing group support in network slicing
US11812370B2 (en) 2018-10-09 2023-11-07 Telefonaktiebolaget Lm Ericsson (Publ) Apparatuses, methods, computer programs, and computer program products for supporting mutually exclusive access to network slices
WO2020153773A1 (en) * 2019-01-22 2020-07-30 Samsung Electronics Co., Ltd. Device and method for providing network slice interworking in wireless communication system
WO2022009773A1 (en) * 2020-07-08 2022-01-13 Sharp Kabushiki Kaisha Cell barring for network slicing
WO2023135572A1 (en) * 2022-01-17 2023-07-20 Telefonaktiebolaget Lm Ericsson (Publ) Dynamic retrieval of nsac information

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20190082897A (ko) * 2016-11-18 2019-07-10 엘지전자 주식회사 무선 통신 시스템에서의 네트워크 노드 선택 방법 및 이를 위한 장치
KR20200003195A (ko) * 2017-06-17 2020-01-08 엘지전자 주식회사 무선 통신 시스템에서 단말의 등록 방법 및 이를 위한 장치
KR20200068668A (ko) * 2017-10-19 2020-06-15 퀄컴 인코포레이티드 네트워크 슬라이싱과 이볼브드 패킷 코어 접속성 사이의 상호작용을 인에이블하기 위한 메커니즘
WO2019245921A1 (en) * 2018-06-22 2019-12-26 Idac Holdings, Inc. Handling mutually exclusive network slices
WO2020080044A1 (ja) * 2018-10-16 2020-04-23 ソニー株式会社 通信制御装置、通信装置、通信制御方法、通信方法、通信制御プログラム、通信プログラム、及び通信システム

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4175367A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023184193A1 (zh) * 2022-03-29 2023-10-05 Oppo广东移动通信有限公司 无线通信方法、装置、设备、存储介质及程序产品

Also Published As

Publication number Publication date
KR20220015104A (ko) 2022-02-08
US20230300731A1 (en) 2023-09-21
CN116058010A (zh) 2023-05-02
JP7766077B2 (ja) 2025-11-07
EP4175367A1 (en) 2023-05-03
EP4175367A4 (en) 2023-12-13
JP2023536145A (ja) 2023-08-23

Similar Documents

Publication Publication Date Title
WO2020251309A1 (en) Method and apparatus for providing service in wireless communication system
WO2020204530A1 (en) Apparatus and method for supporting one-to-one communication service in wireless communication system
WO2021096325A1 (en) Method and apparatus for improving network slice control accuracy in wireless communication system
WO2021045531A1 (en) Apparatus and method for network automation in wireless communication system
WO2021091285A1 (en) Method and apparatus for controlling network slice in wireless communication system
WO2019194630A1 (en) Method and apparatus for supporting vehicle communications in 5g system
WO2018128499A1 (en) Method and apparatus for selecting an access and mobility management function in a mobile communication system
WO2022025666A1 (ko) 네트워크 슬라이스의 동시 사용 방법 및 장치
WO2022211424A1 (en) Method and apparatus for session management
WO2019035637A1 (en) METHOD FOR NEGOTIATING CAPACITY AND MAPPING WAFER INFORMATION BETWEEN A NETWORK AND TERMINAL IN A 5G SYSTEM
WO2019035638A1 (ko) 제 3자 응용 서버에서 단말의 무선 연결 타입 변경을 확인하는 방법
WO2021096222A1 (en) Apparatus and method for providing interworking of network slices in wireless communication system
WO2022177333A1 (ko) 무선 액세스 네트워크에서 셀 정보와 e2 인터페이스 셋업을 위한 장치 및 방법
WO2021025463A1 (en) Method and apparatus for improving voice service quality in wireless communication system
WO2021167290A1 (en) Method and apparatus for enhancing network selection accuracy in wireless communication system
WO2022065985A1 (en) Method and device for supporting network slice upon network interworking
WO2021034175A1 (ko) 복수의 sim을 이용한 서비스 제공 방법 및 장치
WO2020071727A1 (ko) 무선 통신 시스템에서 로밍 단말의 네트워크 슬라이스에 상호 배타적 접속 방법 및 장치
WO2022164199A1 (en) Method and apparatus for configuring session in wireless communication system
WO2018230941A1 (ko) 단말의 망 접속 방법 및 이동성 지원과 데이터 전달 방법 및 장치
WO2023075418A1 (en) Method and apparatus for providing network slice in wireless communication system
WO2019216663A1 (ko) 차세대 이동통신 시스템에서 rrc 상태 미일치 문제를 제어하는 방법 및 장치
WO2021235887A1 (ko) 네트워크 슬라이싱을 지원하는 무선 통신 시스템에서 통신 방법 및 장치
WO2022025669A1 (ko) 슬라이스 연동을 지원하는 방법 및 장치
WO2023059141A1 (en) Method and device for session breakout of home routed session in visited plmn in wireless communication system

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2023506133

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2021851581

Country of ref document: EP

Effective date: 20230130

NENP Non-entry into the national phase

Ref country code: DE