WO2021125691A1 - Commutation de trajet de communication - Google Patents

Commutation de trajet de communication Download PDF

Info

Publication number
WO2021125691A1
WO2021125691A1 PCT/KR2020/018001 KR2020018001W WO2021125691A1 WO 2021125691 A1 WO2021125691 A1 WO 2021125691A1 KR 2020018001 W KR2020018001 W KR 2020018001W WO 2021125691 A1 WO2021125691 A1 WO 2021125691A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdu session
interface
switching
request message
information
Prior art date
Application number
PCT/KR2020/018001
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 WO2021125691A1 publication Critical patent/WO2021125691A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H04W36/00695—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink using split of the control plane or user plane
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H04W36/00698—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink using different RATs
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H04W36/144—Reselecting a network or an air interface over a different radio air interface technology
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/25—Maintenance of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management

Definitions

  • This specification relates to mobile communication.
  • New RAT new radio access technology
  • a wireless communication device such as a UE may communicate with another wireless communication device via a Uu interface or via a PC5 interface. Communication performed through the PC5 interface may be performed through a PC5 communication link established between wireless communication devices. In addition, communication performed through the Uu interface may be performed through a network in which each wireless communication device is connected to a data session (eg, a protocol data unit (PDU) session) established with a network.
  • a data session eg, a protocol data unit (PDU) session
  • wireless communication devices While wireless communication devices communicate with each other through the PC5 interface, there may be a case in which the wireless communication devices need to switch to communication through the Uu interface. Conversely, while wireless communication devices communicate with each other through the Uu interface, there may be a case in which the wireless communication devices need to switch to communication through the PC5 interface.
  • the network node includes at least one processor; and at least one memory for storing instructions and operably electrically connectable with the at least one processor, wherein the operations performed based on the instructions being executed by the at least one processor include: a first Receiving, from the UE, a PDU session establishment request message requesting establishment of a PDU session; and transmitting a PDU session establishment acceptance message including switching rule information to the first UE.
  • Radio Interface Protocol Radio Interface Protocol
  • 5A and 5B are signal flow diagrams illustrating an exemplary registration procedure.
  • FIG. 11 shows a signal flow diagram according to a first example of a discovery procedure of the disclosure of the present specification.
  • FIG. 14 illustrates a block diagram of a network node according to an embodiment.
  • FIG 17 illustrates a communication system 1 applied to the disclosure of the present specification.
  • a or B (A or B) may mean “only A”, “only B” or “both A and B”.
  • a or B (A or B)” may be interpreted as “A and/or B (A and/or B)”.
  • A, B or C(A, B or C) herein means “only A”, “only B”, “only C”, or “any and any combination of A, B and C ( any combination of A, B and C)”.
  • At least one of A and B may mean “only A”, “only B” or “both A and B”.
  • the expression “at least one of A or B” or “at least one of A and/or B” means “at least one It can be interpreted the same as “at least one of A and B”.
  • parentheses used herein may mean “for example”. Specifically, when displayed as “control information (PDCCH)”, “PDCCH” may be proposed as an example of “control information”. In other words, “control information” of the present specification is not limited to “PDCCH”, and “PDDCH” may be proposed as an example of “control information”. Also, even when displayed as “control information (ie, PDCCH)”, “PDCCH” may be proposed as an example of “control information”.
  • UE user equipment
  • ME mobile equipment
  • the illustrated UE may be referred to as a terminal, mobile equipment (ME), and the like.
  • the UE may be a portable device such as a notebook computer, a mobile phone, a PDA, a smart phone, a multimedia device, or the like, or a non-portable device such as a PC or a vehicle-mounted device.
  • FIG. 1 is a structural diagram of a next-generation mobile communication network.
  • 5GC may include various components, and in FIG. 1 , AMF (Access and Mobility Management Function) 410 and SMF (Session Management Function: Session Management) corresponding to some of them Function) (420) and PCF (Policy Control Function) (430), UPF (User Plane Function) (440), AF (Application Function: Application Function) (450), UDM (Unified Data) Management: Unified Data Management) 460 , and 3rd Generation Partnership Project (N3IWF) Inter Working Function (N3IWF) 490 .
  • AMF Access and Mobility Management Function
  • SMF Session Management Function: Session Management
  • PCF Policy Control Function
  • UPF User Plane Function
  • AF Application Function
  • UDM Unified Data Management: Unified Data Management
  • N3IWF 3rd Generation Partnership Project
  • the UE 100 is connected to a data network via the UPF 440 through a Next Generation Radio Access Network (NG-RAN) including the gNB 20 .
  • NG-RAN Next Generation Radio Access Network
  • the UE 100 may be provided with a data service through untrusted non-3GPP access, for example, a wireless local area network (WLAN).
  • a wireless local area network WLAN
  • an N3IWF 490 may be deployed.
  • the illustrated N3IWF 490 performs a function of managing interworking between non-3GPP access and 5G systems.
  • the UE 100 When the UE 100 is connected to non-3GPP access (e.g., WiFi referred to as IEEE 801.11), the UE 100 may be connected to the 5G system through the N3IWF 490 .
  • the N3IWF 490 performs control signaling with the AMF 410 and is connected to the UPF 440 through the N3 interface for data transmission.
  • the illustrated AMF 410 may manage access and mobility in a 5G system.
  • the AMF 410 may perform a function of managing Non-Access Stratum (NAS) security.
  • the AMF 410 may perform a function of handling mobility in an idle state.
  • NAS Non-Access Stratum
  • the illustrated UPF 440 is a type of gateway through which user data is transmitted and received.
  • the UPF node 440 may perform all or part of the user plane functions of a Serving Gateway (S-GW) and a Packet Data Network Gateway (P-GW) of 4G mobile communication.
  • S-GW Serving Gateway
  • P-GW Packet Data Network Gateway
  • the UPF 440 is an element that operates as a boundary point between the next generation RAN (NG-RAN) and the core network and maintains a data path between the gNB 20 and the SMF 420 . Also, when the UE 100 moves over an area served by the gNB 20 , the UPF 440 serves as a mobility anchor point.
  • the UPF 440 may perform a function of handling PDUs. For mobility within NG-RAN (Next Generation-Radio Access Network defined after 3GPP Release-15), UPF packets can be routed.
  • NG-RAN Next Generation-Radio Access Network defined after 3GPP Release-15
  • the UPF 440 is another 3GPP network (RAN defined before 3GPP Release-15, for example, UTRAN, E-UTRAN (Evolved-Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network)) or GERAN (GSM (GSM)). It may function as an anchor point for mobility with Global System for Mobile Communication/EDGE (Enhanced Data rates for Global Evolution) Radio Access Network). UPF 440 may correspond to a termination point of a data interface towards a data network.
  • UTRAN Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network)
  • GSM GSM
  • UPF 440 may correspond to a termination point of a data interface towards a data network.
  • the illustrated PCF 430 is a node that controls the operator's policy.
  • the illustrated AF 450 is a server for providing various services to the UE 100 .
  • the illustrated UDM 460 is a kind of server that manages subscriber information, like a home subscriber server (HSS) of 4G mobile communication.
  • the UDM 460 stores and manages the subscriber information in a Unified Data Repository (UDR).
  • UDR Unified Data Repository
  • the illustrated SMF 420 may perform a function of allocating an Internet Protocol (IP) address of the UE.
  • the SMF 420 may control a protocol data unit (PDU) session.
  • IP Internet Protocol
  • PDU protocol data unit
  • 5G mobile communication supports multiple numerology or subcarrier spacing (SCS) to support various 5G services. For example, when SCS is 15kHz, it supports a wide area in traditional cellular bands, and when SCS is 30kHz/60kHz, dense-urban, lower latency and a wider carrier bandwidth, and when the SCS is 60 kHz or higher, a bandwidth greater than 24.25 GHz to overcome phase noise.
  • SCS subcarrier spacing
  • FR1 may include a band of 410 MHz to 7125 MHz as shown in Table 2 below. That is, FR1 may include a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher. For example, a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) included in FR1 may include an unlicensed band. The unlicensed band may be used for various purposes, for example, for communication for a vehicle (eg, autonomous driving).
  • next-generation mobile communication is an exemplary diagram illustrating an expected structure of next-generation mobile communication from a node perspective.
  • the UE is connected to a data network (DN) through a next-generation RAN (Radio Access Network).
  • DN data network
  • next-generation RAN Radio Access Network
  • the illustrated control plane function (CPF) node is all or part of the functions of the MME (Mobility Management Entity) of the 4th generation mobile communication, and the control plane functions of the Serving Gateway (S-GW) and the PDN Gateway (P-GW). carry out all or part of The CPF node includes an Access and Mobility Management Function (AMF) and a Session Management Function (SMF).
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • P-GW PDN Gateway
  • the illustrated PCF Policy Control Function
  • Policy Control Function is a node that controls the operator's policy.
  • the illustrated application function (Application Function: AF) is a server for providing various services to the UE.
  • the illustrated Authentication Server Function authenticates and manages the UE.
  • the illustrated Network Exposure Function is a node for providing a mechanism for securely exposing the services and functions of the 5G core.
  • the NEF exposes functions and events, securely provides information from external applications to the 3GPP network, translates internal/external information, provides control plane parameters, and provides packet flow description (PFD). ) can be managed.
  • PFD packet flow description
  • a UE may simultaneously access two data networks using multiple protocol data unit or packet data unit (PDU) sessions.
  • PDU packet data unit
  • 3 shows an architecture for supporting simultaneous access to two data networks; is an example .
  • FIG 3 shows an architecture for a UE to simultaneously access two data networks using one PDU session.
  • N1 represents a reference point between the UE and the AMF.
  • N3 represents the reference point between (R)AN and UPF.
  • N4 represents a reference point between SMF and UPF.
  • N5 represents the reference point between PCF and AF.
  • N6 represents a reference point between UPF and DN.
  • N8 represents a reference point between UDM and AMF.
  • N10 represents a reference point between the UDM and the SMF.
  • N12 represents a reference point between AMF and AUSF.
  • N14 represents a reference point between AMFs.
  • N15 represents a reference point between the PCF and the AMF in a non-roaming scenario, and a reference point between the AMF and the PCF of a visited network in a roaming scenario.
  • N16 represents a reference point between SMFs.
  • N30 represents a reference point between the PCF and the NEF.
  • N33 denotes a reference point between AF and NEF.
  • AF by a third party other than an operator may be connected to 5GC through NEF.
  • the air interface protocol is based on the 3GPP radio access network standard.
  • the air interface protocol is horizontally composed of a physical layer, a data link layer, and a network layer, and vertically a user plane for data information transmission and control. It is divided into a control plane for signal transmission.
  • the protocol layers are L1 (first layer), L2 (second layer), and L3 (third layer) based on the lower three layers of the Open System Interconnection (OSI) reference model widely known in communication systems. ) can be distinguished.
  • OSI Open System Interconnection
  • the first layer provides an information transfer service using a physical channel.
  • the physical layer is connected to an upper medium access control layer through a transport channel, and data between the medium access control layer and the physical layer is transmitted through the transport channel. And, data is transferred between different physical layers, that is, between the physical layers of the transmitting side and the receiving side through a physical channel.
  • the second layer includes a Medium Access Control (MAC) layer, a Radio Link Control (RLC) layer, and a Packet Data Convergence Protocol (PDCP) layer.
  • MAC Medium Access Control
  • RLC Radio Link Control
  • PDCP Packet Data Convergence Protocol
  • the NAS (Non-Access Stratum) layer performs functions such as connection management (session management) and mobility management (Mobility Management).
  • the NAS layer is divided into a NAS entity for MM (Mobility Management) and a NAS entity for SM (session management).
  • NAS entity for MM provides the following general functions.
  • NAS procedures related to AMF including the following.
  • AMF supports the following functions.
  • the NAS entity for SM performs session management between the UE and the SMF.
  • the SM signaling message is processed, ie, generated and processed in the NAS-SM layer of the UE and SMF.
  • the content of the SM signaling message is not interpreted by the AMF.
  • the NAS entity for MM creates a NAS-MM message that derives how and where to forward the SM signaling message with a security header indicating the NAS transmission of the SM signaling, additional information about the receiving NAS-MM.
  • the NAS entity for the SM Upon receiving the SM signaling, the NAS entity for the SM performs an integrity check of the NAS-MM message, and interprets the additional information to derive a method and a place to derive the SM signaling message.
  • the RRC layer, the RLC layer, the MAC layer, and the PHY layer located below the NAS layer are collectively referred to as an Access Stratum (AS).
  • AS Access Stratum
  • a network system (ie, 5GC) for next-generation mobile communication (ie, 5G) also supports non-3GPP access.
  • An example of the non-3GPP access is typically a WLAN access.
  • the WLAN access may include both a trusted WLAN and an untrusted WLAN.
  • AMF performs registration management (RM: Registration Management) and connection management (CM: Connection Management) for 3GPP access as well as non-3GPP access.
  • RM Registration Management
  • CM Connection Management
  • a Multi-Access (MA) PDU session using both 3GPP access and non-3GPP access may be used.
  • the MA PDU session is a PDU session that can be serviced simultaneously with 3GPP access and non-3GPP access using one PDU session.
  • the ID of the UE may be obtained from the UE.
  • AMF can pass PEI (IMEISV) to UDM, SMF and PCF.
  • PEI IMEISV
  • 5A and 5B are signal flow diagrams illustrating an exemplary registration procedure.
  • the registration type is "initial registration” (i.e. the UE is in a non-registered state), "Mobility registration update” (i.e. the UE is in a registered state and initiates the registration procedure due to mobility) or "periodic registration update” ( That is, the UE is in the registered state and starts the registration procedure due to the expiration of the periodic update timer).
  • the temporary user ID indicates the last serving AMF. If the UE is already registered through non-3GPP access in a PLMN different from the PLMN of 3GPP access, the UE may not provide the temporary ID of the UE assigned by AMF during the registration procedure through non-3GPP access.
  • Security parameters can be used for authentication and integrity protection.
  • the PDU session state may indicate a (previously established) PDU session usable in the UE.
  • the RAN may select an AMF based on (R)AT and NSSAI.
  • the (R)AN cannot select an appropriate AMF, it selects an arbitrary AMF according to a local policy, and transmits a registration request to the selected AMF. If the selected AMF cannot service the UE, the selected AMF selects another more suitable AMF for the UE.
  • the RAN transmits an N2 message to the new AMF.
  • the N2 message includes an N2 parameter and a registration request.
  • the registration request may include registration type, subscriber permanent identifier or temporary user ID, security parameters, NSSAI and MICO mode default settings, and the like.
  • the N2 parameters include location information related to the cell the UE is camping on, cell identifier and RAT type.
  • steps 4 to 17 to be described later may not be performed.
  • the newly selected AMF may transmit an information request message to the previous AMF.
  • the new AMF may send an information request message containing the complete registration request information to the old AMF to request the SUPI and MM context of the UE. have.
  • the previous AMF transmits an information response message to the newly selected AMF.
  • the information response message may include SUPI, MM context, and SMF information.
  • the previous AMF sends an information response message including the UE's SUPI and MM context.
  • the previous AMF may include SMF information including the ID of the SMF and the PDU session ID in the information response message.
  • the new AMF sends an Identity Request message to the UE if the SUPI is not provided by the UE or retrieved from the previous AMF.
  • AMF may decide to trigger AUSF.
  • the AMF may select the AUSF based on the SUPI.
  • AUSF may initiate authentication of UE and NAS security functions.
  • the new AMF may transmit an information response message to the previous AMF.
  • the new AMF may transmit the information response message to confirm delivery of the UE MM context.
  • the new AMF may transmit an Identity Request message to the UE.
  • an Identity Request message may be sent for the AMF to retrieve the PEI.
  • the new AMF checks the ME identifier.
  • step 14 described later the new AMF selects a UDM based on SUPI.
  • the AMF When network slicing is used, the AMF obtains the allowed NSSAI based on the requested NSSAI, UE subscription and local policy. Reroute registration requests if AMF is not eligible to support allowed NSSAI.
  • the new AMF transmits a UE Context Establishment Request message to the PCF.
  • the AMF may request an operator policy for the UE from the PCF.
  • the new AMF transmits an N11 response message to the SMF.
  • the previous AMF transmits a UE Context Termination Request message to the PCF.
  • the old AMF may delete the UE context in the PCF.
  • the PCF may transmit a UE Context Termination Request message to the previous AMF.
  • the new AMF sends a registration accept message to the UE.
  • the registration acceptance message may include temporary user ID, registration area, mobility restriction, PDU session status, NSSAI, regular registration update timer, and allowed MICO mode.
  • the registration accept message may include information of the allowed NSSAI and the mapped NSSAI.
  • the allowed NSSAI information for the access type of the UE may be included in the N2 message including the registration accept message.
  • the mapped NSSAI information is information that maps each S-NSSAI of the allowed NSSAI to the S-NASSI of the NSSAI configured for Home Public Land Mobile Network (HPLMN).
  • the temporary user ID may be further included in the registration acceptance message.
  • information indicating the mobility restriction may be additionally included in the registration accept message.
  • the AMF may include information indicating the PDU session state for the UE in the registration accept message. The UE may remove any internal resources associated with a PDU session that are not marked as active in the received PDU session state. If the PDU session state information is in the Registration Request, the AMF may include information indicating the PDU session state to the UE in the registration accept message.
  • the UE transmits a registration complete message to the new AMF.
  • PDU session establishment procedure two types of PDU session establishment procedures may exist as follows.
  • 6A and 6B are exemplary PDU It is a signal flow diagram showing the session establishment procedure.
  • the procedure shown in FIGS. 6A and 6B assumes that the UE has already registered on the AMF according to the registration procedure shown in FIGS. 5A and 5B . Therefore, it is assumed that AMF has already obtained user subscription data from UDM.
  • the UE sends a NAS message to the AMF.
  • the message may include Session Network Slice Selection Assistance Information (S-NSSAI), DNN, PDU session ID, request type, N1 SM information, and the like.
  • S-NSSAI Session Network Slice Selection Assistance Information
  • the UE includes the S-NSSAI from the allowed NSSAI of the current access type. If the information on the mapped NSSAI is provided to the UE, the UE may provide both the S-NSSAI based on the allowed NSSAI and the corresponding S-NSSAI based on the information of the mapped NSSAI.
  • the mapped NSSAI information is information that maps each S-NSSAI of the allowed NSSAI to the S-NASSI of the NSSAI configured for HPLMN.
  • the UE may generate a new PDU session ID.
  • the UE may start the PDU session establishment procedure initiated by the UE by sending a NAS message including the PDU session establishment request message in the N1 SM information.
  • the PDU session establishment request message may include a request type, an SSC mode, and a protocol configuration option.
  • the request type indicates "initial request”. However, if there is an existing PDU session between 3GPP access and non-3GPP access, the request type may indicate "existing PDU session”.
  • the NAS message transmitted by the UE is encapsulated in the N2 message by the AN.
  • the N2 message is transmitted to the AMF and may include user location information and access technology type information.
  • - N1 SM information may include an SM PDU DN request container including information on PDU session authentication by external DN.
  • the AMF may determine that the message corresponds to a request for a new PDU session when the message indicates that the request type is "initial request" and the PDU session ID is not used for the existing PDU session of the UE.
  • the AMF may determine the default S-NSSAI for the requested PDU session according to the UE subscription.
  • the AMF may store the PDU session ID and the SMF ID in association.
  • the AMF transmits the SM request message to the SMF.
  • the SM request message may include subscriber permanent ID, DNN, S-NSSAI, PDU session ID, AMF ID, N1 SM information, user location information, and access technology type.
  • the N1 SM information may include a PDU session ID and a PDU session establishment request message.
  • the AMF ID is used to identify the AMF serving the UE.
  • the N1 SM information may include a PDU session establishment request message received from the UE.
  • SMF transmits subscriber data request message to UDM.
  • the subscriber data request message may include a subscriber permanent ID and DNN.
  • the SMF determines that the request is due to handover between 3GPP access and non-3GPP access.
  • the SMF may identify an existing PDU session based on the PDU session ID.
  • the UDM may send a subscription data response message to the SMF.
  • the subscription data may include information about an authenticated request type, an authenticated SSC mode, and a basic QoS profile.
  • the SMF may check whether the UE request complies with user subscription and local policies. Alternatively, the SMF rejects the UE request through NAS SM signaling (including the relevant SM rejection cause) delivered by the AMF, and the SMF informs the AMF that the PDU session ID should be considered released.
  • NAS SM signaling including the relevant SM rejection cause
  • the SMF selects the UPF and triggers the PDU.
  • the SMF terminates the PDU session establishment procedure and notifies the UE of rejection.
  • the SMF may start establishing a PDU-CAN session toward the PCF to obtain a basic PCC rule for the PDU session. If the request type in step 3 indicates "existing PDU session", the PCF may start modifying the PDU-CAN session instead.
  • step 3 If the request type in step 3 indicates "initial request", the SMF selects the SSC mode for the PDU session. If step 5 is not performed, SMF can also select UPF. In case of the request type IPv4 or IPv6, the SMF may allocate an IP address/prefix for the PDU session.
  • the SMF may start the PDU-CAN session start.
  • the SMF may start the N4 session establishment procedure using the selected UPF, otherwise the N4 session modification procedure may start using the selected UPF.
  • the SMF transmits an N4 session establishment/modification request message to the UPF.
  • the SMF may provide packet detection, enforcement and reporting rules to be installed in the UPF for the PDU session.
  • the SMF is allocated CN tunnel information, the CN tunnel information may be provided to the UPF.
  • the UPF may respond by sending an N4 session establishment/modification response message.
  • the CN tunnel information may be provided to the SMF.
  • the SMF transmits an SM response message to the AMF.
  • the message may include a cause, N2 SM information, and N1 SM information.
  • the N2 SM information may include PDU session ID, QoS profile, and CN tunnel information.
  • the N1 SM information may include a PDU session establishment acceptance message.
  • the PDU session establishment accept message may include an allowed QoS rule, SSC mode, S-NSSAI, and an assigned IPv4 address.
  • the N1 SM information includes a PDU session acceptance message that the AMF should provide to the UE.
  • Multiple QoS rules may be included in N1 SM information and N2 SM information in the PDU session establishment accept message.
  • the SM response message also contains the PDU session ID and information allowing the AMF to determine which access should be used for the UE as well as which target UE.
  • the AMF transmits an N2 PDU session request message to the RAN.
  • the message may include N2 SM information and a NAS message.
  • the NAS message may include a PDU session ID and a PDU session establishment acceptance message.
  • the AMF may transmit a NAS message including a PDU session ID and a PDU session establishment accept message.
  • the AMF transmits the received N2 SM information from the SMF to the RAN by including it in the N2 PDU session request message.
  • the RAN may do a specific signaling exchange with the UE related to the information received from the SMF.
  • the RAN delivers the NAS message provided in step 10 to the UE.
  • the NAS message may include a PDU session ID and N1 SM information.
  • the N1 SM information may include a PDU session establishment acceptance message.
  • the RAN transmits an N2 PDU session response message to the AMF.
  • the message may include PDU session ID, cause, and N2 SM information.
  • the N2 SM information may include a PDU session ID, (AN) tunnel information, and a list of allowed/rejected QoS profiles.
  • the RAN tunnel information may correspond to the access network address of the N3 tunnel corresponding to the PDU session.
  • the AMF may transmit the SM request message to the SMF.
  • the SM request message may include N2 SM information.
  • the AMF may be to transfer the N2 SM information received from the RAN to the SMF.
  • the SMF may start the N4 session establishment procedure together with the UPF. Otherwise, the SMF may use the UPF to initiate the N4 session modification procedure.
  • the SMF may provide AN tunnel information and CN tunnel information.
  • the CN tunnel information may be provided only when the SMF selects the CN tunnel information in step 8.
  • the UPF may transmit an N4 session establishment/modification response message to the SMF.
  • the SMF may transmit the SM response message to the AMF. After this process, the AMF can deliver the related event to the SMF. Occurs during handover when RAN tunnel information is changed or AMF is relocated.
  • SMF transmits information to UE through UPF. Specifically, in the case of PDU Type IPv6, the SMF may generate an IPv6 Router Advertisement and transmit it to the UE through N4 and UPF.
  • the SMF may call "UDM_Register UE serving NF service" including the SMF address and DNN.
  • the UDM may store the ID, address and associated DNN of the SMF.
  • the SMF informs the AMF.
  • D2D device to device
  • UE#1 (100-1), UE#2 (100-2), UE#3 (100-3) or UE#4 (100-) 4), UE#5 (100-5), and UE#6 (100-6) a method for directly communicating without the intervention of the base station (gNB) 300 is being discussed.
  • UE#4 ( 100-4 ) may serve as a relay for UE#5 ( 100-5 ) and UE#6 ( 100-6 ).
  • UE#1100-1 may serve as a repeater for UE#2100-2 and UE#3100-3 that are far away from the cell center.
  • D2D communication is also called a proximity service (Proximity based Service: ProSe).
  • ProSe Proximity based Service
  • a UE performing a proximity service is also called a ProSe UE.
  • a link between UEs used for the D2D communication is also called a sidelink.
  • the physical channels used for the sidelink include the following.
  • DMRS Demodulation Reference signal
  • the SLSS includes a primary sidelink synchronization signal (PSLSS) and a secondary sidelink synchronization signal (Secondary SLSS: SSLSS).
  • PSLSS primary sidelink synchronization signal
  • SSLSS secondary sidelink synchronization signal
  • FIG. 8 shows an architecture for a ProSe service.
  • UE-1 and UE-2 are respectively connected to a base station (gNB) through a Uu link.
  • UE-1 and UE-2 can also communicate directly via the PC5 link.
  • the PC5 link may be an interface between the UE and the UE.
  • the Uu link may be an interface between the UE and the base station.
  • the UE may establish a PC5 link with another UE, and may perform a ProSe service with another UE through the established PC5 link.
  • PC5 will be mainly described with reference to NR PC5, but this is only an example, and the description related to PC5 described in this specification is PC5 related to another RAT (Radio Access Technology) (eg, LTE PC5, non -3GPP PC5, etc.) can also be applied.
  • RAT Radio Access Technology
  • the ProSe layer may mean a layer used by the UE for a ProSe service.
  • the ProSe layer may mean a V2X layer.
  • the ProSe layer may include a PC5 layer.
  • PC5 may mean NR PC5, LTE PC5, or both NR PC5 and LTE PC5.
  • NG-RAN may mean gNB or both gNB and ng-eNB.
  • a Uu link may mean a communication link through a Uu interface, and a Uu link may be used as the same meaning as a Uu path.
  • the PC5 link may mean a communication link through the PC5 interface, and the PC5 link may be used as the same meaning as the PC5 path.
  • IP Internet Protocol
  • FIG 9 shows an example of a structure for path switching according to the disclosure of the present specification.
  • 5GS_A indicates 5GS connected to UE A
  • 5GS_B indicates 5GS connected to UE B.
  • the UE may establish a PDU session.
  • the UE and/or an application eg, an application used by the UE may use the PC5 interface.
  • the PCF and/or the SMF may provide a switching rule to the UE.
  • the switching rule may provide information on how to steer traffic through the Uu interface and/or the PC5 interface and which traffic should be switched between the Uu interface and the PC5 interface.
  • an Active-Stanby mode may be used.
  • an Active-Stanby mode may be used.
  • the active-standby mode may be used to switch traffic to another available interface (ie, the Standby interface).
  • PCF and / or SMF is a switching indication (or information), capability (capability) information of the UE (eg, capability information of the UE related to PC5, MPTCP, etc.), subscriber information (subscription information) and / or local policy (local policy) and the like, may provide a switching rule to the UE.
  • the switching indication (or information) may be an indication (or information) indicating that the UE wants to use path switching between the Uu interface and the PC5 interface.
  • the PCF and/or SMF may provide a switching rule to the UE or update the switching rule while the PDU session modification procedure is performed.
  • ATSSS Access Traffic Steering, Switching, Splitting rules
  • the ATSSS rule may be used to configure the switching rule as it is, or an ATSS rule to which an appropriate change for path switching between the Uu interface and the PC5 interface is applied may be used to configure the switching rule.
  • Table 3 shows an example of a switching rule.
  • Optional Yes PDU context Non-IP descriptor (see NOTE 4) Represents one or more descriptors that identify the destination of non-IP traffic (eg, Ethernet traffic).
  • Optional Yes PDU context Access Selection Descriptor This part defines the Interface Selection Descriptor components for the switching rule.
  • the access selection descriptor indicates the Steering Mode.
  • Mandatory Steering Mode Identifies the steering mode applied for matching traffic.
  • NOTE 1 Each switching rule may have a different priority value than other switching rules.
  • NOTE 2 There may be at least one traffic descriptor component.
  • the application identifier may include an Operating System Identifier (OSId) and an OS specific Application Identifier (OSAppID).
  • OSId Operating System Identifier
  • OSAppID OS specific Application Identifier
  • a switching rule cannot contain both IP descriptors and non-IP descriptors.
  • Table 3 also shows an example of the structure of a switching rule.
  • the switching rule may include one or more pieces of information.
  • the switching rule may include information such as rule priority, traffic descriptor, application descriptor, IP descriptor, Non-IP descriptor, access selection descriptor, and Steering Mode.
  • Steering Mode may include an Active-Standby mode.
  • the following example of the switching rule may be used.
  • Traffic Descriptor Source IP address #C, Destination IP address #D
  • the terminal applies the rule according to the order of rule precedence.
  • load balancing mode is applied to transmit data to Uu interface and PC5 interface at a rate of 50%, respectively.
  • the Load Balancing mode is a mode in which data is divided and transmitted according to a predetermined ratio (eg 50:50).
  • Rule Precedence 2 check whether other traffic that is not applied to Rule Precedence 1 is applied to the next rule, Rule Precedence 2.
  • switching is performed by applying Active Standby mode to packets corresponding to Source IP address #C and Destination IP address #D. That is, if transmission through the Uu interface is not possible, transmission is performed through the PC5 interface.
  • the PCF and/or SMF may provide threshold information used to determine the availability and/or unavailability of a particular interface.
  • the PCF and/or SMF may provide threshold information to the UE.
  • the threshold information may include information on the threshold value of the signal strength of the interface.
  • the threshold information may also include information on a hysteresis value used to adjust an entry condition and a leave condition of the threshold value of the signal strength. If threshold information is included in the steering rule (eg, switching rule) for each interface, the UE may use the threshold information to determine the availability and/or unavailability of the interface. .
  • the UE receives this information from an AN (eg, NG-RAN or N3IWF, etc.) via broadcast (eg, System Information Block (SIB) or dedicated signaling) (eg, RRC signaling, Internet Key Exchange (IKE) signaling). Threshold information may be received. If the UE does not receive the threshold information, the UE determines the availability and/or unavailability of the interface based on pre-configured information or implementation (pre-configured information or implementation). unavailability) can be determined.
  • SIB System Information Block
  • dedicated signaling eg, RRC signaling, Internet Key Exchange (IKE) signaling
  • IKE Internet Key Exchange
  • the MPTCP layer In order to establish a new subflow over the PC5 link, the MPTCP layer needs to know which application is communicating through the PDU session of the Uu interface and the PC5 link associated with a specific UE. Based on the IP address information, the MPTCP layer may add a new subflow through the PC5 link.
  • FIG. 10 shows an example of a signal flow diagram of a procedure for path switching of the present specification.
  • both UE_A and UE_B use the same NG-RAN and core network.
  • UE_A and UE_B may use different NG-RANs and/or different core networks. That is, there is no restriction that the NG-RAN and/or the core network in which UE_A and UE_B communicate, respectively, must be identical to each other.
  • the NG-RAN and core network of UE_A selected during the PDU session establishment procedure may be different from the NG-RA and core network of UE_B selected during the PDU session establishment procedure.
  • UE_A may want to use both the Uu interface and the PC5 interface for a specific application (eg, application_X).
  • UE_A may transmit a PDU session establishment request message to the SMF and the PCF via the NG-RAN.
  • the PDU session establishment request message may include a switching indication (or information).
  • the switching indication (or information) may be an indication (or information) informing that the UE wants to use the path switching between the Uu interface and the PC5 interface, and the UE wants to use the path switching between the Uu interface and the PC5 interface.
  • SMF and/or PCF may accept UE_A's PDU session establishment request.
  • the SMF may transmit a PDU session establishment acceptance message to the UE.
  • the PDU session establishment acceptance message may include a switching rule.
  • the switching rule provided by the SMF to the UE may be a switching rule as in the example of Table 3 above.
  • UE_A may receive an IP address (eg, IP address #A_Uu) for a PDU session through NAS signaling or Dynamic Host Configuration Protocol (DHCP). The assigned IP address may be used by the application layer of UE_A.
  • IP address #A_Uu IP address #A_Uu
  • DHCP Dynamic Host Configuration Protocol
  • UE_B may want to use both the Uu interface and the PC5 interface for a specific application (eg, application_X).
  • UE_B may transmit a PDU session establishment request message to the SMF and the PCF via the NG-RAN.
  • the PDU session establishment request message may include a switching indication (or information).
  • the switching indication (or information) may be an indication (or information) informing that the UE wants to use the path switching between the Uu interface and the PC5 interface, and the UE wants to use the path switching between the Uu interface and the PC5 interface.
  • a PDU session of UE_B for switching (the IP address of the PDU session is IP address #B_Uu) may be established.
  • UE-A/application_X and UE-B/application_X may communicate with each other through a Uu interface. For example, when UE-A performs communication related to application_X with UE-B, it may perform communication through a Uu interface.
  • UE_A and UE_B may start a discovery procedure.
  • UE_A and UE_B may initiate a discovery procedure to perform direct communication via PC5.
  • a specific example of a discovery procedure performed by UE_A and UE_B will be described with reference to FIGS. 11 and 12 .
  • the operation performed in step 5) may include the operation illustrated in the example of FIG. 11 or 12 .
  • UE_A and/or UE_B may discover the other's Layer-2 ID.
  • UE_A may discover that UE_B is in proximity by using PC5 direct discovery.
  • UE_A may send a PC5 direct communication request message to UE_B using the Layer-2 ID found in step 5).
  • UE_B may assign a PC5 Link Identifier.
  • the PC5 direct communication request message transmitted by UE_A may include an indication (or information) for path switching to PC5.
  • the switching indication (or information) described in steps 1) and 2) transmits information that a UE (eg, UE_A or UE_B) can perform PC5 switching to a network node (eg, SMF, PCF). , can be used to obtain a switching rule from a network node (eg, SMF, PCF).
  • a network node eg, SMF, PCF
  • the indication (or information) for path switching to PC5 in step 6) is that the newly established (or created) PC5 link (PC5 link established (or created) according to the PC5 direct communication request message) uses the Uu interface. It can be used to inform that it is a PC5 link for switching the communication path performed through the PC5 interface.
  • the ProSe layer of each UE sends the MPTCP layer of application_X (eg, the MPTCP layer of each UE) to PC5 unicast link information (the IP address of the PC5 link ( Example: including the source IP address, optionally including the destination IP address)).
  • the MPTCP layer of application_X e.g, the MPTCP layer of each UE
  • PC5 unicast link information the IP address of the PC5 link ( Example: including the source IP address, optionally including the destination IP address)).
  • UE_B may send a PC5 direct communication accept message to UE_A.
  • UE_A may assign a PC5 link identifier.
  • the ProSe layer of each UE sends PC5 unicast link information (eg, the source IP address of the PC5 link to the MPTCP layer of application_X (eg, the MPTCP layer of each UE)). Included, optionally including the destination IP address) can be provided. Then, the MPTCP layer of each UE may add the MPTCP subflow over the PC5 unicast link to the MPTCP connection.
  • PC5 unicast link information eg, the source IP address of the PC5 link to the MPTCP layer of application_X (eg, the MPTCP layer of each UE)
  • the MPTCP layer of each UE may add the MPTCP subflow over the PC5 unicast link to the MPTCP connection.
  • one of the UEs may determine that the PC5 unicast link is unavailable.
  • One of the UEs may determine that the PC5 unicast link cannot be used based on a threshold value related to the PC5 link source strength (threshold value information included in the switching rule). For example, when the PC5 link signal strength of a peer UE (eg, UE_B) measured by UE_A is less than a threshold value, UE_A may determine that the PC5 unicast link is unavailable (unavailable).
  • UE_A or both UE_A and UE_B may periodically measure the PC5 link signal strength.
  • UE_A or UE_A and UE_B may compare the periodically measured PC5 link signal strength with a threshold to determine the availability/unavailability of the PC5 unicast link.
  • the ProSe layer of the UE (UE_A or UE_A and UE_B) may inform the MPTCP layer that the PC5 link is not available.
  • UE_A may trigger path switching from the PC5 interface to the Uu interface.
  • UE_A may transmit a PC5 path switching request message or a PC5 disconnect request message (including an indication (or information) informing of path switching to Uu) to UE_B.
  • UE_B may respond by sending a PC5 path switching response message to UE_A.
  • Both UE_A and UE_B may maintain the context for the PC5 unicast link without releasing/disconnecting the PC5 unicast link. In this case, the state of the PC5 unicast link may be marked as "unavailable” or "disabled”.
  • the PC5 unicast link can be re-used.
  • the status of the PC5 unicast link may be marked as “available” or “enabled”.
  • UE_A and UE_B may perform the PC5 unicast link establishment procedure according to the examples of steps 5) to 7). By performing steps 5) to 7), when a PC5 unicast link between UE_A and UE_B is established, the status of the PC5 unicast link may be marked as “available” or “enabled”.
  • UE_A When UE_A transmits a PC5 Disconnect request message (including an indication (or information) informing of path switching to Uu) to UE_B, UE_B may respond by sending a PC5 Disconnect response message to UE_A.
  • the PC5 disconnect request message may include an indication (or information) informing of path switching to Uu.
  • both UE_A and UE_B release the PC5 unicast link. Without /disconnect, you can keep the context for the PC5 unicast link.
  • the IP address used by the application (eg, the IP address of the Uu interface) is not changed when the MPTCP layer performs path switching. And, even if the MPTCP layer performs path switching, the application is not affected.
  • FIG. 11 shows a signal flow diagram according to a first example of a discovery procedure of the disclosure of the present specification.
  • UE_B may allocate a Layer-2 ID for a unicast PC5 link.
  • UE_B may periodically broadcast a Discovery Announce message through the PC5 interface.
  • the Discovery Announce message may include an IP address of a PDU session associated with an application, an IP address of a destination with which the application wishes to communicate, and an application identifier.
  • the Discovery Announce message may also include information on a Layer-2 ID allocated by UE_B (eg, a Layer-2 ID of UE_B).
  • a Discovery Announce message may be received by UE_A.
  • UE_B periodically broadcasts a Discovery Announce message, and when UE_A and UE_B are close to each other, UE_A may receive a Discovery Announce message. Based on the information included in the Discovery Announce message, UE_A may know the Layer-2 ID of UE_B.
  • UE_A may use the Layer-2 ID of UE_B as a destination Layer-2 ID for establishing a PC5 unicast link. Otherwise, UE_A may use the Layer-2 ID of the Discovery Announce message as the destination Layer-2 ID for establishing a PC5 unicast link.
  • FIG. 12 shows a signal flow diagram according to a second example of a discovery procedure of the disclosure of the present specification.
  • UE_A may broadcast a Discovery Request message through the PC5 interface.
  • the discovery request message may include an IP address of a PDU session associated with an application, an IP address of a destination with which the application intends to communicate, and an application identifier.
  • the discovery request message may be received by UE_B. For example, if UE_A broadcasts a discovery request message, and UE_A and UE_B are in proximity, UE_B may receive the discovery request message. Based on the information included in the discovery request message, UE_B may allocate a Layer-2 ID (eg, Layer-2 ID of UE_B) for the unicast PC5 link.
  • Layer-2 ID eg, Layer-2 ID of UE_B
  • UE_B may respond to UE_A by sending a Discovery Response message to UE_A.
  • UE_B may set the Layer-2 ID of UE_B allocated in step 1 as the source Layer-2 ID of the discovery response message.
  • UE_A may know the Layer-2 ID of UE_B. For example, when UE_A receives a discovery response message, UE_A may know the Layer-2 ID of UE_B.
  • UE_A may use the Layer-2 ID of UE_B as the destination Layer-2 ID for establishing a PC5 unicast link. Otherwise, UE_A may use the Layer-2 ID of the discovery response message as the destination Layer-2 ID for PC5 unicast link establishment.
  • the UE may have the following effects: For example, the UE may provide the switching indication (or information) to the SMF and/or the PCF by including the switching indication (or information) in the PDU session establishment request message.
  • the UE may receive the switching rule included in the PDU session establishment accept message, and the UE may apply the switching rule.
  • the UE may provide the IP address of the PDU session to the peer UE while performing the direct discovery procedure.
  • the UE may support MPTCP functionality.
  • the SMF and/or PCF may have the following effects:
  • the SMF and/or PCF may provide the UE with switching rules.
  • the SMF and/or the PCF may transmit a PDU session establishment acceptance message including a switching rule to the UE.
  • the UE transmits an indication (or information) indicating that path switching (eg, PC5 switching) is required while establishing (or generating) a PDU session to the network (eg, SMF and/or PCF).
  • the network eg, SMF and/or PCF
  • the ProSe layer of the terminal may determine access availability/unavailability. For example, the UE may determine the availability/unavailability of the PC5 unicast link based on the switching rule. The ProSe layer of the UE may inform the MPTCP layer of access availability/unavailability. In addition, the MPTCP layer of the terminal may perform traffic steering between the Uu link and the PC5 link according to the PC5 switching rule provided by the SMF and/or the PCF.
  • the terminal Before the PC5 link of the terminal is disconnected, the terminal may transmit a PC5 switching request message to the peer UE.
  • the UE transmits a PC5 switching request message to the peer UE, even if the PC5 link is disconnected, the context related to the PC5 link may be maintained. Thereafter, when the PC5 link becomes available, the UE can use the previously set up PC5 link as it is.
  • the terminal switches (switches) a path between the PC5 link and the Uu link according to the link situation of the terminal (eg, the PC5 link situation and/or the Uu link situation) , so that the link can be switched before the PC5 link or the Uu link is broken.
  • the UE eg, UE
  • the service can be performed seamlessly. That is, service continuity may be improved.
  • One or more processors 1020a or 1020b control one or more memories 1010a or 1010b and one or more transceivers 1031a or 1031b, and execute instructions/programs stored in one or more memories 1010a or 1010b as disclosed herein. It is possible to perform the operation of the UE (eg, UE_A or UE_B) described in .
  • instructions for performing an operation of a terminal may be stored in a non-volatile computer-readable storage medium in which it is recorded.
  • the storage medium may be included in one or more memories 1010a or 1010b.
  • the instructions recorded in the storage medium may be executed by one or more processors 1020a or 1020b to perform the operation of the terminal (eg, UE_A or UE_B) described in the disclosure of the present specification.
  • a network node eg, SMF, PCF, etc.
  • a base station eg, NG-RAN, gNB, eNB, etc.
  • the network node may be the first device 100a or the second device 100b of FIG. 14 .
  • the operation of the network node described herein may be processed by one or more processors 1020a or 1020b.
  • the operations of the network node or base station described herein may be stored in one or more memories 1010a or 1010b in the form of instructions/programs (e.g.
  • processors 1020a or 1020b control one or more memories 1010a or 1010b and one or more transceivers 1031a or 1031b, and execute instructions/programs stored in one or more memories 1010a or 1010b as disclosed herein. It is possible to perform the operation of the network node or the base station described in .
  • FIG 13 is one in the example A wireless communication system according to the present invention is shown.
  • a wireless communication system may include a first device 100a and a second device 100b.
  • the first device 100a and the second device 100b may be wireless communication devices capable of performing wireless communication.
  • the first device 100a may be UE_A or UE_B described in the disclosure of this specification.
  • the first device 100a is a base station, a network node (eg, SMF, PCF, or AMF, etc.), a transmitting UE, a receiving UE, a wireless device, a wireless communication device, a vehicle, a vehicle equipped with an autonomous driving function, a connected Car (Connected Car), Drone (Unmanned Aerial Vehicle, UAV), AI (Artificial Intelligence) Module, Robot, AR (Augmented Reality) Device, VR (Virtual Reality) Device, MR (Mixed Reality) Device, Hologram Device, Public Safety It may be a device, an MTC device, an IoT device, a medical device, a fintech device (or a financial device), a security device, a climate/environmental device, a device related to 5G services, or other devices related to the 4th industrial revolution field.
  • a network node eg, SMF, PCF
  • the second device 100b may be a network node (eg, SMF, PCF, or AMF) described in the disclosure of the present specification.
  • the second device 100b may be a base station, a network node, a transmitting UE, a receiving UE, a wireless device, a wireless communication device, a vehicle, a vehicle equipped with an autonomous driving function, a connected car, or a drone (Unmanned Aerial).
  • Vehicle UAV
  • AI Artificial Intelligence
  • Robot Robot
  • AR Augmented Reality
  • VR Virtual Reality
  • MR Magnetic Reality
  • Hologram Device Hologram Device
  • Public Safety Device MTC Device
  • IoT Device Medical Device
  • fintech devices or financial devices
  • security devices climate/environment devices, devices related to 5G services, or other devices related to the field of the fourth industrial revolution.
  • the UE 100 includes a mobile phone, a smart phone, a laptop computer, a UE device for digital broadcasting, personal digital assistants (PDA), a portable multimedia player (PMP), a navigation system, and a slate PC (slate).
  • PDA personal digital assistants
  • PMP portable multimedia player
  • PC tablet PC
  • ultrabook wearable device
  • wearable device e.g., watch-type UE device (smartwatch), glass-type UE device (smart glass), HMD (head mounted display)
  • the HMD may be a display device worn on the head.
  • an HMD may be used to implement VR, AR or MR.
  • the drone may be a flying vehicle that does not ride by a person and flies by a wireless control signal.
  • the VR device may include a device that implements an object or a background of a virtual world.
  • the AR device may include a device that implements by connecting an object or background in the virtual world to an object or background in the real world.
  • the MR device may include a device that implements a virtual world object or background by fusion with a real world object or background.
  • the hologram device may include a device for realizing a 360-degree stereoscopic image by recording and reproducing stereoscopic information by utilizing an interference phenomenon of light generated by the meeting of two laser beams called holography.
  • the public safety device may include an image relay device or an image device that can be worn on a user's body.
  • the MTC device and the IoT device may be devices that do not require direct human intervention or manipulation.
  • the MTC device and the IoT device may include a smart meter, a bending machine, a thermometer, a smart light bulb, a door lock, or various sensors.
  • a medical device may be a device used for the purpose of diagnosing, treating, alleviating, treating, or preventing a disease.
  • a medical device may be a device used for the purpose of diagnosing, treating, alleviating or correcting an injury or disorder.
  • a medical device may be a device used for the purpose of examining, replacing, or modifying structure or function.
  • the medical device may be a device used for the purpose of controlling pregnancy.
  • the medical device may include a medical device, a surgical device, an (ex vivo) diagnostic device, a hearing aid, or a device for a procedure.
  • the security device may be a device installed to prevent a risk that may occur and maintain safety.
  • the security device may be a camera, CCTV, recorder or black box.
  • the fintech device may be a device capable of providing financial services such as mobile payment.
  • the fintech device may include a payment device or a Point of Sales (POS).
  • the climate/environment device may include a device for monitoring or predicting the climate/environment.
  • the first device 100a may include at least one processor such as a processor 1020a, at least one memory such as a memory 1010a, and at least one transceiver such as a transceiver 1031a.
  • the processor 1020a may perform the functions, procedures, and/or methods described above.
  • the processor 1020a may perform one or more protocols.
  • the processor 1020a may perform one or more layers of an air interface protocol.
  • the memory 1010a is connected to the processor 1020a and may store various types of information and/or commands.
  • the transceiver 1031a may be connected to the processor 1020a and may be controlled to transmit/receive a wireless signal.
  • the second device 100b may include at least one processor such as a processor 1020b, at least one memory device such as a memory 1010b, and at least one transceiver such as a transceiver 1031b.
  • the processor 1020b may perform the functions, procedures, and/or methods described above.
  • the processor 1020b may implement one or more protocols.
  • the processor 1020b may implement one or more layers of an air interface protocol.
  • the memory 1010b is connected to the processor 1020b and may store various types of information and/or commands.
  • the transceiver 1031b may be connected to the processor 1020b and may be controlled to transmit/receive a wireless signal.
  • the memory 1010a and/or the memory 1010b may be respectively connected inside or outside the processor 1020a and/or the processor 1020b, and may be connected to other processors through various technologies such as wired or wireless connection. may be connected to
  • FIG. 14 is a work in the example A block diagram of a network node according to the following is illustrated.
  • FIG. 14 is a diagram illustrating in detail a case in which a base station is divided into a central unit (CU) and a distributed unit (DU).
  • CU central unit
  • DU distributed unit
  • base stations W20 and W30 may be connected to the core network W10 , and the base station W30 may be connected to a neighboring base station W20 .
  • the interface between the base stations W20 and W30 and the core network W10 may be referred to as NG, and the interface between the base station W30 and the neighboring base station W20 may be referred to as Xn.
  • the base station W30 may be divided into CUs W32 and DUs W34 and W36. That is, the base station W30 may be hierarchically separated and operated.
  • the CU W32 may be connected to one or more DUs W34 and W36, for example, an interface between the CU W32 and the DUs W34 and W36 may be referred to as F1.
  • the CU (W32) may perform functions of upper layers of the base station, and the DUs (W34, W36) may perform functions of lower layers of the base station.
  • One DU (W34, W36) may support one or more cells. One cell can be supported by only one DU (W34, W36).
  • One DU (W34, W36) may be connected to one CU (W32), and one DU (W34, W36) may be connected to a plurality of CUs by appropriate implementation.
  • 15 is a block diagram illustrating the configuration of the UE 100 according to an embodiment.
  • the UE 100 illustrated in FIG. 15 is a diagram illustrating the first apparatus of FIG. 13 in more detail.
  • the UE 100 includes a memory 1010, a processor 1020, a transceiver 1031, a power management module 1091, a battery 1092, a display 1041, an input unit 1053, a speaker 1042, and a microphone ( 1052), a subscriber identification module (SIM) card, and one or more antennas.
  • a memory 1010 a processor 1020, a transceiver 1031, a power management module 1091, a battery 1092, a display 1041, an input unit 1053, a speaker 1042, and a microphone ( 1052), a subscriber identification module (SIM) card, and one or more antennas.
  • SIM subscriber identification module
  • the processor 1020 may be configured to implement the proposed functions, procedures, and/or methods described herein.
  • the layers of the air interface protocol may be implemented in the processor 1020 .
  • the processor 1020 may include an application-specific integrated circuit (ASIC), other chipsets, logic circuits, and/or data processing devices.
  • the processor 1020 may be an application processor (AP).
  • the processor 1020 may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modem (modulator and demodulator).
  • DSP digital signal processor
  • CPU central processing unit
  • GPU graphics processing unit
  • modem modulator and demodulator
  • processor 1020 examples include SNAPDRAGONTM series processors manufactured by Qualcomm®, EXYNOSTM series processors manufactured by Samsung®, A series processors manufactured by Apple®, HELIOTM series processors manufactured by MediaTek®, INTEL® It may be an ATOMTM series processor manufactured by the company or a corresponding next-generation processor.
  • the power management module 1091 manages power for the processor 1020 and/or the transceiver 1031 .
  • the battery 1092 supplies power to the power management module 1091 .
  • the display 1041 outputs the result processed by the processor 1020 .
  • Input 1053 receives input to be used by processor 1020 .
  • the input unit 1053 may be displayed on the display 1041 .
  • a SIM card is an integrated circuit used to securely store an international mobile subscriber identity (IMSI) and its associated keys used to identify and authenticate subscribers in mobile phone devices such as mobile phones and computers. Many SIM cards can also store contact information.
  • IMSI international mobile subscriber identity
  • the memory 1010 is operatively coupled to the processor 1020 , and stores various information for operating the processor 610 .
  • Memory 1010 may include read-only memory (ROM), random access memory (RAM), flash memory, memory cards, storage media, and/or other storage devices.
  • ROM read-only memory
  • RAM random access memory
  • flash memory memory cards
  • storage media storage media
  • other storage devices such as hard disk drives, floppy disk drives, and the like.
  • modules may be stored in memory 1010 and executed by processor 1020 .
  • the memory 1010 may be implemented inside the processor 1020 . Alternatively, the memory 1010 may be implemented outside the processor 1020 , and may be communicatively connected to the processor 1020 through various means known in the art.
  • the transceiver 1031 is operatively coupled to the processor 1020 and transmits and/or receives a radio signal.
  • the transceiver 1031 includes a transmitter and a receiver.
  • the transceiver 1031 may include a baseband circuit for processing a radio frequency signal.
  • the transceiver controls one or more antennas to transmit and/or receive radio signals.
  • the processor 1020 transmits command information to the transceiver 1031 to transmit, for example, a wireless signal constituting voice communication data to initiate communication.
  • the antenna functions to transmit and receive radio signals.
  • the transceiver 1031 may transmit the signal for processing by the processor 1020 and convert the signal to a baseband.
  • the processed signal may be converted into audible or readable information output through the speaker 1042 .
  • the speaker 1042 outputs sound related results processed by the processor 1020 .
  • Microphone 1052 receives sound related input to be used by processor 1020 .
  • the user inputs command information, such as a phone number, by, for example, pressing (or touching) a button of the input unit 1053 or voice activation using the microphone 1052 .
  • the processor 1020 receives such command information and processes it to perform an appropriate function, such as making a call to a phone number. Operational data may be extracted from the SIM card or the memory 1010 .
  • the processor 1020 may display command information or driving information on the display 1041 for the user to recognize and for convenience.
  • FIG. 16 is a detailed block diagram illustrating the transceiver of the first device shown in FIG. 13 or the transceiver of the device shown in FIG. 15 .
  • the transceiver 1031 includes a transmitter 1031-1 and a receiver 1031-2.
  • the transmitter 1031-1 includes a Discrete Fourier Transform (DFT) unit 1031-11, a subcarrier mapper 1031-12, an IFFT unit 1031-13 and a CP insertion unit 1031-14, and a wireless transmitter 1031. -15).
  • the transmitter 1031-1 may further include a modulator.
  • it may further include, for example, a scramble unit (not shown; scramble unit), a modulation mapper (not shown; modulation mapper), a layer mapper (not shown; layer mapper), and a layer permutator (not shown; layer permutator),
  • a scramble unit not shown; scramble unit
  • a modulation mapper not shown; modulation mapper
  • a layer mapper not shown; layer mapper
  • a layer permutator not shown; layer permutator
  • the IFFT Inverse Fast Fourier Transform
  • the DFT unit 1031-11 outputs complex-valued symbols by performing DFT on input symbols. For example, when Ntx symbols are input (however, Ntx is a natural number), the DFT size is Ntx.
  • the DFT unit 1031-11 may be referred to as a transform precoder.
  • the subcarrier mapper 1031-12 maps the complex symbols to each subcarrier in the frequency domain. The complex symbols may be mapped to resource elements corresponding to resource blocks allocated for data transmission.
  • the subcarrier mapper 1031 - 12 may be referred to as a resource element mapper.
  • the IFFT unit 1031-13 outputs a baseband signal for data that is a time domain signal by performing IFFT on an input symbol.
  • the CP insertion unit 1031-14 copies a part of the rear part of the base band signal for data and inserts it into the front part of the base band signal for data.
  • ISI Inter-symbol interference
  • ICI inter-carrier interference
  • the receiver 1031-2 includes a radio receiver 1031-21, a CP remover 1031-22, an FFT unit 1031-23, and an equalizer 1031-24.
  • the radio receiving unit 1031-21, the CP removing unit 1031-22, and the FFT unit 1031-23 of the receiver 1031-2 include the radio transmitting unit 1031-15 in the transmitting end 1031-1, It performs the reverse function of the CP insertion unit 1031-14 and the IFF unit 1031-13.
  • the receiver 1031 - 2 may further include a demodulator.
  • the communication system 1 applied to the disclosure of the present specification includes a wireless device, a base station, and a network.
  • the wireless device refers to a device that performs communication using a radio access technology (eg, 5G NR (New RAT), LTE (Long Term Evolution)), and may be referred to as a communication/wireless/5G device.
  • a radio access technology eg, 5G NR (New RAT), LTE (Long Term Evolution)
  • the wireless device includes a robot 100a, a vehicle 100b-1, 100b-2, an eXtended Reality (XR) device 100c, a hand-held device 100d, and a home appliance 100e. ), an Internet of Things (IoT) device 100f, and an AI device/server 400 .
  • the vehicle may include a vehicle equipped with a wireless communication function, an autonomous driving vehicle, a vehicle capable of performing inter-vehicle communication, and the like.
  • the vehicle may include an Unmanned Aerial Vehicle (UAV) (eg, a drone).
  • UAV Unmanned Aerial Vehicle
  • XR devices include AR (Augmented Reality)/VR (Virtual Reality)/MR (Mixed Reality) devices, and include a Head-Mounted Device (HMD), a Head-Up Display (HUD) provided in a vehicle, a television, a smartphone, It may be implemented in the form of a computer, a wearable device, a home appliance, a digital signage, a vehicle, a robot, and the like.
  • the portable device may include a smart phone, a smart pad, a wearable device (eg, a smart watch, smart glasses), a computer (eg, a laptop computer), and the like.
  • Home appliances may include a TV, a refrigerator, a washing machine, and the like.
  • the IoT device may include a sensor, a smart meter, and the like.
  • the base station and the network may be implemented as a wireless device, and a specific wireless device 200a may operate as a base station/network node to other wireless devices.
  • the wireless communication technology implemented in the wireless devices 100a to 100f, 400, and 100 and 200 of FIG. 14 of the present specification may include a narrowband Internet of Things for low-power communication as well as LTE, NR, and 6G.
  • the NB-IoT technology may be an example of a LPWAN (Low Power Wide Area Network) technology, and may be implemented in standards such as LTE Cat NB1 and/or LTE Cat NB2, and is limited to the above-mentioned names. no.
  • the wireless communication technology implemented in the wireless devices 100a to 100f and 400 of the present specification and 100 and 200 in FIG. 14 may perform communication based on the LTE-M technology.
  • the LTE-M technology may be an example of an LPWAN technology, and may be called by various names such as enhanced machine type communication (eMTC).
  • eMTC enhanced machine type communication
  • LTE-M technology is 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine It may be implemented in at least one of various standards such as Type Communication, and/or 7) LTE M, and is not limited to the above-described name.
  • Power Wide Area Network may include at least any one of, but is not limited to the above-described name.
  • the ZigBee technology can create PAN (personal area networks) related to small/low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.
  • Wireless communication/connection 150a, 150b, and 150c may be performed between the wireless devices 100a to 100f/base station 200 and the base station 200/base station 200 .
  • the wireless communication/connection includes uplink/downlink communication 150a and sidelink communication 150b (or D2D communication), and communication between base stations 150c (eg relay, IAB (Integrated Access Backhaul)).
  • This can be done through technology (eg 5G NR)
  • Wireless communication/connection 150a, 150b, 150c allows the wireless device and the base station/radio device, and the base station and the base station to transmit/receive wireless signals to each other.

Landscapes

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

Abstract

Selon un mode de réalisation, l'invention concerne un procédé permettant d'exécuter une communication associée à une commutation de trajet au moyen d'un premier UE. Le procédé peut comprendre les étapes consistant à : transmettre un message de demande d'établissement de session PDU qui demande l'établissement d'une session PDU; recevoir un message d'acceptation d'établissement de session PDU comprenant des informations de règle de commutation; effectuer une communication avec un second UE par le biais d'une interface Uu; effectuer une communication directe avec le second UE par le biais d'une interface PC5; et commuter, de l'interface Uu à l'interface PC5, un trajet pour une communication avec le second UE.
PCT/KR2020/018001 2019-12-20 2020-12-10 Commutation de trajet de communication WO2021125691A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR20190172379 2019-12-20
KR10-2019-0172379 2019-12-20

Publications (1)

Publication Number Publication Date
WO2021125691A1 true WO2021125691A1 (fr) 2021-06-24

Family

ID=76477803

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2020/018001 WO2021125691A1 (fr) 2019-12-20 2020-12-10 Commutation de trajet de communication

Country Status (1)

Country Link
WO (1) WO2021125691A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114189912A (zh) * 2021-12-21 2022-03-15 中国联合网络通信集团有限公司 会话方法、控制面功能实体及代理、会话系统
WO2023207687A1 (fr) * 2022-04-24 2023-11-02 索尼集团公司 Dispositif et procédé de commutation rapide de mode de communication et support
WO2024027491A1 (fr) * 2022-08-02 2024-02-08 中国电信股份有限公司 Procédé, appareil et système de commutation de trajet
WO2024065844A1 (fr) * 2022-09-30 2024-04-04 北京小米移动软件有限公司 Procédé d'interaction pour capacités de commutation de trajet et appareil associé

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
CATT, HUAWEI, HISILICON: "Solution for path switch between PC5 and Uu", 3GPP DRAFT; S2-1912400, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Reno, USA; 20191118 - 20191122, 20 November 2019 (2019-11-20), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051827103 *
ERICSSON: "On the sidelink session and connection", 3GPP DRAFT; R2-1817928 - ON THE SIDELINK SESSION AND CONNECTION, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Spokane, WA, USA; 20181112 - 20181116, 1 November 2018 (2018-11-01), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051481813 *
KANG YUHWA, CHOI YOUNG-IL: "3GPP 5G System Access Traffic Steering Standard Technology Trend", NATIONAL IT INDUSTRY PROMOTION AGENCY, 17 June 2019 (2019-06-17), XP055821335, Retrieved from the Internet <URL:https://signalm.sedaily.com/ReportView/2293> [retrieved on 20210706] *
VIVO MOBILE COMMUNICATION CO. LTD: "PC5: IP or Unstructured data", 3GPP DRAFT; S2-1910921, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Reno, Nevada, United States; 20191118 - 20191122, 8 November 2019 (2019-11-08), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051821048 *
VIVO: "Clarification on the path selection", 3GPP DRAFT; S2-1912706, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Reno, USA; 20191118 - 20191122, 22 November 2019 (2019-11-22), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051828565 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114189912A (zh) * 2021-12-21 2022-03-15 中国联合网络通信集团有限公司 会话方法、控制面功能实体及代理、会话系统
CN114189912B (zh) * 2021-12-21 2024-01-09 中国联合网络通信集团有限公司 会话方法、控制面功能实体及代理、会话系统
WO2023207687A1 (fr) * 2022-04-24 2023-11-02 索尼集团公司 Dispositif et procédé de commutation rapide de mode de communication et support
WO2024027491A1 (fr) * 2022-08-02 2024-02-08 中国电信股份有限公司 Procédé, appareil et système de commutation de trajet
WO2024065844A1 (fr) * 2022-09-30 2024-04-04 北京小米移动软件有限公司 Procédé d'interaction pour capacités de commutation de trajet et appareil associé

Similar Documents

Publication Publication Date Title
WO2021034073A1 (fr) Procédé de relais de trafic non structuré, et ue de relais
WO2021034093A1 (fr) Authentification pour relais
WO2021029512A1 (fr) Communication liée à une modification de serveur d&#39;application
WO2021091115A1 (fr) Commutation de trajet entre liaison pc5 et liaison uu
WO2021125691A1 (fr) Commutation de trajet de communication
WO2021049841A1 (fr) Procédé permettant de déplacer une session vocale ims sur un accès non 3gpp vers un accès 3gpp
WO2021034142A1 (fr) Procédé de fonctionnement d&#39;un équipement utilisateur relais pour équipement utilisateur à distance
WO2021040423A1 (fr) Communication liée à une mise à jour de configuration
WO2017138757A1 (fr) Procédé de transmission et de réception de données utilisant de multiples dispositifs de communication dans un système de communication sans fil, et dispositif prenant en charge celui-ci
WO2021034126A1 (fr) Communication associée à un relais de couche 2
WO2021040463A1 (fr) Communication relative à un état de désactivation du service de données ps 3gpp
WO2020218807A1 (fr) Schéma de prise en charge de pmf pour session pdu ma
WO2021157974A1 (fr) Communication associée à une session pdu multi-accès
WO2021025308A1 (fr) Procédé de traitement d&#39;amf pour prendre en charge de multiples usim
WO2017138768A1 (fr) Procédé d&#39;émission/réception de données dans un système de communication sans fil et dispositif de prise en charge de ce dernier
WO2021096193A1 (fr) Communication à relais
WO2021066346A1 (fr) Procédé permettant de déplacer une session de pdu sur un accès non 3gpp vers un accès 3gpp
WO2021091186A1 (fr) Procédé de commande de réseau pour transmission de politique d&#39;ue
WO2021167200A1 (fr) Procédé de fonctionnement pour ausf et udm pour authentification et autorisation pour chaque tranche de réseau
WO2020251226A1 (fr) Procédé d&#39;accès à un npn dans un système de communication mobile 5g et équipement utilisateur
WO2021167233A1 (fr) Communication relative à une tranche de réseau
WO2021162275A1 (fr) Communication relative à une tranche de réseau
WO2022225262A1 (fr) Procédé de gestion de session pdu redondante pour transmission redondante
WO2021133047A1 (fr) Procédé par lequel un ue de communication de relais prend en charge efficacement un ue à distance lors d&#39;une mise à jour de configuration
WO2021020913A1 (fr) Procédé de fonctionnement pour équipement utilisateur prenant en charge un usim multiple

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

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

Country of ref document: EP

Kind code of ref document: A1