WO2017213457A1 - Procédé et appareil de réception d'une identification de fonction de plan de commande commun - Google Patents

Procédé et appareil de réception d'une identification de fonction de plan de commande commun Download PDF

Info

Publication number
WO2017213457A1
WO2017213457A1 PCT/KR2017/006015 KR2017006015W WO2017213457A1 WO 2017213457 A1 WO2017213457 A1 WO 2017213457A1 KR 2017006015 W KR2017006015 W KR 2017006015W WO 2017213457 A1 WO2017213457 A1 WO 2017213457A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
control plane
plane function
common control
base station
Prior art date
Application number
PCT/KR2017/006015
Other languages
English (en)
Korean (ko)
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 엘지전자 주식회사
Publication of WO2017213457A1 publication Critical patent/WO2017213457A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • 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
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices

Definitions

  • the present invention relates to a wireless communication system, and more particularly, to a method for a base station to receive an ID of a common control plane function (Common CP-Function) and an apparatus supporting the same.
  • a common control plane function Common CP-Function
  • a 5G communication system or a pre-5G communication system is called a system after a 4G network (beyond 4G network) or after a long term evolution (LTE) system (post LTE).
  • 5G communication systems are being considered for implementation in the ultra-high frequency (mmWave) band (eg, such as the 60 giga (60 GHz) band).
  • mmWave ultra-high frequency
  • FD-MIMO massive array multiple input / output
  • FD-MIMO full dimensional MIMO
  • advanced small cells in the 5G communication system, advanced small cells, advanced small cells, cloud radio access network (cloud RAN), ultra-dense network (ultra-dense network) ), Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, coordinated multi-points, and received interference cancellation Technology development, etc.
  • cloud RAN cloud radio access network
  • ultra-dense network ultra-dense network
  • D2D Device to Device communication
  • wireless backhaul moving network, cooperative communication, coordinated multi-points, and received interference cancellation Technology development, etc.
  • FQAM hybrid FSK and QAM modulation
  • SWSC sliding window superposition coding
  • ACM advanced coding modulation
  • FBMC advanced access bank filter bank multi carrier
  • NOMA non orthogonal multiple access
  • SCMA sparse code multiple access
  • network slicing is introduced, which aims to independence and flexibility of services and network resources.
  • the UE cannot know which slice is selected in response to the requested service. Therefore, in the MM attach procedure, a procedure for the UE and the base station to receive information on the selected slice needs to be proposed.
  • a method of receiving an identification of a common control plane function (Common CP-Function) by a base station in a wireless communication system includes selecting a common control plane function; Receiving an ID of the selected common control plane function from the selected common control plane function; And transmitting the received ID of the common control plane function to the terminal.
  • Common control plane function Common CP-Function
  • the method may further include receiving an attach request from the terminal, wherein the access request may include information on a service desired by the UE.
  • the selected common control plane function may be selected based on the connection request.
  • the selected common control plane function may be a common control plane function corresponding to a network slice providing a service desired by the terminal.
  • the method may further include allocating a first unique ID to the terminal that has transmitted the access request.
  • the method may further include transmitting the assigned first unique ID to the selected common control plane function.
  • the method further includes receiving a second unique ID from the selected common control plane function, wherein the second unique ID is for the terminal that has sent the connection request by the selected common control plane function.
  • the method may further include establishing a UE-associated logical NG1-connection when the base station receives a second unique ID, wherein the UE-related logical NG1 connection is established with the terminal. It may be a reference point between the selected common control plane functions.
  • the method may further include receiving a temporary ID including information on the common control plane function from the terminal.
  • the selected common control plane function may be selected based on the temporary ID.
  • the common control plane function may be an access and mobility function (AMF).
  • AMF access and mobility function
  • a base station receiving an identification of a common control plane function (Common CP-Function) in a wireless communication system.
  • the base station includes a memory; Transceiver; And a processor connecting the memory and the transceiver, wherein the processor selects a common control plane function, controls the transceiver to receive an ID of the selected common control plane function from the selected common control plane function,
  • the transceiver may be configured to control the transmission of the received ID of the common control plane function to the terminal.
  • the base station and the terminal may know which slice is selected in response to the attach request.
  • FIG. 1 shows a structure of an LTE system.
  • FIG 5 shows a scenario of a separated base station deployment (Centralized Deployment).
  • FIG. 6 shows an example where a network is sliced.
  • FIG. 7 illustrates an example of sharing a set of common C-plane functions among multiple core network instances.
  • 8 and 9 illustrate examples of signal flows for supporting a connection with a plurality of core network instances.
  • FIG. 10 illustrates an initial MM attach procedure according to an embodiment of the present invention.
  • FIG. 11 is a block diagram illustrating a method for a base station to receive an ID of a common control plane function according to an embodiment of the present invention.
  • FIG. 12 is a block diagram of a wireless communication system in which an embodiment of the present invention is implemented.
  • CDMA code division multiple access
  • FDMA frequency division multiple access
  • TDMA time division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single carrier frequency division multiple access
  • CDMA may be implemented with a radio technology such as universal terrestrial radio access (UTRA) or CDMA2000.
  • TDMA may be implemented with wireless technologies such as global system for mobile communications (GSM) / general packet radio service (GPRS) / enhanced data rates for GSM evolution (EDGE).
  • GSM global system for mobile communications
  • GPRS general packet radio service
  • EDGE enhanced data rates for GSM evolution
  • OFDMA may be implemented by wireless technologies such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, evolved UTRA (E-UTRA), and the like.
  • IEEE 802.16m is an evolution of IEEE 802.16e and provides backward compatibility with systems based on IEEE 802.16e.
  • UTRA is part of a universal mobile telecommunications system (UMTS).
  • 3rd generation partnership project (3GPP) long term evolution (LTE) is part of evolved UMTS (E-UMTS) using evolved-UMTS terrestrial radio access (E-UTRA), which employs OFDMA in downlink and SC in uplink -FDMA is adopted.
  • LTE-A (advanced) is the evolution of 3GPP LTE.
  • 5G communication system is the evolution of LTE-A.
  • FIG. 1 shows a structure of an LTE system.
  • Communication networks are widely deployed to provide various communication services such as IMS and Voice over internet protocol (VoIP) over packet data.
  • VoIP Voice over internet protocol
  • an LTE system structure includes one or more UEs 10, an evolved-UMTS terrestrial radio access network (E-UTRAN), and an evolved packet core (EPC).
  • the terminal 10 is a communication device moved by a user.
  • the terminal 10 may be fixed or mobile and may be called by other terms such as a mobile station (MS), a user terminal (UT), a subscriber station (SS), and a wireless device.
  • MS mobile station
  • UT user terminal
  • SS subscriber station
  • wireless device a wireless device.
  • the E-UTRAN may include one or more evolved node-eB (eNB) 20, and a plurality of terminals may exist in one cell.
  • the eNB 20 provides an end point of a control plane and a user plane to the terminal.
  • the eNB 20 generally refers to a fixed station communicating with the terminal 10, and may be referred to in other terms such as a base station (BS), a base transceiver system (BTS), an access point, and the like.
  • BS base station
  • BTS base transceiver system
  • One eNB 20 may be arranged per cell. There may be one or more cells within the coverage of the eNB 20.
  • One cell may be configured to have one of bandwidths such as 1.25, 2.5, 5, 10, and 20 MHz to provide downlink (DL) or uplink (UL) transmission service to various terminals. In this case, different cells may be configured to provide different bandwidths.
  • DL means communication from the eNB 20 to the terminal 10
  • UL means communication from the terminal 10 to the eNB 20.
  • the transmitter may be part of the eNB 20 and the receiver may be part of the terminal 10.
  • the transmitter may be part of the terminal 10 and the receiver may be part of the eNB 20.
  • the EPC may include a mobility management entity (MME) that serves as a control plane, and a system architecture evolution (SAE) gateway (S-GW) that serves as a user plane.
  • MME mobility management entity
  • SAE system architecture evolution gateway
  • S-GW gateway
  • the MME / S-GW 30 may be located at the end of the network and is connected to an external network.
  • the MME has information about the access information of the terminal or the capability of the terminal, and this information may be mainly used for mobility management of the terminal.
  • S-GW is a gateway having an E-UTRAN as an endpoint.
  • the MME / S-GW 30 provides the terminal 10 with the endpoint of the session and the mobility management function.
  • the EPC may further include a packet data network (PDN) -gateway (GW).
  • PDN-GW is a gateway with PDN as an endpoint.
  • the MME includes non-access stratum (NAS) signaling to the eNB 20, NAS signaling security, access stratum (AS) security control, inter CN (node network) signaling for mobility between 3GPP access networks, idle mode terminal reachability ( Control and execution of paging retransmission), tracking area list management (for terminals in idle mode and active mode), P-GW and S-GW selection, MME selection for handover with MME change, 2G or 3G 3GPP access Bearer management, including roaming, authentication, and dedicated bearer settings, SGSN (serving GPRS support node) for handover to the network, public warning system (ETWS) and commercial mobile alarm system (PWS) It provides various functions such as CMAS) and message transmission support.
  • NAS non-access stratum
  • AS access stratum
  • inter CN node network
  • MME selection for handover with MME change
  • 2G or 3G 3GPP access Bearer management including roaming, authentication, and dedicated bearer settings
  • SGSN serving GPRS support no
  • S-GW hosts can be based on per-user packet filtering (eg, through deep packet inspection), legal blocking, terminal IP (Internet protocol) address assignment, transport level packing marking in DL, UL / DL service level charging, gating and It provides various functions of class enforcement, DL class enforcement based on APN-AMBR.
  • MME / S-GW 30 is simply represented as a "gateway", which may include both MME and S-GW.
  • An interface for user traffic transmission or control traffic transmission may be used.
  • the terminal 10 and the eNB 20 may be connected by the Uu interface.
  • the eNBs 20 may be interconnected by an X2 interface. Neighboring eNBs 20 may have a mesh network structure by the X2 interface.
  • the eNBs 20 may be connected with the EPC by the S1 interface.
  • the eNBs 20 may be connected to the EPC by the S1-MME interface and may be connected to the S-GW by the S1-U interface.
  • the S1 interface supports a many-to-many-relation between eNB 20 and MME / S-GW 30.
  • the eNB 20 may select for the gateway 30, routing to the gateway 30 during radio resource control (RRC) activation, scheduling and transmission of paging messages, scheduling channel information (BCH), and the like.
  • RRC radio resource control
  • BCH scheduling channel information
  • the gateway 30 may perform paging initiation, LTE idle state management, user plane encryption, SAE bearer control, and encryption and integrity protection functions of NAS signaling in the EPC.
  • EPC Evolved Packet Core
  • MME mobility management entity
  • S-GW serving gateway
  • P-GW packet data network gateway
  • 5G core network or NextGen core network
  • a function, a reference point, and a protocol are defined for each network function (NF). That is, 5G core network does not define functions, reference points, protocols, etc. for each entity.
  • the RAN may be a base station using a new RAT.
  • 5G RAN, RAN, base station, RAN node, gNB, Next Generation NodeB, New RAN and NR BS may refer to a base station newly defined for 5G.
  • the AN may be a general base station including a non-3GPP access technology such as Wi-Fi.
  • An NG2 reference point may be defined between the RAN (or AN) and the Access and Mobility Function (AMF).
  • An NG3 reference point may be defined between the RAN (or AN) and the user plane function (UPF).
  • Control plane functions may include various functions for controlling the network and the terminal.
  • the CP function may include an AMF responsible for mobility management function and a session management function (SMF) for session management function. Since the AMF provides a function independent of the access technology (that is, a terminal-based access and mobility management function), each terminal may be basically connected to one AMF. On the other hand, in the case of SMF, a different SMF may be allocated to each terminal having multiple sessions.
  • the application function may provide information on packet flow to a policy control function (PCF) in charge of policy control to ensure quality of service (QoS). Based on this, the PCF may determine a policy such as session management, mobility management, and the like, and deliver the policy to AMF, SMF, etc., and thus, proper mobility management, session management, and QoS management may be performed.
  • PCF policy control function
  • QoS quality of service
  • the data network may transmit a protocol data unit (PDU) to be transmitted in the downlink direction to the UPF or may receive the PDU sent by the terminal through the UPF.
  • PDU protocol data unit
  • An NG6 reference point may be defined between the UPF and the data network.
  • the NG4 reference point may be defined so that the UPF may be set using the control signal information generated in the SMF, and the UPF may report its status to the SMF.
  • An NG1 reference point may be defined between the terminal and the AMF.
  • the authentication server function (AUSF) may store data for authentication of the terminal, and the user data management (UDM) may store subscription data, policy data, and the like of the user.
  • 5G RAN is a non-centralized deployment scenario and co-sited deployment according to the type of base station functions deployed in a central unit and a distributed unit, and coexistence with 4G base stations. It may be divided into a Deployment with E-UTRA scenario and a Centralized Deployment scenario.
  • 5G RAN, gNB, Next Generation NodeB, New RAN, and NR BS New Radio Base Station
  • 5G RAN, gNB, Next Generation NodeB, New RAN, and NR BS New Radio Base Station
  • the basic functions to be supported by the 5G RAN may be defined as shown in Table 1.
  • gNBs may be configured horizontally rather than hierarchically separated like a central unit and a distributed unit. In this case, a full set of protocol stacks may be supported for each gNB.
  • Integrated base station deployment scenarios may be suitable for macro cell or indoor hotspot environments.
  • the gNB may be directly connected with another gNB or eLTE eNB via an Inter-BS Interface.
  • the gNB may be directly connected with the core network through the RAN-CN interface.
  • a 5G transmission scheme eg, New Radio
  • a 4G transmission scheme eg, E-UTRA
  • Co-located deployment scenarios may be appropriate for an Urban Macro environment.
  • the base station configuration is adjusted by using load balancing and multi-connectivity, all the frequency resources allocated to 4G / 5G can be utilized, and the cell boundary using low frequency is used. Cell coverage may be extended for subscribers located at.
  • FIG 5 shows a scenario of a separated base station deployment (Centralized Deployment).
  • the gNB may be divided into a central unit and a distribution unit. That is, gNB may be separated and operated hierarchically.
  • the central unit may perform the function of the upper layers of the base station, and the distributed unit may perform the function of the lower layers of the base station.
  • the high performance transport type and the low performance transport type may be classified according to transmission capacity and delay characteristics of the transport equipment connecting the central unit and the distributed unit.
  • the central unit accommodates many functions from the upper layer to the lower layer, while the distributed unit accommodates only some of the lower layer functions that are relatively smaller than the central unit.
  • the processing burden of the central unit may be heavy and it may be difficult to meet the requirements for transmission capacity or delay and synchronization of the transport equipment.
  • the transmission equipment is estimated to have a transmission band of 157 Gbps and a maximum delay of 250 us.
  • Port equipment requires high capacity and low latency optical networks.
  • the transmission delay is short, there is an advantage that cooperative communication between base stations (for example, CoMP) can be more easily realized by using an optimal scheduling technique.
  • the central unit accommodates higher layer protocol functionality with less processing overhead, leaving room for transmission capacity and delay in transport equipment.
  • RRC layer the upper layer
  • PDCP layer to RF the transmission band of the transport equipment is 3 to 4 Gbps, maximum Since the delay is estimated to be 10ms, there is a margin in transmission band and delay compared to a transport requiring high performance.
  • a key distinguishing feature of 5G systems is the flexibility and adaptability of network functions and services.
  • One of the main concepts for achieving this flexibility is network slicing.
  • Network slicing can efficiently support various requirements for the network.
  • Network slicing refers to separating a single physical network into a plurality of logical networks composed of specific network functions to provide various services of heterogeneous characteristics. At this time, isolation between different network slices may be required so that the service provided by one network slice does not affect the service provided by another network slice.
  • service for a user may be provided by one network slice operated by a network operator.
  • a particular user may simultaneously access more than one network slice in order to take advantage of more diverse services, such as Mobile Broad Band (MBB), Critical Communication, or the like.
  • MBB Mobile Broad Band
  • Critical Communication Critical Communication
  • FIG. 6 shows an example where a network is sliced.
  • one physical network supports slice 1 for supporting a smartphone, slice 2 for supporting autonomous driving, slice 3 for supporting a massive IoT, and other services.
  • Slice into logical networks such as other slices for For example, when the network is requested for autonomous driving service, the slice 2 may be selected.
  • Each slice is guaranteed resources (eg, resources in virtualized servers and virtualized network resources).
  • resources eg, resources in virtualized servers and virtualized network resources.
  • each slice is isolated from each other, even if an error or failure occurs in a specific slice, communication of other slices is not affected. For example, even if a failure occurs in slice 1 for supporting a smartphone, the autonomous driving service and the Massive IoT service may be normally performed because the failure occurring in slice 1 does not affect other slices.
  • FIG. 7 illustrates an example of sharing a set of common C-plane functions among multiple core network instances.
  • the principle of the solution shown in FIG. 7 is as follows.
  • the core network instance consists of a single set of C-Plane functions and a single set of U-Plane functions.
  • the core network instance is dedicated for terminals belonging to the same terminal type. Identifying the terminal type is completed using specific parameters. For example, certain parameters are information from the UE usage type, and / or subscription of the terminal.
  • the set of C-Plane functions serves to support terminal mobility if required, or to authorize the terminal to the network by performing authentication and subscription verification.
  • the set of U-Plane functions in the core network instance provides a specific service to the UE and transmits U-Plane data of the specific service.
  • one set of U-Plane functionality in Core Network Instance # 1 provides an enhanced mobile broadband service to the terminal
  • another set of U-Plane functionality in Core Network Instance # 2 provides the terminal with important communication services. .
  • Each terminal may have a plurality of U-Plane connections for different sets of U-Plane functions simultaneously available in different core network instances.
  • the network slice selection function serves to select a core network instance to accommodate the terminal by considering the subscription of the terminal and a specific parameter (eg, terminal usage type).
  • C-Plane selection function serves to select the C-Plane function within the selected core network instance with which the base station should communicate. This selection of the C-Plane function is completed using specific parameters (eg terminal usage type).
  • 8 and 9 illustrate examples of signal flows for supporting a connection with a plurality of core network instances.
  • 8 shows an MM attach management procedure.
  • 9 shows a session management (SM) procedure.
  • the SM procedure shown in FIG. 9 may be performed.
  • the common C-Plane function (C-CPF) may be called another name, for example, an access and mobility management function (AMF).
  • the control plane function (ie, CNI-1 CPF-1 or CNI-2 CPF-2) in the core network instance may be called another name, for example, a session management function (SMF).
  • step S800 when the terminal first connects to the operator's network, the terminal sends a network connection request to the RAN node.
  • the RAN node may be a gNB that may have similar functionality as an eNB in LTE. If the terminal provides the RAN node with enough information to route the message to the appropriate core network instance and its corresponding C-Plane function, the RAN node routes the request to the C-Plane function. Thus, the flow continues at step S830 to be described later. Otherwise, the RAN node sends a connection request to NSSF / CPSF, and the flow continues at step S810.
  • the NSSF / CPSF determines the core network instance to be connected and the corresponding C-Plane function (s) by considering the information in the request from the terminal in step S800. In addition, other information may be considered from the subscription database.
  • the core network instance to be connected is core network instance # 1.
  • step S820 NSSF / CPSF transmits a response to the RAN node having the C-Plane function of the selected core network instance # 1.
  • step S830 based on the response sent in step S820, the RAN node selects the C-Plane function of the selected core network instance # 1.
  • step S840 the RAN node delivers a network connection request of the terminal to C-CPF-1, which is the C-Plane function selected in steps S820 and S830.
  • step S850 authentication and accepting of the terminal to the core network instance # 1 are performed.
  • step S900 the terminal requests a communication service (eg, service # 1 provided by the core network instance # 1).
  • a communication service eg, service # 1 provided by the core network instance # 1).
  • step S910 the RAN node forwards a request for service to C-CPF-1.
  • step S920 the C-CPF-1 selects the C-Plane function of the core network instance # 1, and the UE for the service # 1 to the CPF-1 in the core network instance # 1 (that is, the CNI-1 CPF-1). Forward the request.
  • step S930 after successful session establishment, CPF-1 in core network instance # 1 sends back a session response to C-CPF-1.
  • step S940 C-CPF-1 sends a new service response back to the terminal via the RAN node.
  • step S950 the terminal requests a new communication service that is a different service type from the previous service.
  • step S960 the RAN node forwards a request for a new communication service to C-CPF-1.
  • step S970 the C-CPF-1 selects the C-Plane function of the core network instance # 2, and sends a request of the terminal for the new service to the CPF- in the core network instance # 2 (ie, CNI-2 CPF-1). Pass it to 1.
  • step S980 after successful session establishment, CPF-1 in network instance # 2 returns a session response back to C-CPF-1.
  • step S990 C-CPF-1 sends a new service response back to the terminal through the RAN node.
  • a procedure for transmitting an attach request of a UE to a common core network instance selected by NSSF / CPSF is not defined.
  • the terminal may not know whether the attach request of the terminal has been accepted by the network.
  • the terminal cannot know which slice is selected in response to the requested service. Therefore, in the MM attach procedure, a procedure for transmitting the attach request of the terminal to the common core network instance selected by the NSSF / CPSF needs to be newly proposed.
  • a procedure for receiving information on the slice selected by the terminal and the base station in response to the requested service needs to be proposed.
  • FIG. 10 illustrates an initial MM attach procedure according to an embodiment of the present invention.
  • the terminal may initiate an MM attach.
  • the terminal may transmit an attach request to the base station.
  • the base station may be a gNB.
  • the temporary ID IE may be transmitted to the base station.
  • the temporary ID IE may be defined similarly to the SAE-Temporary Mobile Subscriber Identity (S-TMSI) IE of LTE. That is, the temporary ID may include information about a common control plane function (C-CPF).
  • C-CPF common control plane function
  • a common control plane function, a common core network instance, a common control plane function for a core network instance, a common core network slice may be used in the same concept.
  • the base station may assign a unique ID to be used for the terminal.
  • the unique ID assigned by the base station may be referred to as gNB UE CP NG1AP ID.
  • the gNB UE CP NG1AP ID may be an ID similar to an eNB UE S1AP ID defined in Section 9.2.3.4 of 3GPP TS 36.413 V12.6.0 (2015-06).
  • the eNB UE S1AP ID may uniquely identify a UE association through an S1 interface in an eNB.
  • the gNB UE CP NG1AP ID may uniquely identify the terminal association over the NG1 interface in the gNB.
  • the base station When the base station receives the temporary ID IE from the terminal, the base station may transmit the attach request received in step S1010 to the common control plane function indicated by the temporary ID IE. Therefore, in step S1020 to be described below, the procedure for selecting a network slice by the NSSF and step S1030 may be omitted.
  • the base station may request NSSF and CPSF to determine in which slice the attach request of the terminal should be delivered. If the base station has not received the temporary ID IE from the terminal, the base station may request the NSSF and CPSF to determine in which slice the attach request of the terminal should be delivered. Alternatively, even when the base station receives the temporary ID IE from the terminal, if the base station is not sufficient to select a common control plane function based on the temporary ID IE, the base station attaches the terminal to NSSF and CPSF. You can request to decide on which slice the request should be delivered. In order for the NSSF and the CPSF to select an appropriate slice for the terminal, the base station may transmit the information received from the terminal to the NSSF and the CPSF.
  • the information received from the terminal may be a UE service type (ie, a type of service desired by the terminal).
  • Other information from the subscription database can be considered in NSSF and CPSF.
  • the NSSF may determine a common core network instance for the terminal and send the selected slice ID to the base station. For example, in FIG. 10, the NSSF may determine the common core network instance # 1 for the terminal and may transmit the ID of the core network instance # 1 to the base station.
  • step S1030 based on the response from the NSSF, the base station may select the common control plane function of the selected common core network instance. For example, in FIG. 10, the base station may select C-CPF-1 to transmit an attach request of the terminal. If the base station receives the temporary ID IE from the terminal in step S1010, step S1030 may be omitted.
  • the base station may transmit a message to a common control plane function of the common core network instance selected in operation S1030 to transmit an attach request of the terminal.
  • the base station may transmit a message to the selected C-CPF-1 in step S1030.
  • the message may be an initial UE message or a new message.
  • the message may include an identity (eg, ECGI in LTE) and a tracking area identity (TAI) of a cell in which the terminal transmits a NAS message.
  • the message may include a NAS-PDU IE including an attach request.
  • the message may include a gNB UE CP NG1AP ID IE.
  • the message may include an RRC Establishment Cause IE. If the base station receives the temporary ID from the terminal, the temporary ID may be transmitted to the selected common core network instance.
  • the common core network instance may assign a unique ID to be used for the terminal.
  • the unique ID assigned by the common core network instance may be referred to as a 5G Core UE CP NG1AP ID.
  • the 5G Core UE CP NG1AP ID may uniquely identify the terminal association over the NG1 interface in the 5G core.
  • step S1050 authorization and authentication may be performed for the terminal.
  • step S1060 after the authorization and authentication is performed for the terminal, the selected common control plane function (ie, C-CPF-1) attach notification to inform the terminal whether the attach request has been accepted (attach response) May be transmitted to the base station.
  • the attach response may be included in an initial connection setup indication message or a new message and transmitted to the base station.
  • the initial connection setup indication message or new message may include a NAS-PDU IE including an ID of the selected network slice, a 5G Core UE CP NG1AP ID IE, and an attach response.
  • the ID of the network slice may be selected by the NSSF or the base station.
  • the network slice may mean a common core network slice. If the temporary ID IE is not received from the terminal during the MME attach procedure, the common core network instance may allocate a value for identifying the UE context in the network. The common core network instance may deliver the assigned value to the terminal.
  • step S1070 when the base station receives the ID of the selected common core network slice from the selected common control plane function, the base station may transmit the ID of the selected common core network slice to the terminal. Additionally, when the base station receives the attach response from the selected common control plane function, the base station may transmit the received attach response to the terminal. Additionally, when the base station receives the 5G Core UE CP NG1AP ID IE from the selected common control plane function, the base station may establish a UE-associated logical NG1-connection. The terminal related logical NG1 connection may be a reference point between the terminal and the selected common control plane function.
  • FIG. 11 is a block diagram illustrating a method for a base station to receive an ID of a common control plane function according to an embodiment of the present invention.
  • the base station may select a common control plane function.
  • the common control plane function may be an access and mobility function (AMF).
  • the base station may receive an ID of the selected common control plane function from the selected common control plane function.
  • the base station may transmit the ID of the received common control plane function to the terminal.
  • the base station receives an attach request from the terminal, and the access request may include information on service desired by the UE.
  • the selected common control plane function may be selected based on the connection request.
  • the selected common control plane function may be a common control plane function corresponding to a network slice providing a service desired by the terminal.
  • the base station may assign a first unique ID to the terminal that transmitted the access request.
  • the base station may send the assigned first unique ID to the selected common control plane function.
  • the base station may receive a second unique ID from the selected common control plane function, wherein the second unique ID may be assigned to the terminal that has transmitted the access request by the selected common control plane function. .
  • the base station establishes a UE-associated logical NG1-connection, wherein the terminal-related logical NG1 connection is controlled by the terminal and the selected common control. It may be a reference point between planar functions.
  • the base station may receive a temporary ID including information on the common control plane function from the terminal.
  • the selected common control plane function may be selected based on the temporary ID.
  • the base station may transmit an attach request of the terminal to the selected common core network instance.
  • the selected common control plane function may transmit the selected common core network slice ID to the base station, and the base station may transmit the selected common core network slice ID to the terminal. . Accordingly, the terminal may know which slice is selected in response to an attach request or a service request of the terminal.
  • FIG. 12 is a block diagram of a wireless communication system in which an embodiment of the present invention is implemented.
  • the base station 1200 includes a processor 1201, a memory 1202, and a transceiver 1203.
  • the memory 1202 is connected to the processor 1201 and stores various information for driving the processor 1201.
  • the transceiver 1203 is connected to the processor 1201 to transmit and / or receive a radio signal.
  • Processor 1201 implements the proposed functions, processes, and / or methods. In the above-described embodiment, the operation of the base station may be implemented by the processor 1201.
  • the terminal 1210 includes a processor 1211, a memory 1212, and a transceiver 1213.
  • the memory 1212 is connected to the processor 1211 and stores various information for driving the processor 1211.
  • the transceiver 1213 is connected to the processor 1211 to transmit and / or receive a radio signal.
  • Processor 1211 implements the proposed functions, processes, and / or methods. In the above-described embodiment, the operation of the terminal may be implemented by the processor 1211.
  • the processor may include application-specific integrated circuits (ASICs), other chipsets, logic circuits, and / or data processing devices.
  • the memory may include read-only memory (ROM), random access memory (RAM), flash memory, memory card, storage medium and / or other storage device.
  • the transceiver may include baseband circuitry for processing wireless signals.
  • the above-described technique may be implemented as a module (process, function, etc.) for performing the above-described function.
  • the module may be stored in memory and executed by a processor.
  • the memory may be internal or external to the processor and may be coupled to the processor by various well known means.

Landscapes

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

Abstract

La présente invention a trait un procédé de réception d'une identification (ID) d'une fonction de plan de commande (CP) commun par une station de base dans un système de communication sans fil et à un appareil prenant en charge ce procédé. Le procédé peut comprendre les étapes consistant à : sélectionner une fonction de CP commun ; recevoir, en provenance de la fonction sélectionnée de CP commun, une ID de la fonction sélectionnée de CP commun ; et transmettre à un terminal l'ID reçue de la fonction de CP commun.
PCT/KR2017/006015 2016-06-10 2017-06-09 Procédé et appareil de réception d'une identification de fonction de plan de commande commun WO2017213457A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201662348182P 2016-06-10 2016-06-10
US62/348,182 2016-06-10
US201662368155P 2016-07-28 2016-07-28
US62/368,155 2016-07-28

Publications (1)

Publication Number Publication Date
WO2017213457A1 true WO2017213457A1 (fr) 2017-12-14

Family

ID=60578843

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2017/006015 WO2017213457A1 (fr) 2016-06-10 2017-06-09 Procédé et appareil de réception d'une identification de fonction de plan de commande commun

Country Status (1)

Country Link
WO (1) WO2017213457A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101268440B1 (ko) * 2011-10-31 2013-06-04 한국과학기술정보연구원 글로벌 네트워크 슬라이스 관리 시스템 및 그 방법

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101268440B1 (ko) * 2011-10-31 2013-06-04 한국과학기술정보연구원 글로벌 네트워크 슬라이스 관리 시스템 및 그 방법

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"Consideration on Network Slice Selection", R3-160755, 3GPP TSG RAN WG3 MEETING #91BIS, 2 April 2016 (2016-04-02), Bangalore, India, XP051083024, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG3_Iu/TSGR3_91bis/Docs> *
"Consideration on Network Slice Selection", R3-161237, 3GPP TSG RAN WG3 MEETING #92, 14 May 2016 (2016-05-14), Nanjing, China, XP051106039, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG3_Iu/TSCR3_92/Docs> *
NOKIA ET AL.: "Key Principles for Slice Selection Support in RAN", R3-160735, 3GPP TSG RAN WG3 MEETING #91BIS, 1 April 2016 (2016-04-01), Bangalore, India, XP051082918, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG3_Iu/TSGR3_91bis/Docs> *
ZTE: "Network Slice Selection Procedure", R3-161107, 3GPP TSG RAN WG3 MEETING #92, 13 May 2016 (2016-05-13), Nanjing, China, XP051105915, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG3_Iu/TSGR3_92/Docs> *

Similar Documents

Publication Publication Date Title
WO2017171354A1 (fr) Procédé et dispositif par lesquels un terminal réalise une mobilité
US9967801B2 (en) Method and apparatus for receiving authorization information on network slice
US11363435B2 (en) Network slicing-aware access network
WO2018080218A1 (fr) Procédé et appareil d&#39;établissement de support
WO2021066587A1 (fr) Appareil et procédé d&#39;abonnement à un service par l&#39;intermédiaire d&#39;une interface e2 dans un système de communication de réseau d&#39;accès radio
CN108307472B (zh) 设备直通系统的通信方法及装置、通信系统
WO2018182231A1 (fr) Procédé pour effectuer une récupération de mcg dans une connectivité double dans un système de communication sans fil et dispositif associé
WO2018208114A1 (fr) Procédé et appareil d&#39;attribution de ressource de liaison latérale à l&#39;aide d&#39;un ue de relais dans un système de communication sans fil
WO2018131902A1 (fr) Procédé permettant de transmettre un paquet de liaison montante (ul) en se basant sur un flux de qualité de service (qos) dans un système de communication et dispositif s&#39;y rapportant
WO2018021861A1 (fr) Procédé et appareil pour effectuer une procédure de spécification de cellule pour un nr basé sur une tranche de réseau dans un système de communication sans fil
WO2017196056A2 (fr) Procédé et appareil de demande de sib dans un système de communication sans fil
WO2019022397A1 (fr) Procédé permettant de modifier une porteuse radio dans un scénario de division d&#39;unité cu-du
WO2021066588A1 (fr) Appareil et procédé d&#39;abonnement à un service, utilisant une interface e2 dans un système de communication de réseau d&#39;accès sans fil
WO2021118281A1 (fr) Appareil et procédé de configuration d&#39;interface e2 incluant des informations de cellule dans un réseau d&#39;accès sans fil
WO2017155361A1 (fr) Procédé et dispositif d&#39;attribution de ressources permettant une communication v2x
WO2017052103A1 (fr) Procédé de gestion de collision id pour un système de communication d2d, et dispositif associé
WO2017135740A1 (fr) Procédé et appareil pour la mise en œuvre de communications v2x
WO2018164431A1 (fr) Procédé et dispositif pour effectuer une coordination d&#39;interférence par tranche
WO2010151047A2 (fr) Appareil et procédé pour établir un support radio dans un système de communication sans fil
WO2018131935A1 (fr) Procédé de communication sans fil basé sur une proximité et équipement utilisateur
WO2018143585A1 (fr) Procédé et dispositif de transmission de liaison montante
WO2017022958A1 (fr) Procédé de réception d&#39;une priorité pour des données relais dans un système de communication d2d, et dispositif associé
WO2019054841A1 (fr) Procédé permettant de mettre en œuvre une qualité de service réfléchissante dans un système de communication sans fil, et dispositif associé
WO2018139829A1 (fr) Procédé pour réaliser la gestion de différents identifiants dans un ue relais d&#39;un système de communication sans fil et dispositif associé
WO2017171355A2 (fr) Procédé et appareil permettant d&#39;acquérir des informations système

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17810580

Country of ref document: EP

Kind code of ref document: A1