WO2021025432A1 - Signalisation ims - Google Patents

Signalisation ims Download PDF

Info

Publication number
WO2021025432A1
WO2021025432A1 PCT/KR2020/010269 KR2020010269W WO2021025432A1 WO 2021025432 A1 WO2021025432 A1 WO 2021025432A1 KR 2020010269 W KR2020010269 W KR 2020010269W WO 2021025432 A1 WO2021025432 A1 WO 2021025432A1
Authority
WO
WIPO (PCT)
Prior art keywords
ims
layer
service
signaling
terminal
Prior art date
Application number
PCT/KR2020/010269
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 WO2021025432A1 publication Critical patent/WO2021025432A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]

Definitions

  • the present specification relates to mobile communication.
  • LTE long term evolution
  • LTE-A LTE-Advanced
  • New RAT new radio access technology
  • 5th generation mobile communication defined by the International Telecommunication Union (ITU) refers to providing a maximum 20Gbps data transmission speed and a sensible transmission speed of at least 100Mbps or more anywhere. Its official name is'IMT-2020' and it aims to be commercialized globally in 2020.
  • ITU International Telecommunication Union
  • a terminal using a 3rd Generation Partnership Project (3GPP) system including LTE and 5G provides IP Multimedia Subsystem (IMS) services such as voice call, video call, and SMS (Short Messge Service) (e.g. SMS over IP (Internet Protocol)). Can be provided.
  • IMS IP Multimedia Subsystem
  • the IMS layer of such a terminal needs to deliver IMS signaling for non-service attempts (e.g., IMS signaling for the purpose of initial registration, re-registration, and subscription refresh) to the IMS network rather than the actual attempt related to the IMS service.
  • IMS layer of the terminal transmits the IMS signaling for non-service attempts to the RRC layer of the terminal through the NAS layer of the terminal, and the RRC layer of the terminal can transmit it to the network.
  • the RRC layer of the terminal performs an access control check on IMS signaling for non-service attempts based on the access category.
  • IMS signaling for non-service attempts does not define a separate access category for this and uses an access category for general transmission data (e.g., access category 7 for Mobile Originating (MO) data), which is applicable to other access categories. Compared to this, the priority is low, so it is highly likely to be blocked by the RRC layer.
  • MO Mobile Originating
  • one disclosure of the present specification aims to provide a solution to the above-described problem.
  • one disclosure of the present specification provides a method for a terminal to perform communication related to IMS.
  • the method includes: transmitting, by the IMS layer, a first request message including information related to IMS signaling for non-service attempts to the NAS layer of the terminal; Receiving, by the IMS layer of the terminal, a response message indicating that the first request message has been blocked from the NAS layer of the terminal; And storing information that transmission of information related to IMS signaling for the non-service attempt has failed.
  • a wireless communication device includes at least one processor; And at least one memory that stores an instruction and is operably electrically connected to the at least one processor.
  • the operation performed based on the execution of the command by the at least one processor is:
  • the IMS layer transmits a first request message including information related to IMS signaling for non-service attempts to the NAS layer of the terminal. The step of doing; Receiving, by the IMS layer of the terminal, a response message indicating that the first request message has been blocked from the NAS layer of the terminal; And storing information that transmission of information related to IMS signaling for the non-service attempt has failed.
  • the apparatus includes at least one processor; And at least one memory that stores an instruction and is operably electrically connected to the at least one processor.
  • the operation performed based on the execution of the command by the at least one processor is: a first including information related to Internet protocol Multimedia Subsystem (IMS) signaling for a non-service attempt Generating a request message; Identifying a response message indicating that the first request message has been blocked; And storing information that transmission of information related to IMS signaling for the non-service attempt has failed.
  • IMS Internet protocol Multimedia Subsystem
  • one disclosure of the present specification provides a non-volatile computer-readable storage medium for recording instructions.
  • the instructions when executed by one or more processors, cause the one or more processors to: a first including information related to Internet protocol Multimedia Subsystem (IMS) signaling for a non-service attempt. 1 generating a request message; Identifying a response message indicating that the first request message has been blocked; And storing information that transmission of information related to IMS signaling for the non-service attempt has failed.
  • IMS Internet protocol Multimedia Subsystem
  • FIG. 1 is an example of a structural diagram of a next-generation mobile communication network.
  • FIG. 2 is an exemplary diagram showing an expected structure of next-generation mobile communication from a node perspective.
  • FIG. 3 is an exemplary diagram showing an architecture for supporting simultaneous access to two data networks.
  • FIG. 4 is another exemplary diagram showing the structure of a radio interface protocol between a UE and a gNB.
  • 5A and 5B are signal flow diagrams illustrating an exemplary registration procedure.
  • 6A and 6B are signal flow diagrams illustrating an exemplary PDU session establishment procedure.
  • FIG. 8 is an exemplary signal flow diagram illustrating the disclosure of the present specification.
  • FIG. 9 is an exemplary signal flow diagram illustrating operations according to case 1 of FIG. 8.
  • FIG. 10 is an exemplary signal flow diagram illustrating operations according to a first example of the disclosure of the present specification.
  • 11 is an exemplary signal flow diagram illustrating a second example of the disclosure of the present specification.
  • FIG. 13 illustrates a wireless device applicable to the disclosure of the present specification.
  • FIG. 14 illustrates a signal processing circuit for a transmission signal.
  • 15 shows another example of a wireless device applied to the disclosure of the present specification.
  • 16 shows an example of a vehicle or an autonomous vehicle that is applied to the disclosure of the present specification.
  • FIG 17 illustrates an AI device applied to the disclosure of the present specification.
  • first and second used in the present specification may be used to describe various elements, but the elements should not be limited by the terms. These terms are only used for the purpose of distinguishing one component from another component. For example, without departing from the scope of the rights, a first component may be referred to as a second component, and similarly, a second component may be referred to as a first component.
  • a component When a component is connected to or is said to be connected to another component, it may be directly connected or connected to the other component, but other components may exist in the middle. On the other hand, when a component is directly connected to or directly connected to another component, it should be understood that there is no other component in the middle.
  • 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) refers to “only A”, “only B”, “only C”, or “A, B, and any combination of C ( It can mean any combination of A, B and C)”.
  • a forward slash (/) or comma used in the present specification may mean “and/or”.
  • A/B may mean “A and/or B”. Accordingly, “A/B” may mean “only A”, “only B”, or “both A and B”.
  • A, B, C may mean “A, B or 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”.
  • At least one of A, B and C means “only A”, “only B”, “only C”, or “A, B and C Can mean any combination of A, B and C”.
  • at least one of A, B or C or “at least one of A, B and/or C” means It can mean “at least one of A, B and C”.
  • parentheses used in the present specification 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 suggested as an example of “control information”. In addition, even when indicated as “control information (ie, PDCCH)”, “PDCCH” may be proposed as an example of “control information”.
  • a user equipment is illustrated by way of example, but the illustrated UE may be referred to in terms of 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, or a multimedia device, or may be a non-portable device such as a PC or a vehicle-mounted device.
  • the UE is used as an example of a wireless communication device (or a wireless device, or a wireless device) capable of wireless communication.
  • the operation performed by the UE may be performed by a wireless communication device.
  • the wireless communication device may also be referred to as a wireless device, a wireless device, or the like.
  • AMF may refer to an AMF node
  • SMF may refer to an SMF node
  • UPF may refer to a UPF node.
  • a base station which is a term used below, generally refers to a fixed station that communicates with a wireless device, eNodeB (evolved-NodeB), eNB (evolved-NodeB), BTS (Base Transceiver System), access point ( Access Point), gNB (Next generation NodeB), and other terms.
  • eNodeB evolved-NodeB
  • eNB evolved-NodeB
  • BTS Base Transceiver System
  • Access Point Access Point
  • gNB Next generation NodeB
  • FIG. 1 is a diagram of a next-generation mobile communication network Structural Yes.
  • 5GC 5G Core
  • AMF Access and Mobility Management Function
  • SMF session management function: Session Management
  • Policy Control Function Policy Control Function
  • UPF User Plane Function
  • AF Application Function
  • UDM Integrated Data Management: Includes Unified Data Management (46) and Non-3GPP InterWorking Function (N3IWF) (49).
  • the UE 100 is connected to a data network through the UPF 44 through a Next Generation Radio Access Network (NG-RAN) including the gNB 200.
  • NG-RAN Next Generation Radio Access Network
  • the UE 100 may receive a data service even through untrusted non-3GPP access, for example, a wireless local area network (WLAN).
  • a wireless local area network for example, a wireless local area network (WLAN).
  • WLAN wireless local area network
  • an N3IWF 49 may be deployed.
  • the illustrated N3IWF 49 performs a function of managing non-3GPP access and interworking between 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 49.
  • the N3IWF 49 performs control signaling with the AMF 41 and is connected to the UPF 44 through an N3 interface for data transmission.
  • the illustrated AMF 41 can manage access and mobility in a 5G system.
  • the AMF 41 may perform a function of managing NAS (Non-Access Stratum) security.
  • the AMF 41 may perform a function of handling mobility in an idle state.
  • the illustrated UPF 44 is a type of gateway through which user data is transmitted and received.
  • the UPF node 44 may perform all or part of a user plane function 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 44 operates as a boundary point between a next generation RAN (NG-RAN) and a core network, and is an element that maintains a data path between the gNB 200 and the SMF 42. In addition, when the UE 100 moves over an area served by the gNB 200, the UPF 44 serves as a mobility anchor point. The UPF 44 may perform a function of handling a PDU. Packets may be routed in the UPF for mobility within the NG-RAN (Next Generation-Radio Access Network defined after 3GPP Release-15).
  • NG-RAN Next Generation-Radio Access Network defined after 3GPP Release-15.
  • the UPF 44 is another 3GPP network (RAN defined before 3GPP Release-15, for example, UTRAN, E-UTRAN (Evolved-UMTS (Universal Mobile Telecommunications System) Terrestrial Radio Access Network)) or GERAN (GSM ( It may also function as an anchor point for mobility with Global System for Mobile Communication)/EDGE (Enhanced Data rates for Global Evolution) Radio Access Network).
  • the UPF 44 may correspond to a termination point of a data interface toward a data network.
  • the illustrated PCF 43 is a node that controls the operator's policy.
  • the illustrated AF 45 is a server for providing various services to the UE 100.
  • the illustrated UDM 46 is a kind of server that manages subscriber information, such as a 4G mobile communication HSS (Home Subscriber Server).
  • the UDM 46 stores and manages the subscriber information in a Unified Data Repository (UDR).
  • UDR Unified Data Repository
  • the illustrated SMF 42 may perform a function of allocating an Internet Protocol (IP) address of the UE.
  • the SMF 42 may control a protocol data unit (PDU) session.
  • IP Internet Protocol
  • PDU protocol data unit
  • 5G mobile communication supports a number of numerology or subcarrier spacing (SCS) to support various 5G services. For example, when the SCS is 15 kHz, it supports a wide area in traditional cellular bands, and when the SCS is 30 kHz/60 kHz, it is dense-urban, lower latency. And a wider carrier bandwidth (wider carrier bandwidth) is supported, and when the SCS is 60 kHz or higher, a bandwidth greater than 24.25 GHz is supported to overcome phase noise.
  • SCS subcarrier spacing
  • the NR frequency band may be defined as a frequency range of two types (FR1, FR2).
  • the numerical value of the frequency range may be changed, for example, the frequency range of the two types (FR1, FR2) may be as shown in Table 1 below.
  • FR1 may mean “sub 6GHz range”
  • FR2 may mean “above 6GHz range” and may be called millimeter wave (mmW). .
  • mmW millimeter wave
  • FR1 may include a band of 410MHz to 7125MHz 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.) or higher included in FR1 may include an unlicensed band.
  • the unlicensed band can be used for a variety of purposes, and can be used, for example, for communication for vehicles (eg, autonomous driving).
  • FIG. 2 is an exemplary diagram showing 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 radio access network (RAN).
  • DN data network
  • RAN next-generation radio access network
  • the illustrated control plane function (CPF) node is all or part of the functions of a mobility management entity (MME) of 4G mobile communication, and a control plane function of a serving gateway (S-GW) and a PDN gateway (P-GW). Do all or part of.
  • the CPF node includes an Access and Mobility Management Function (AMF) and a Session Management Function (SMF).
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • the illustrated User Plane Function (UPF) node is a type of gateway through which user data is transmitted and received.
  • the UPF node may perform all or part of the user plane functions of S-GW and P-GW of 4G mobile communication.
  • the illustrated PCF Policy Control Function
  • Policy Control Function is a node that controls the operator's policy.
  • the illustrated application function is a server for providing various services to the UE.
  • the illustrated Unified Data Management is a kind of server that manages subscriber information, such as a 4G mobile communication HSS (Home Subscriber Server).
  • the UDM stores and manages the subscriber information in a Unified Data Repository (UDR).
  • UDR Unified Data Repository
  • the illustrated authentication server function (AUSF) authenticates and manages the UE.
  • the illustrated network slice selection function (NSSF) is a node for network slicing as described below.
  • the illustrated network exposure function is a node for providing a mechanism to securely disclose services and functions of the 5G core.
  • NEF discloses 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
  • Figure 3 shows an architecture for supporting simultaneous access to two data networks It is an exemplary diagram .
  • FIG. 3 an architecture for a UE to access two data networks simultaneously using one PDU session is shown.
  • N1 represents a reference point between the UE and the AMF.
  • N2 represents a reference point between (R)AN and AMF.
  • N3 represents a 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.
  • N7 represents a reference point between the SMF and PCF.
  • N8 represents a reference point between UDM and AMF.
  • N9 represents a reference point between UPFs.
  • N10 represents a reference point between UDM and SMF.
  • N11 represents a reference point between AMF and SMF.
  • N12 represents a reference point between AMF and AUSF.
  • N13 represents a reference point between UDM and AUSF.
  • N14 represents a reference point between AMFs.
  • N15 denotes 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.
  • N22 represents a reference point between AMF and NSSF.
  • N30 represents a reference point between PCF and NEF.
  • N33 represents a reference fit between AF and NEF.
  • AF by a third party other than an operator may be connected to 5GC through NEF.
  • FIG. 4 UE and gNB Another showing the structure of the Radio Interface Protocol It is an exemplary diagram .
  • the air interface protocol is based on the 3GPP radio access network standard.
  • the radio interface protocol is horizontally composed of a physical layer (Physical layer), a data link layer (Data Link layer), and a network layer (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 (layer 1), L2 (layer 2), and L3 (layer 3) based on the lower 3 layers of the Open System Interconnection (OSI) reference model widely known in communication systems. ) Can be separated.
  • 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.
  • data is transmitted 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 third layer includes Radio Resource Control (hereinafter abbreviated as RRC).
  • RRC Radio Resource Control
  • the RRC layer is defined only in the control plane, and is related to setting (setting), resetting (Re-setting) and release (Release) of radio bearers (Radio Bearer; RB).
  • Radio Bearer Radio Bearer
  • RB means a service provided by the second layer for data transmission between the UE and the E-UTRAN.
  • the NAS (Non-Access Stratum) layer performs functions such as connection management (session management) and mobility management.
  • the NAS layer is divided into a NAS entity for mobility management (MM) and a NAS entity for session management (SM).
  • MM mobility management
  • SM session management
  • NAS entity for MM provides the following functions in general.
  • NAS procedures related to AMF including the following.
  • AMF supports the following functions.
  • the NAS entity for the SM performs session management between the UE and the SMF.
  • the SM signaling message is processed, that is, generated and processed at the NAS-SM layer of the UE and SMF.
  • the contents of the SM signaling message are not interpreted by the AMF.
  • the NAS entity for the MM generates a NAS-MM message that derives how and where to deliver the SM signaling message through the security header representing the NAS transmission of SM signaling, and additional information about the receiving NAS-MM.
  • the NAS entity for the SM upon receiving the SM signaling, performs an integrity check of the NAS-MM message, analyzes the additional information, and derives a method and place to derive the SM signaling message.
  • an RRC layer, an RLC layer, a MAC layer, and a PHY layer located below the NAS layer are collectively referred to as an Access Stratum (AS).
  • AS Access Stratum
  • the 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 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 non-3GPP access as well as 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 capable of simultaneously serving 3GPP access and non-3GPP access using one PDU session.
  • the UE needs to obtain authorization in order to enable mobility tracking, enable data reception, and receive services. For this, the UE must register with the network.
  • the registration procedure is performed when the UE needs to do initial registration for the 5G system.
  • the registration procedure is performed when the UE performs periodic registration update, when moving from an idle mode to a new tracking area (TA), and when the UE needs to perform periodic registration update.
  • TA new tracking area
  • the ID of the UE can be obtained from the UE.
  • AMF can deliver PEI (IMEISV) to UDM, SMF and PCF.
  • PEI IMEISV
  • 5A and 5B are signal flow diagrams illustrating an exemplary registration procedure.
  • the UE can transmit an AN message to the RAN.
  • the AN message may include an AN parameter and a registration request message.
  • the registration request message may include information such as registration type, subscriber permanent ID or temporary user ID, security parameters, Network Slice Selection Assistance Information (NSSAI), 5G capability of the UE, and protocol data unit (PDU) session state.
  • NSSAI Network Slice Selection Assistance Information
  • 5G capability of the UE 5G capability of the UE
  • PDU protocol data unit
  • the AN parameter may include a SUPI (Subscription Permanent Identifier) or a temporary user ID, a selected network, and NSSAI.
  • SUPI Subscriber Permanent Identifier
  • NSSAI Network Access Management Function
  • the registration type is "initial registration” (ie, the UE is in a non-registered state), "mobility registration update” (ie, the UE is in a registered state and starts the registration process due to mobility) or "regular registration update” (That is, it may indicate whether the UE is in a registered state and starts a registration procedure due to periodic update timer expiration).
  • the temporary user ID indicates the last serving AMF. If the UE has already been 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 allocated by the AMF during the registration procedure through the non-3GPP access.
  • Security parameters can be used for authentication and integrity protection.
  • the PDU session state may indicate a (previously established) PDU session available in the UE.
  • the RAN may select AMF based on (R)AT and NSSAI.
  • the (R)AN cannot select an appropriate AMF, it selects a random AMF according to local policy, and transmits a registration request to the selected AMF. If the selected AMF cannot serve the UE, the selected AMF selects another AMF more appropriate for the UE.
  • the RAN transmits an N2 message to a new AMF.
  • the N2 message includes an N2 parameter and a registration request.
  • the registration request may include a registration type, a subscriber permanent identifier or a temporary user ID, a security parameter, and a default setting for NSSAI and MICO modes.
  • the N2 parameter includes location information related to a cell in which the UE is camping, a cell identifier, and a RAT type.
  • steps 4 to 17 described below may not be performed.
  • the newly selected AMF may transmit an information request message to the previous AMF.
  • the new AMF can send an information request message containing complete registration request information to the previous 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 transmits an information response message including the SUPI and MM context of the UE.
  • SMF information including the ID of the SMF and the PDU session ID may be included in the information response message in the previous AMF.
  • the new AMF transmits an Identity Request message to the UE if SUPI is not provided by the UE or is not retrieved from the previous AMF.
  • the UE transmits an Identity Response message including the SUPI to the new AMF.
  • AMF may decide to trigger AUSF.
  • AMF may select AUSF based on SUPI.
  • AUSF can 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 UDM based on SUPI.
  • the new AMF After the final registration, if the AMF is changed, there is no valid subscription context for the UE in the AMF, or the UE provides a SUPI that does not refer to a valid context in the AMF, the new AMF starts the update location procedure. . Alternatively, it may be initiated even when the UDM initiates a cancel location for the previous AMF.
  • the old AMF discards the MM context and notifies all possible SMF(s), and the new AMF creates an MM context for the UE after obtaining the AMF-related subscription data from the UDM.
  • the AMF When network slicing is used, the AMF obtains the allowed NSSAI based on the requested NSSAI, UE subscription and local policy. If AMF is not suitable to support the allowed NSSAI, it will reroute the registration request.
  • the new AMF can select a PCF based on SUPI.
  • 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 PCF transmits a UE Context Establishment Acknowledged message to the new AMF.
  • the new AMF transmits an N11 request message to the SMF.
  • the new AMF when the AMF is changed, notifies each SMF of the new AMF serving the UE.
  • the AMF verifies the PDU session state from the UE with available SMF information.
  • usable SMF information may be received from the previous AMF.
  • the new AMF may request the SMF to release network resources related to a PDU session that is not active in the UE.
  • 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 previous AMF may delete the UE context from the PCF.
  • the PCF may transmit a UE Context Termination Request message to the previous AMF.
  • the new AMF transmits a registration acceptance message to the UE.
  • the registration acceptance message may include a temporary user ID, a registration area, mobility restriction, PDU session state, NSSAI, a regular registration update timer, and an allowed MICO mode.
  • the registration acceptance message may include the allowed NSSAI and information of the mapped NSSAI.
  • the allowed NSSAI information on the access type of the UE may be included in an N2 message including a registration acceptance message.
  • the mapped NSSAI information is information obtained by mapping each S-NSSAI of the allowed NSSAI to the S-NASSI of the NSSAI set for HPLMN.
  • a temporary user ID may be further included in the registration acceptance message.
  • information indicating mobility limitation may be additionally included in the registration acceptance message.
  • the AMF may include information indicating the PDU session state for the UE in the registration acceptance message. The UE may remove any internal resources related to a PDU session that is 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 acceptance message.
  • the UE transmits a registration completion message to the new AMF.
  • PDU session establishment procedure there may be two types of PDU session establishment procedures as follows.
  • the network may transmit a device trigger message to the application(s) of the UE.
  • 6A and 6B are exemplary PDU This is a signal flow diagram showing a procedure for establishing a session.
  • the UE transmits a NAS message to 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 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 obtained by mapping each S-NSSAI of the allowed NSSAI to the S-NASSI of the NSSAI set for HPLMN.
  • the UE extracts and stores information of the allowed S-NSSAI and the mapped S-NSSAI included in the registration acceptance message received from the network (ie, AMF) in the registration procedure of FIGS. 7A and 7B Can be doing. Accordingly, the UE may include and transmit both the S-NSSAI based on the allowed NSSAI and the corresponding S-NSSAI based on information of the mapped NSSAI in the PDU session establishment request message.
  • the UE may generate a new PDU session ID.
  • the UE may initiate a PDU session establishment procedure initiated by the UE by transmitting a NAS message including a PDU session establishment request message in 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, when 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 through AMF, and may include user location information and access technology type information.
  • the N1 SM information may include an SM PDU DN request container that includes information on PDU session authentication by an external DN.
  • the AMF may determine that the message corresponds to a request for a new PDU session when the request type indicates "initial request" and when 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 with each other.
  • AMF sends an SM request message to the SMF.
  • the SM request message may include a 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 a subscriber data request message to UDM.
  • the subscriber data request message may include a subscriber permanent ID and DNN.
  • step 3 if the request type indicates "existing PDU session", the SMF determines that the request is due to handover between 3GPP access and non-3GPP access.
  • the SMF can identify an existing PDU session based on the PDU session ID.
  • the SMF may request subscription data.
  • UDM may transmit a subscription data response message to the SMF.
  • the subscription data may include information on an authenticated request type, an authenticated SSC mode, and a basic QoS profile.
  • the SMF can check whether the UE request complies with the user subscription and local policy. Alternatively, the SMF rejects the UE request through NAS SM signaling (including the related 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 related SM rejection cause
  • SMF sends a message to DN through UPF.
  • 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 initiate PDU-CAN session establishment towards the PCF to obtain basic PCC rules 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 of step 3 indicates "initial request", the SMF selects the SSC mode for the PDU session. If step 5 is not performed, the SMF may also select UPF. In case of request type IPv4 or IPv6, SMF may allocate an IP address/prefix for a PDU session.
  • the SMF can start the PDU-CAN session.
  • step 5 If the request type indicates "initial request” and step 5 is not performed, the SMF starts the N4 session establishment procedure using the selected UPF, otherwise the N4 session modification procedure can start using the selected UPF.
  • SMF transmits an N4 session establishment/modification request message to the UPF.
  • the SMF may provide a packet detection, enforcement and reporting rule to be installed in the UPF for the PDU session.
  • CN tunnel information may be provided to the UPF.
  • UPF can respond by transmitting an N4 session establishment/modification response message.
  • CN tunnel information may be provided to the SMF.
  • the SMF transmits an SM response message to the AMF.
  • the message may include 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 acceptance message may include a permitted QoS rule, an SSC mode, an S-NSSAI, and an assigned IPv4 address.
  • the N2 SM information is information that the AMF must deliver to the RAN and may include the following.
  • -CN tunnel information This corresponds to the core network address of the N3 tunnel corresponding to the PDU session.
  • -PDU Session ID This may be used to indicate to the UE the association between the PDU session and AN resources for the UE by AN signaling for the UE.
  • the N1 SM information includes a PDU session acceptance message that the AMF must provide to the UE.
  • Multiple QoS rules may be included in the N1 SM information and the N2 SM information in the PDU session establishment acceptance message.
  • the SM response message also contains information that allows the PDU session ID and AMF to determine which target UE as well as which access should be used for the UE.
  • AMF transmits an N2 PDU session request message to the RAN.
  • the message may include N2 SM information and 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 acceptance message. Also, the AMF includes received N2 SM information from the SMF in the N2 PDU session request message and transmits it to the RAN.
  • the RAN may exchange specific signaling with the UE related to information received from the SMF.
  • the RAN also allocates RAN N3 tunnel information for the PDU session.
  • the RAN delivers the NAS message provided in step 10 to the UE.
  • the NAS message may include PDU session ID and N1 SM information.
  • the N1 SM information may include a PDU session establishment acceptance message.
  • the RAN transmits a NAS message to the UE only when necessary RAN resources are set and allocation of RAN tunnel information is successful.
  • 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.
  • -RAN tunnel information may correspond to the access network address of the N3 tunnel corresponding to the PDU session.
  • the AMF may transmit an SM request message to the SMF.
  • the SM request message may include N2 SM information.
  • the AMF may be to transmit 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 can start the N4 session modification procedure using UPF.
  • SMF may provide AN tunnel information and CN tunnel information. CN tunnel information may be provided only when the SMF selects CN tunnel information in step 8.
  • the UPF may transmit an N4 session establishment/modification response message to the SMF.
  • the SMF may transmit an SM response message to the AMF.
  • the AMF can deliver the related event to the SMF. Occurs at handover when RAN tunnel information is changed or AMF is relocated.
  • SMF transmits information to the 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.
  • UDM can store SMF's ID, address, and related DNN.
  • the SMF During the procedure, if the PDU session establishment is not successful, the SMF notifies the AMF.
  • the 5G system can provide a single unified access control for operators to control access based on access ID and access category.
  • each access attempt may be categorized into one or more access IDs and one access category. Based on the access ID corresponding to the access attempt and the access control information available for the access category corresponding to the access attempt, the terminal (eg, the UE) may test whether an actual access attempt can be made.
  • the terminal eg, the UE
  • Unified access control supports extensibility to include additional standardized access IDs and additional standardized access categories.
  • the integrated access control supports the flexibility of the operator to define an access category using the operator's own criterion.
  • the 5G system may prevent a terminal (eg, a UE) from accessing the network by using an access ID and a related barring parameter that varies according to an access category.
  • a terminal eg, a UE
  • the access ID may be set in the UE as shown in Table 3 below.
  • the access category may be defined as a combination of a condition related to the UE and a type of access attempt, as shown in Table 4 below. One or more access IDs and one access category can be selected and tested for an access attempt.
  • Table 3 below shows an example of an access ID that can be set in the UE.
  • Access Identity number UE configuration 0 UE is not configured with any parameters from this table.
  • UE is configured for Multimedia Priority Service (MPS).
  • MPS Multimedia Priority Service
  • MCS Mission Critical Service
  • UE is configured for MCS 3-10 Reserved for future use 11
  • Access Class 11 is configured in the UE.
  • 12 (NOTE 3) Access Class 12 is configured in the UE.
  • 13 (NOTE 3) Access Class 13 is configured in the UE.
  • 14 (NOTE 3) Access Class 14 is configured in the UE.
  • 15 (NOTE 3) Access Class 15 is configured in the UE.
  • NOTE 1 Access ID 1 can be used by UEs configured for MPS in PLMNs whose configuration is valid.
  • PLMNs for which the configuration is valid may be HPLMNs, PLMNs equivalent to HPLMNs, and visted PLMNs of a home country. Access ID 1 may also be valid when the UE is explicitly authenticated based on the PLMN set inside and outside the local station.
  • Access ID 2 may be used by the UE configured for the MCS in PLMNs for which the configuration is valid. have.
  • PLMNs for which the configuration is valid may be HPLMNs, PLMNs equivalent to HPLMNs, and visted PLMNs of a home country. Access ID 2 may also be valid when the UE is explicitly authenticated based on the PLMN set inside and outside the local station.
  • Access IDs 11 and 15 are Home when the EHPLMN (Equivalent HPLMN) list does not exist. It can be valid in PLMN, or it can be valid in any EHPLMN. Access IDs 12, 13, and 14 may be valid only in Home PLMNs and visited PLMNs of the host country. To this end, a mother station may be defined as a country of a mobile country code (MCC) part of an international mobile subscriber identity (IMSI).
  • MCC mobile country code
  • IMSI international mobile subscriber identity
  • Table 4 shows an example of an access category that can be defined as a combination of a condition related to a UE and a type of an access attempt.
  • the UE is set for a delay tolerant service, and may be an object of access control for access category 1 (an object of access control determined according to the relationship between the HPLMN of the UE and the selected PLMN).
  • a barring parameter for access category 1 may be accompanied by information defining whether to apply to one of the following categories: a) UEs configured for delay-allowed service; b) Delay UEs set for allowed service and not in PLMN equivalent to HPLMN or HPLMN; c) “most preferred PLMN of countries set for delay allowed service and roaming within the operator-defined PLMN selector list of SIM/USIM UEs that are
  • the UE When the UE is configured for both EAB and EAB override, if a higher layer (eg, application layer) indicates to override access category 1, access category 1 is not applicable. (When a UE is configured for EAB, the UE is also configured for delay tolerant service.In case a UE is configured both for EAB and for EAB override, when upper layer indicates to override Access Category 1, then Access Category 1 is not applicable .)
  • NOTE 2 If there are both an access category based on a carrier classification in which an access attempt can be classified and an access category based on a standardized access category, and the standardized access category is not 0 or 2, the UE is based on the operator classification. To apply the access category.
  • the UE applies the standardized access category.
  • NOTE 3 Real-Time Text (RTT) included.
  • NOTE 4 IMS Messaging included.
  • the 5G network may broadcast barring control information in one or more areas of the RAN.
  • the blocking control information may be, for example, an access ID and a list of blocking parameters related to the access category.
  • the UE is a specific new access attempt based on the blocking parameter (received from the broadcast blocking control information by the UE) and the UE's settings. You can decide whether or not is allowed.
  • the RAN may individually apply access control to different core networks.
  • the unified access control framework may be applicable to both a UE accessing a 5G Core Network (CN) using E-UTRA and a UE accessing 5G CN using NR.
  • CN 5G Core Network
  • the integrated access control framework may be applicable to a UE in a Radio Resource Control (RRC) Idle state, an RRC Inactive (inactive) state, and an RRC Connected state when the UE starts a new access attempt (eg, a new session request).
  • RRC Radio Resource Control
  • request for a new session in the RRC Connected state may mean an event.
  • the event is a new MMTEL voice session, MMTEL video session, transmission of SMS (SMS over IP, or SMS over NAS), establishment of a new PDU session, modification of an existing PDU session, and user plane for an existing PDU session. It may be a service request for re-establishing (re-establish).
  • the 5G system may support a means by which an operator can define an operator-defined access category as mutually exclusive.
  • examples of the criteria for the operator-defined access category may be network slicing, applications, and application servers.
  • the unified access control framework may be applicable to inbound roamers to the PLMN.
  • the serving PLMN may provide the definition of the operator-defined access category to the UE.
  • the UE may first perform an access control check to determine whether access is allowed. Access control checks can be performed on access attempts defined by a list of events such as:
  • the NAS layer of the terminal (e.g. 5GMM) is MO-MMTEL-voice-call-started information/indication from the upper layer (e.g., application layer), MO-MMTEL-video-call-started When information/indication or MO-SMSoIP-attempt-started information/indication is received;
  • the NAS layer of the terminal receives a request to transmit mobile originated SMS over NAS from a higher layer (e.g., application layer), and the request sends the UE in 5GMM-IDLE mode When not triggering a service request to switch to 5GMM-CONNECTED mode;
  • the NAS layer (e.g., 5GMM) of the terminal receives a request to transmit a UL NAS TRANASPORT message for the purpose of establishing a PDU session from an upper layer (e.g., application layer), and the request is 5GMM- When not triggering a service request to switch from IDLE mode to 5GMM-CONNECTED mode;
  • an upper layer e.g., application layer
  • the NAS layer (e.g., 5GMM) of the terminal receives a request to transmit a UL NAS TRANASPORT message for the purpose of PDU session modification from a higher layer (e.g., application layer), and the request is 5GMM- When not triggering a service request to switch from IDLE mode to 5GMM-CONNECTED mode;
  • the NAS layer of the terminal may perform an operation of mapping one or more access IDs and a kind of request to an access category. Further, a lower layer of the terminal (eg, an RRC layer) may perform an access barring check on the request based on the determined access ID and access category. For reference, the NAS layer of the terminal may recognize the above-described events through information/indication provided from an upper layer and/or when determining that normal NAS operation needs to be started.
  • the NAS layer of the terminal includes a set of access IDs and a reason for access to the set of access categories, the type of the requested service, and the UE's configuration. You can check the profile.
  • an example of the set of the access ID and the set of the access category is as follows:
  • the terminal e.g., UE
  • the terminal When the terminal (e.g., UE) needs to initiate an access attempt to one of the events as examples of a) to b-6) above, the terminal is one related to the access attempt in a set of standardized access IDs.
  • the above access ID may be determined, and one access category related to the access attempt may be determined from a set of standardized access categories and a set of operator-defined access categories.
  • the set of access IDs available for a request related to an access attempt may be determined by the terminal (eg, UE) in the following manner:
  • the UE will check whether the access ID is available in the selected PLMN when a new PLMN is selected. I can. Or the UE may check whether the access ID is applicable to the RPLMN or equivalent PLMN; And
  • access ID 0 If there is no available access ID among the access IDs 1, 2, 11, 12, 13, 14, and 15, access ID 0 can be used.
  • the NAS layer of the terminal may check a rule as shown in Table 5 below, and use a matching access category for a barring check.
  • Table 5 below is an example of rules used when the NAS layer of the terminal determines an available access category for an access attempt.
  • LTP LTE Positioning Protocol
  • the UE is set for low priority NAS signaling (UE is configured for NAS signaling low priority) or the UE supporting S1 mode is set for EAB (Extended Access Barring) not applied "EAB override" (B)
  • the UE receives one of categories a, b, or c as part of a parameter for integrated access control in broadcast system information (e.g., broadcast barring control information), and the UE Is a member of a broadcast category within the selected PLMN or RPLMN/equivalent PLMN.
  • broadcast system information e.g., broadcast barring control information
  • the 5GMM connection management procedure required to re-establish the network may be included.
  • this may include a service request procedure initiated by a SERVICE REQUEST message in which the service type IE is set to "emergency services fallback".
  • RRC establishment RRC establishment cause
  • the selected PLMN may be used to check membership; Otherwise, the UE may use RPLMN or PLMN equivalent to the RPLMN.
  • This may include a 5GMM connection management procedure triggered by a UE-initiated NAS transport procedure for transmitting MO SMS.
  • NOTE5 Available access categories for access attempts. In case of 1, the UE may further determine a second access category in the range of 3 to 7. If more than one access category matches, the access category with the lowest rule number will be selected. The UE may use the second access category only to detect the reason for establishing the RRC for the access attempt.
  • the UE is not configured to allow overriding the EAB, or the NAS layer of the UE is a higher layer.
  • the UE In the case of not receiving an indication to override the EAB from (eg, the application layer), if the UE does not have a PDU session established based on the EAB override, “EAB override” may not be applied.
  • an access category having the lowest rule number among the one or more rules may be selected. If the access attempt matches one or more operator-defined access category definitions, the UE may select the operator-defined access category definition having the lowest precedence value.
  • the case where one access attempt matches one or more rules may include a case in which a plurality of events trigger one access attempt at the same time.
  • the NAS layer of the terminal is Upon receiving a request for an access attempt from a higher layer, the NAS layer of the terminal may classify the access attempt into an access ID and an access category according to the examples of Tables 4 and 5 described above.
  • the NAS layer of the terminal may forward a request including an available access ID and an available access category to a lower layer (eg, an RRC layer).
  • the lower layer may perform an access blocking check.
  • the NAS layer of the terminal may provide the cause of RRC establishment in the request for the lower layer.
  • the NAS layer of the terminal may provide the RRC establishment cause to the lower layer after receiving a notification that the access attempt is allowed from the lower layer.
  • the NAS layer may initiate a procedure for transmitting an initial NAS message for the access attempt.
  • the NAS layer may not initiate a procedure for transmitting the initial NAS message for the access attempt.
  • the event triggering the access attempt is MO-MMTEL-voice-call-started information/indication, MO-MMTEL-video-call-started information/indication, or MO-SMSoIP-attempt-started information/indication If so, the NAS layer can inform the upper layer (eg, the application layer) that the access attempt has been blocked. In this case, when the NAS layer receives information/indication from a lower layer (eg, RRC layer) that the blocking of the access category related to the access attempt has been relaxed, the NAS layer indicates that the blocking of the access category has been relaxed.
  • a lower layer eg, RRC layer
  • the NAS layer can initiate a procedure for transmitting the initial NAS message if still necessary.
  • a barring timer for each access category may be run by a lower layer.
  • the blocking timer expires, the lower layer may notify the NAS layer of the information/indication that the access blocking has been relaxed to the NAS layer for each access category.
  • the NAS layer of the terminal When the UE is in a 5GMM-CONNECTED mode or a 5GMM-CONNECTED mode with an RRC deactivation indication, when the upper layer of the terminal detects one of the events of b-1) to b-6), the NAS layer of the terminal A request for an access attempt may be received from an upper layer of the terminal. Then, the NAS layer of the terminal may classify the access attempt into an access ID and an access category according to the examples of Tables 4 and 5 described above. For access control checking, the NAS layer of the terminal may forward a request including an available access ID and an available access category to a lower layer (eg, an RRC layer). The lower layer may perform an access blocking check.
  • a lower layer eg, an RRC layer
  • the NAS layer of the terminal may provide the cause of RRC establishment in the request for the lower layer.
  • the NAS layer of the terminal may provide the RRC establishment cause to the lower layer after receiving a notification that the access attempt is allowed from the lower layer.
  • the UE When the UE builds a registration request (REGISTRATION REQUEST) message or a service request (SERVICE REQUEST) message for an access attempt, when the UE has uplink user data pending for one or more PDU sessions , Regardless of the access category in which the access blocking check is performed, the UE may indicate each PDU session in an uplink data state information element (IE). Even when the blocking timer is running for some of the corresponding access categories, the UE may indicate user data waiting for each PDU session.
  • IE uplink data state information element
  • the NAS layer may perform the following operation according to the event triggering the access attempt:
  • the event triggering the access attempt is MO-MMTEL-voice-call-started information/indication, MO-MMTEL-video-call-started information/indication or MO-SMSoIP-attempt-started information/indication If so, the NAS layer may notify the upper layer (eg, the application layer) that the access attempt has been allowed;
  • the NAS layer (e.g., 5GMM layer) transmits the SMS in a UL NAS TRANSPORT message message.
  • the NAS layer (eg, 5GMM layer) may initiate a NAS transport procedure to transmit a PDU session establishment request message. ;
  • the NAS layer (e.g., 5GMM layer) performs a NAS transport procedure to transmit a PDU session modification request message. Can initiate;
  • the NAS layer eg, 5GMM layer
  • the NAS layer may initiate a service request procedure
  • the NAS layer (e.g. 5GMM layer) considers that the uplink user data packet can be transmitted. can do.
  • the NAS layer may perform the following actions according to the event triggering the access attempt:
  • the event triggering the access attempt is MO-MMTEL-voice-call-started information/indication, MO-MMTEL-video-call-started information/indication or MO-SMSoIP-attempt-started information/indication
  • the NAS layer may notify the upper layer that the access attempt has been blocked.
  • the upper layer may prohibit the initiation of the MMTEL voice session, the MMTEL video session, or the transmission of the SMS over IP.
  • the NAS layer receives information/indication from a lower layer (eg, RRC layer) that the blocking of the access category related to the access attempt has been relaxed, the NAS layer indicates that the blocking of the access category has been relaxed. Can inform the hierarchy;
  • the NAS layer (e.g., 5GMM layer) is used to transmit the SMS through the UL NAS TRANSPORT message.
  • the NAS transmission procedure may not be initiated.
  • the NAS layer receives information/indication from a lower layer (e.g., RRC layer) that the blocking of the access category associated with the access attempt has been relaxed, the NAS layer will initiate the NAS transmission procedure if the NAS transmission procedure is still required.
  • a lower layer e.g., RRC layer
  • the NAS layer (e.g., 5GMM layer) may not initiate a NAS transport procedure to transmit a PDU session establishment request message. have.
  • the NAS layer receives information/indication from a lower layer (e.g., RRC layer) that the blocking of the access category associated with the access attempt has been relaxed, the NAS layer will initiate the NAS transmission procedure if the NAS transmission procedure is still required.
  • a lower layer e.g., RRC layer
  • the NAS layer (e.g., 5GMM layer) performs a NAS transport procedure to transmit a PDU session modification request message. May not be disclosed.
  • the NAS layer receives information/indication from a lower layer (e.g., RRC layer) that the blocking of the access category associated with the access attempt has been relaxed, the NAS layer will initiate the NAS transmission procedure if the NAS transmission procedure is still required.
  • a lower layer e.g., RRC layer
  • the NAS layer (e.g., 5GMM layer) performs a service request procedure. May not be disclosed.
  • the NAS layer may initiate a service request procedure if the service request procedure is still required. Can; And
  • the NAS layer (e.g. 5GMM layer) considers that the uplink user data packet can be transmitted. I can't.
  • the NAS layer receives information/indication from a lower layer (eg, an RRC layer) indicating that the blocking of the access category associated with the access attempt has been relaxed, the NAS layer may consider that the blocking of the access category is relaxed.
  • the terminal when the terminal is connected to the IM (IP Multimedia) CN (Core Network) subsystem, a specific example to which the integrated access control is applied is as follows.
  • the IM CN subsystem may mean the core network of the IMS.
  • the upper layer of the terminal (eg, the application layer) can provide information such as the following example to the NAS layer of the terminal:
  • the upper layer of the terminal e.g., application layer
  • MMTEL multimedia telephony
  • the terminal e.g., UE
  • the application layer may transmit the MO-MMTEL-voice-started indication/information to the NAS layer.
  • the upper layer (eg, application layer) of the terminal may continue the session establishment procedure for establishing the MMTEL communication session.
  • the blocking result may be a blocking result for MO-MMTEL-voice-started indication/information transmitted from the NAS layer.
  • the upper layer (eg, application layer) of the terminal rejects the establishment of the MMTEL communication session, and may skip the following steps;
  • the application layer of the UE may transmit the MO-MMTEL-video-started indication/information to the NAS layer.
  • the upper layer (eg, application layer) of the terminal may continue the session establishment procedure for establishing the MMTEL communication session.
  • the upper layer (eg, application layer) of the terminal rejects the establishment of the MMTEL communication session and may skip the following steps.
  • adding or removing media may not be subject to integrated access control.
  • an outgoing MMTEL communication session (audio or real-time text or an outgoing MMTEL communication session that was initiated with both audio and real-time text) is terminated (e.g. due to a response to a BYE message or a failure response to an initial INVITE request message)
  • the application layer of the terminal e.g., UE
  • the outgoing MMTEL communication session (the outgoing MMTEL communication session that was initiated with the video provided) ends (e.g. BYE or the response to the message is due to a failure response to the initial INVITE request message)
  • providing the video e.g., initial INVITE
  • the application layer of the terminal e.g., UE
  • MO-MMTEL-video-ended indication/information to the NAS layer. Can be transferred to.
  • an IP-based session can be controlled by a session initiation protocol (SIP).
  • SIP is a protocol for controlling sessions, and SIP specifies a procedure for communicating terminals to identify each other and find their location, to create a multimedia service session between them, or to delete and change the created session. Refers to the signaling protocol.
  • SIP uses a SIP Uniform Resource Identifier (URI) similar to an e-mail address to identify each user, so that services can be provided without being subordinated to an IP (Internet Protocol) address.
  • URI Uniform Resource Identifier
  • IP Internet Protocol
  • the terminal In order for a terminal using the 3GPP system to receive IMS services such as voice call, video call, and SMS (eg, SMS over IP), the terminal must be registered in the IMS network. In addition, the terminal must periodically re-registration in the IMS network.
  • IMS services such as voice call, video call, and SMS (eg, SMS over IP)
  • the signaling between the terminal and the IMS may be performed through SIP signaling (or IMS signaling) between the IMS layer of the terminal and the core IMS.
  • the IMS layer of the terminal may be a layer included in an application layer of the terminal.
  • the IMS layer of the terminal may be an upper layer based on the NAS layer of the terminal.
  • the application layer of the terminal may also be a higher layer based on the NAS layer of the terminal.
  • the IMS layer of the terminal and the application layer of the terminal may be implemented separately from each other.
  • the IMS layer of the terminal may be included in the application layer of the terminal.
  • the operation performed by the IMS layer of the terminal may also be performed by the application layer of the terminal.
  • IMS signaling may mean signaling between the IMS layer of the terminal and the IMS.
  • This IMS signaling is a user plane or PDN (Packet Data) of a PDU session based on IMS APN (Access Point Name)/DNN (Data Network Name) (when a terminal performs 5GS (5G System)-based communication).
  • Network when the terminal performs EPS-based communication may be performed through the user plane.
  • the IMS layer of the terminal may transmit related information or indication to the attempt related to the IMS service to the NAS layer of the terminal.
  • the attempt related to the IMS service may mean an attempt related to the IMS service such as multimedia telephony (MMTEL) voice, MMTEL video, and SMS.
  • MMTEL multimedia telephony
  • the NAS layer of the terminal may determine an access category of an attempt related to the IMS service based on the information or indication received from the IMS layer of the terminal.
  • the access category related to the IMS service is 4 (for example, an access category related to MO (Mobile Originated) MMTel voice), 5 (for example, an access category related to MO MMTel video), 6 (for example, MO SMS or SMSoIP ( SMS over IP) related access category).
  • the NAS layer of the terminal may determine the access category according to the information or indication delivered by the IMS layer of the terminal.
  • the NAS layer of the terminal may deliver the information or indication transmitted by the IMS layer of the terminal and information on the determined access category to the RRC layer of the terminal.
  • the RRC layer of the terminal is based on information on the access category transmitted by the NAS layer of the terminal, system information block (SIB) information broadcast by the base station, and access control information (e.g., unified access control information). Barring check) can be performed.
  • SIB system information block
  • the RRC layer of the terminal may deliver information on whether to barring the access category delivered by the NAS layer to a higher layer (eg, the NAS layer).
  • the NAS layer of the terminal may transmit information that the access category is barred to the IMS layer.
  • IMS signaling e.g., initial registration, re-registration, subscription refresh, etc.
  • IMS service e.g., MMTEL (multimedia telephony) voice, MMTEL video, SMS, etc.
  • IMS signaling may need to be delivered.
  • IMS signaling that is not an actual attempt related to the IMS service will be referred to as IMS signaling for a non-service attempt.
  • the IMS layer of the terminal generally contains information on IMS signaling for non-service attempts and user data for a general IMS-related PDU session or PDN connection without interaction between a separate IMS layer and a NAS layer. Information that has occurred can be delivered to the NAS layer of the terminal.
  • the terminal transmits information that user data has occurred through the user plane to the IMS (when the terminal is connected to the IMS) or the terminal performs a connected transition procedure (e.g., the terminal In the case of the idle state or the connected with inactive indication state, the terminal may perform a procedure for transitioning to the connected state).
  • a connected transition procedure e.g., the terminal In the case of the idle state or the connected with inactive indication state, the terminal may perform a procedure for transitioning to the connected state.
  • the NAS layer of the terminal uses category 7 (MO data) for IMS signaling transmission for non-service attempts.
  • the NAS layer of the terminal may deliver information on IMS signaling and access category information (category 7) for non-service attempts to the RRC layer of the terminal.
  • category 7 category 7
  • the category for general data transmission e.g., category 7 (MO data)
  • category 4 ⁇ 6, etc. Since the priority is likely to be low compared to the service related category), it is likely to be barred by the RRC layer.
  • a policy for priority between a plurality of access categories may be set (or may be preset).
  • a network node eg, AMF
  • AMF network node
  • the probability of blocking for each access category may differ, and it is highly likely that the access category with a lower priority is first blocked.
  • FIG. 7 is a signal flow diagram illustrating an example of a problem to be solved by the disclosure of the present specification.
  • the following drawings are made to explain an example of a problem to be solved by the disclosure of the present specification. Since the names of specific devices or names of specific signals/messages/fields described in the drawings are provided by way of example, technical features of the present specification are not limited to specific names used in the following drawings.
  • a terminal may include an IMS layer, a NAS layer, and an RRC layer.
  • the IMS layer may determine that IMS signaling for non-service attempts is required.
  • IMS signaling for non-service attempts may be IMS signaling according to the purpose of initial registration, re-registration, and subscription refresh.
  • the IMS layer may transmit a request message for a PDU session for transmitting IMS signaling to the NAS layer in order to transmit IMS signaling for a non-service attempt.
  • the request message may be transmitted to activate a user plane for data transmission by the terminal.
  • the IMS layer may request activation of a PDU session using a request message.
  • the terminal may be in a CM (Connection Management)-IDLE state, or the terminal may be in a state in which activation of the user plane is required in the CM-Connected state.
  • the request message may also include information related to outgoing data.
  • Information related to outgoing data may indicate information that user data has occurred.
  • Information related to outgoing data may include information called MO data (corresponding to access category 7).
  • the NAS layer may use the access category 7 for IMS signaling for non-service attempts from the IMS layer to the NAS layer.
  • the NAS layer may transmit a request message (including information on access category 7) to the RRC layer.
  • the RRC layer may be in a state in which access control is being applied due to a network congestion situation or the like. Since the RRC layer has received information on the access category 7 from the NAS layer, it may perform an access control check based on the access category 7. This category for general data transmission (e.g., access category 7 (MO data)) has a lower priority than other access categories (e.g., categories related to IMS services such as access categories 4-6), so it is barred by the RRC layer. Is likely to be. For example, when access control is applied to the RRC layer, priorities for a plurality of access categories may be set (or may be set in advance), and the network and/or terminal may have a specific access category (eg, category 5). When access control is applied to the network and/or the terminal, the network and/or the terminal may barring access related to a specific access category and an access category 7 having a lower priority than the specific access category.
  • MO data access category 7
  • the network and/or the terminal may barring access related to a specific
  • the RRC layer may transmit a response message to the NAS layer.
  • the response message may include information indicating that the request message transmitted by the NAS layer in step S703 is barred.
  • the NAS layer may transmit a response message to the IMS layer.
  • the response message may include information that the request message transmitted by the IMS layer is barred in step S702.
  • an access attempt related to IMS signaling for a non-service attempt may fail. Since the attempt to access the IMS, such as re-registration, has failed, it may be impossible for the terminal to use the IMS-related service.
  • differentiated access control eg, congestion control
  • IMS services such as voice, video, and SMS.
  • the terminal can register with the IMS.
  • IMS registration message such as SIP REGISTER
  • the terminal can register with the IMS.
  • the terminal is not provided with the IMS service because there is no.
  • the terminal cannot use services that are very important to the user such as voice call.
  • the SIP signal may be used interchangeably with the IMS signal.
  • the IMS layer of the terminal may need to transmit SIP (Session Initiation Protocol) signaling (or IMS signaling) (that is, the IMS layer of the terminal may need to transmit SIP signaling (or IMS signaling)).
  • SIP Session Initiation Protocol
  • IMS signaling IMS signaling
  • the SIP signaling (or IMS signaling) is not a call attempt related to MMTEL voice (eg, SIP INVITE), a call attempt related to MMTEL video (eg, SIP INVITE), or SMS over IP (eg, SIP MESSAGE).
  • SIP signaling or IMS signaling
  • IMS signaling may have the same meaning.
  • SIP signaling for IMS services such as a call attempt related to MMTEL voice (eg, SIP INVITE), a call attempt related to MMTEL video (eg, SIP INVITE), or SMS over IP (eg, SIP MESSAGE) )
  • SIP signaling for service attempt
  • an access category related to the corresponding SIP signaling may be defined.
  • an access category of MO MMTEL voice related signaling may be 4
  • an access category of MO MMTel video related signaling may be 5
  • an access category of MO SMS or MO SMSoIP related signaling may be 6.
  • SIP signaling (or IMS signaling) that is not an actual attempt related to the IMS service may be, for example, a SIP REGISTER for initial registration or re-registration, or a SIP SUBSCRBE for refreshing a subscription.
  • SIP signaling (or IMS signaling) that is not an actual attempt related to the IMS service will be referred to as SIP signaling (or IMS signaling) for a non-service attempt.
  • SIP signaling (or IMS signaling) for a non-service attempt may be SIP signaling (or IMS signaling) other than SIP signaling (or IMS signaling) for the service attempt.
  • SIP signaling and IMS signaling may be used interchangeably.
  • the IMS layer of the terminal includes information related to outgoing data to the NAS layer of the terminal You can send a request message.
  • Information related to outgoing data may indicate information that user data has occurred.
  • Information related to outgoing data may include information called MO data (corresponding to access category 7).
  • the IMS layer After the IMS layer transmits a request message including information related to the outgoing data to the NAS layer, information indicating that the request message has been blocked may be received from the NAS layer (eg, step S706 in FIG. 7 ).
  • the IMS layer may operate as follows.
  • the IMS layer may not retry transmission of IMS signaling (eg, "SIP signaling for non-service attempts (or IMS signaling)").
  • the IMS layer may remember that the transmission of IMS signaling (eg, "SIP signaling for non-service attempts (or IMS signaling)”) has failed.
  • the IMS layer may store information that IMS signaling (eg, "SIP signaling for non-service attempts (or IMS signaling)" has failed.
  • the IMS layer may store information indicating that IMS signaling (eg, "SIP signaling for non-service attempts (or IMS signaling)”) has failed in a flag form or in various forms.
  • IMS signaling eg, "SIP signaling for non-service attempts (or IMS signaling)
  • the IMS layer may store information that IMS signaling has failed in the form of a flag. If the flag is set (if the flag value is 1), the stored flag may indicate that previously required IMS signaling (eg, "SIP signaling for non-service attempts (or IMS signaling)”) has failed.
  • the IMS layer may also store the type of IMS signaling that has failed in transmission (eg, SIP REGISTER for initial registration or re-registration, SIP SUBSCRIBE for subscription refresh, etc.).
  • the IMS layer may store information that IMS signaling (eg, "SIP signaling for non-service attempts (or IMS signaling)”) has failed and information about the type of signaling that has failed to transmit.
  • the IMS layer may also store information related to the access category (eg, access category 7 (MO data)) used for IMS signaling (eg, "SIP signaling for non-service attempts (or IMS signaling)”). have.
  • access category 7 access category 7 (MO data)
  • SIP signaling for non-service attempts or IMS signaling
  • the IMS layer may store the message itself (eg, a request message in S702 of FIG. 7) related to IMS signaling (eg “SIP signaling (or IMS signaling) for non-service attempts”) that failed to be transmitted in a queue.
  • IMS signaling eg “SIP signaling (or IMS signaling) for non-service attempts”
  • a time limit for storing the message may be determined according to the implementation of the terminal, the configuration of the terminal, and/or the operator policy.
  • the stored message may be deleted when a reset event of the terminal occurs.
  • the reset event may be any one of power off/power on of the terminal, USIM removal, deregistration/detach, and registration/attach for the 3GPP system.
  • FIG. 8 is an exemplary signal flow diagram illustrating the disclosure of the present specification.
  • a terminal may include an IMS layer, a NAS layer, a Packet Data Convergence Protocol (PDCP) layer, and an RRC layer.
  • IMS Internet Multimedia Subsystem
  • NAS Non-Fi Protected Access
  • PDCP Packet Data Convergence Protocol
  • RRC Radio Resource Control
  • the IMS layer may determine that IMS signaling for non-service attempts is required.
  • IMS signaling for non-service attempts may be IMS signaling according to the purpose of initial registration, re-registration, and subscription refresh.
  • the IMS layer may transmit a first request message to the NAS layer.
  • the first request message may include information related to outgoing data.
  • Information related to outgoing data may indicate information that user data has occurred.
  • Information related to outgoing data may include information called MO data (corresponding to access category 7).
  • the NAS layer may determine an access category of the first request message as an access category 7 based on information related to the origination data. For example, the NAS layer of the terminal may allocate access category 7 to the first request message. In addition, the NAS layer of the terminal may request a barring check for the first request message from a lower layer (eg, an RRC layer) based on access category 7. The NAS layer may transmit the first request message to the RRC layer.
  • the first request message transmitted by the NAS layer may include information on the access category category 7.
  • the RRC layer may be in a state in which access control is being applied due to a network congestion situation or the like. Since the RRC layer has received information on the access category 7 from the NAS layer, it may perform an access control check based on the access category 7.
  • This category for general data transmission (e.g., access category 7 (MO data)) has a lower priority than other access categories (e.g., categories related to IMS services such as access categories 4-6), so it is barred by the RRC layer. Is likely to be.
  • access category 7 (MO data)
  • priorities for a plurality of access categories may be set (or may be set in advance), and the network and/or terminal may have a specific access category (eg, category 5).
  • the network and/or the terminal may barring access related to a specific access category and an access category 7 having a lower priority than the specific access category.
  • the RRC layer may transmit a response message to the NAS layer.
  • the response message may include information indicating that the first request message transmitted by the NAS layer in step S803 is barred.
  • the NAS layer may transmit a response message to the IMS layer.
  • the response message may include information indicating that the first request message transmitted by the IMS layer is barred in step S802.
  • the IMS layer may store information that "SIP signaling for non-service attempt (or IMS signaling)" has failed.
  • the IMS layer may store information that IMS signaling (eg, "SIP signaling for non-service attempts (or IMS signaling)”) has failed in a flag form or in various forms.
  • the IMS layer may store information that IMS signaling has failed in the form of a flag. If the flag is set (if the flag value is 1), the stored flag may indicate that previously required IMS signaling (eg, "SIP signaling for non-service attempts (or IMS signaling)”) has failed.
  • the IMS layer may also store the type of IMS signaling that has failed in transmission (eg, SIP REGISTER for initial registration or re-registration, SIP SUBSCRIBE for subscription refresh, etc.).
  • the IMS layer may store information that IMS signaling (eg, "SIP signaling for non-service attempts (or IMS signaling)”) has failed and information about the type of signaling that has failed to transmit.
  • the IMS layer may also store information related to the access category (eg, access category 7 (MO data)) used for IMS signaling (eg, "SIP signaling for non-service attempts (or IMS signaling)”). have.
  • access category 7 access category 7 (MO data)
  • SIP signaling for non-service attempts or IMS signaling
  • the IMS layer may store the message itself (eg, a request message in S702 of FIG. 7) related to IMS signaling (eg “SIP signaling (or IMS signaling) for non-service attempts”) that failed to be transmitted in a queue.
  • IMS signaling eg “SIP signaling (or IMS signaling) for non-service attempts”
  • a time limit for storing the message may be determined according to the implementation of the terminal, the configuration of the terminal, and/or the operator policy.
  • the stored message may be deleted when a reset event of the terminal occurs.
  • the reset event may be any one of power off/power on of the terminal, USIM removal, deregistration/detach, and registration/attach for the 3GPP system.
  • a terminal performed after the IMS layer stores information that "SIP signaling for non-service attempts (or IMS signaling)" has failed, and/or The operation of the network node will be described.
  • a SIP signaling (or IMS signaling) request for service attempt may be generated.
  • a user who actually uses the terminal requests an IMS service (eg, voice call/video call/SMS).
  • an IMS service eg, voice call/video call/SMS.
  • the operation described in the first example of the disclosure of the present specification may be performed.
  • the IMS layer of the terminal may store information indicating that "SIP signaling for non-service attempt (or IMS signaling)" has previously failed.
  • SIP signaling or IMS signaling
  • the IMS layer of the terminal previously failed to "SIP signaling for a non-service attempt (or IMS signaling)", so SIP signaling for a non-service attempt (Or IMS signaling)" may be determined to be transmitted.
  • the IMS layer of the terminal must first perform SIP signaling for a service attempt (or IMS signaling), which must be performed first in order to perform SIP signaling for a non-service attempt (or IMS signaling)" exists, so it can be determined to transmit "SIP signaling for non-service attempts (or IMS signaling)" (eg, when IMS registration is required because the terminal is not registered in the IMS network).
  • SIP signaling for non-service attempts or IMS signaling
  • the IMS layer of the terminal may transmit "SIP signaling for non-service attempt (or IMS signaling)".
  • the IMS layer of the terminal may provide one or more of the following a) and/or b) to the NAS layer of the terminal.
  • SIP signaling for non-service attempts or IMS signaling
  • the IMS layer of the terminal is "for non-service attempts”
  • one or more of the following information a) and/or b) may be provided to the NAS layer of the terminal.
  • the IMS layer of the terminal may transmit a second request message including information related to "SIP signaling for non-service attempts (or IMS signaling)" to the NAS layer in step S902 of FIG. 9. .
  • the information related to "SIP signaling for non-service attempt (or IMS signaling)" may include one or more of the following a) and/or b).
  • the information related to "SIP signaling for non-service attempt (or IMS signaling)" includes only a)
  • the information related to "SIP signaling for non-service attempt (or IMS signaling)" is generated IMS service attempt It may have the same meaning as information and/or indication related to.
  • SIP signaling for non-service attempts refers to b) accompanying IMS service ( Alternatively, it may have the same meaning as information/indication indicating (or notifying) that "SIP signaling for non-service attempts (or IMS signaling)" followed by an IMS service and information on a corresponding IMS service.
  • the terminal may provide information and/or indications related to the generated IMS service attempt to the NAS layer in order for the IMS layer to perform "SIP signaling (or IMS signaling) for non-service attempts".
  • the IMS layer of the terminal may provide conventional information/indication related to the generated IMS service attempt.
  • the IMS layer of the terminal may provide "MO-MMTEL-voice-started" information/indication to the NAS layer of the terminal.
  • information provided by the IMS layer of the terminal to the NAS layer of the terminal may be newly defined.
  • information that SIP signaling (or IMS signaling) is related to the generated IMS service attempt may be defined.
  • the IMS layer of the terminal may provide information/indication of MO-MMTE-voice related SIP signaling (or IMS signaling) to the NAS layer.
  • the IMS layer of the terminal is information/indication indicating (or notifying) that "SIP signaling (or IMS signaling) for non-service attempts" accompanying the IMS service (or followed by the IMS service) and information on the corresponding IMS service Can be provided to the NAS layer of the terminal.
  • the IMS layer of the terminal when the generated IMS service attempt is related to the MMTEL voice, the IMS layer of the terminal must perform SIP signaling (or IMS signaling) for the service attempt for the MMTEL voice. In this case, the IMS layer of the terminal must transmit a SIP REGISTER ("SIP signaling for non-service attempts (or IMS signaling)") for IMS registration before performing SIP signaling (or IMS signaling) for service attempts. I can.
  • SIP REGISTER SIP signaling for non-service attempts (or IMS signaling)
  • the IMS layer of the terminal If the IMS layer of the terminal must first transmit the SIP REGISTER for IMS registration, the IMS layer of the terminal provides information related to "SIP signaling (or IMS signaling) for non-service attempts" and information related to "MMTEL voice". It can be provided to the NAS layer.
  • the IMS layer of the terminal may provide information in the form of "SIP signaling (or IMS signaling) for non-service attempt" related to the IMS service attempt to the NAS layer.
  • the IMS layer of the terminal may provide implicit information such as "SIP signaling (or IMS signaling) followed by MMTEL voice for non-service attempts" to the NAS layer.
  • the IMS layer of the terminal may provide one or more of a) and/or b) to the NAS layer of the terminal.
  • the IMS layer of the terminal may include one or more of a) and/or b) in a request message requesting "SIP signaling for non-service attempt (or IMS signaling)".
  • the IMS layer of the terminal may provide (or transmit) the request message to the NAS layer of the terminal.
  • the request message related to "SIP signaling for non-service attempts (or IMS signaling)" is actually based on the occurrence of the IMS service attempt. It can be interpreted as a request.
  • the NAS layer may interpret the request message as a request message related to "SIP signaling for non-service attempts (or IMS signaling)", but is transmitted because an IMS service attempt has actually occurred. That is, the request message is not transmitted for the purpose of simply transmitting "SIP signaling (or IMS signaling) for non-service attempt", but may be regarded as a request according to an actual IMS service related access attempt.
  • the NAS layer may receive a request message including information of one or more of a) and/or b) described above.
  • the NAS layer may attempt access based on one or more of information a) and/or b) provided by the IMS layer.
  • the NAS layer may determine the access category of the request message transmitted by the IMS layer of one or more of a) and/or b).
  • the NAS layer may attempt access by using access category 4.
  • the NAS layer may transmit a request message including information on access category 4 to the RRC layer.
  • the RRC layer may perform an access control check based on the access category 4. After the RRC layer performs the access control check, the result of the access control check may be transmitted to the NAS layer.
  • the NAS layer may receive information indicating that the request message (or access request) has been accepted from the RRC layer. The NAS layer may transmit information that the request message (or access request) has been accepted to the IMS layer. Then, the IMS layer of the terminal may successfully transmit "SIP signaling for non-service attempts (or IMS signaling)" based on the IMS PDU session and/or PDN connection associated with the IMS service. After the transmission of "SIP signaling (or IMS signaling) for non-service attempt" is successful, the terminal can use the IMS service according to the IMS service attempt. For example, the IMS layer of the terminal successfully performs "SIP signaling for non-service attempts (or IMS signaling)" and then performs SIP signaling (or IMS signaling) for IMS service attempts to use the IMS service. I can.
  • the IMS layer may reset the stored/marked/set/displayed “signaling transmission failure” flag from 1 to 0.
  • the IMS layer may delete information on the type of IMS signaling that failed to be transmitted.
  • the IMS layer also stores information related to the access category (eg, access category 7 (MO data)) used for IMS signaling (eg "SIP signaling for non-service attempts (or IMS signaling)"
  • IMS The layer can delete information related to the access category.
  • the IMS layer stores the message itself (eg, the request message in S702 of Fig. 7) related to the IMS signaling (eg, "SIP signaling for non-service attempts (or IMS signaling)" that failed to be transmitted in the queue
  • the IMS layer may delete the IMS signaling related message itself that has failed to transmit.
  • FIG. 9 is an exemplary signal flow diagram illustrating operations according to a first example of the disclosure of the present specification.
  • FIG. 9 the operations shown in FIG. 9 are only examples, and the scope of the disclosure of the present specification for operations performed by the IMS layer, the NAS layer, the RRC layer, and the PDCP layer is not limited by the example of FIG. 9.
  • Step S807 of FIG. 9 may be performed in the same manner as step S807 of FIG. 8.
  • the IMS layer may store information that "SIP signaling for non-service attempt (or IMS signaling)" has failed.
  • the IMS layer may store information that IMS signaling (eg, "SIP signaling for non-service attempts (or IMS signaling)”) has failed in a flag form or in various forms.
  • a SIP signaling (or IMS signaling) request for service attempt may be generated. For example, there may be a case where a user who actually uses the terminal requests an IMS service (eg, voice call/video call/SMS).
  • IMS service eg, voice call/video call/SMS
  • the IMS layer may determine that IMS signaling for service attempt is required in order to request a first IMS service (eg, voice call/video call/SMS).
  • a first IMS service eg, voice call/video call/SMS.
  • the IMS layer since the IMS layer stores information that "SIP signaling for non-service attempt (or IMS signaling)" has failed, the IMS layer first, in order to perform IMS signaling for a service attempt, -It can be determined to transmit "SIP signaling (or IMS signaling)" for service attempt.
  • the IMS layer may transmit a second request message including information related to "SIP signaling for non-service attempt (or IMS signaling)" to the NAS layer.
  • the information related to "SIP signaling for non-service attempt (or IMS signaling)" may include one or more of a) and/or b) described above.
  • the second request message may include: a) information and/or indication related to the IMS service attempt that occurred and/or b) the SIP for non-service attempt accompanying the IMS service (or followed by the IMS service).
  • Signaling (or IMS signaling) may include one or more of information/indication indicating (or notifying) that “signaling (or IMS signaling)” and information on a corresponding IMS service.
  • a) and b) are the same as those described above.
  • the NAS layer may attempt access based on one or more information of a) and/or b). For example, the NAS layer may determine the access category of the second request message as the first access category based on one or more information of a) and/or b). For example, if one or more of a) and/or b) is information related to MMTEL voice, the NAS layer may attempt access using a first access category (eg, access category 4).
  • a first access category eg, access category 4
  • the NAS layer may transmit a second request message including information on the first access category to the RRC layer.
  • the RRC layer may be in a state in which access control is being applied due to a network congestion situation or the like. Since the RRC layer has received information on the first access category (eg, access category 4) from the NAS layer, it will perform an access control check on the second request message based on the first access category (eg, access category 4). I can.
  • the first access category eg, access category 4
  • the RRC layer Since the RRC layer has received information on the first access category (eg, access category 4) from the NAS layer, it will perform an access control check on the second request message based on the first access category (eg, access category 4). I can.
  • the RRC layer When access control is not applied for the first access category (e.g., access category 4) (e.g., when the priority of an access category blocked according to access control is lower than access category 4), the RRC layer receives from the NAS layer One request message can be accepted.
  • the RRC layer may transmit information (eg, "not barred” information) indicating that the request message is allowed to the NAS layer. If the request message is accepted, an operation related to case 1 may be performed.
  • the RRC layer When access control is applied to the first access category (e.g., access category 4) (e.g., when the priority of an access category blocked according to access control is higher than access category 4), the RRC layer receives from the NAS layer. You can block the request message. The RRC layer may transmit information (eg, "barred" information) that the request message has been blocked to the NAS layer. When the request message is blocked, an operation related to case 2 may be performed.
  • the first access category e.g., access category 4
  • the RRC layer receives from the NAS layer. You can block the request message.
  • the RRC layer may transmit information (eg, "barred" information) that the request message has been blocked to the NAS layer. When the request message is blocked, an operation related to case 2 may be performed.
  • the operation related to case 1 of FIG. 9 may be performed, and when the request message is blocked, case 2 of FIG. 9 An operation related to can be performed.
  • an operation related to case 1 may be performed.
  • the RRC layer may transmit to an upper layer (eg, the NAS layer) that the access request due to the second request message is approved.
  • the RRC layer may transmit a response message including information that the second request message has been accepted (eg, information that the access request due to the request message has been approved) to the NAS layer.
  • the NAS layer may prioritize related NAS operations if necessary. For example, when the terminal is in the IDLE state, the NAS layer may perform a first service request procedure for IMS signaling transmission for non-service attempts. When the access is finally granted, for example, transition to the CONNECTED state (e.g., CM-CONNECTED state) and successfully activate the PDU session related to IMS signaling for non-service attempts, in step S906a, the NAS layer May transmit a response message including information that the request message has been accepted to the IMS layer.
  • CONNECTED state e.g., CM-CONNECTED state
  • the IMS layer of the terminal may transmit a third request message including information related to IMS signaling for non-service attempts to the IMS network through the packet data convergence protocol (PDCP) layer of the terminal.
  • the IMS layer of the terminal may transmit a third request message including information related to IMS signaling for a non-service attempt to the PDCP layer based on the response message received in step S906a.
  • the PDCP layer can transmit the third request message to the IMS network through the RAN and UPF.
  • step S907a For reference, a specific example in which the third request message in step S907a is transmitted to the network will be described with reference to FIG. 11.
  • an operation related to case 2 may be performed.
  • the RRC layer may transmit a response message (including information that the second request message is blocked) to the NAS layer.
  • the NAS layer may transmit a response message (including information that the second request message is blocked) to the application layer.
  • the NAS layer of the terminal may inform the IMS layer of the terminal of the state transition (or state change). For example, the NAS layer of the terminal may provide information on state transition (or state change) to the IMS layer. For example, the NAS layer of the terminal may transmit information that the state of the terminal has transitioned (or changed) to the CONNECTED state to the IMS layer of the terminal.
  • the IMS layer may receive information on state transition (or state change) from the NAS layer.
  • state transition or state change
  • information indicating that "SIP signaling for non-service attempts (or IMS signaling)" has failed is stored at the time when the IMS layer recognizes the state transition (or state change) (for example, the "Signaling Transmission Failure” flag is When set to 1), the IMS layer of the terminal may attempt to retransmit the previously failed SIP signaling (or IMS signaling).
  • the IMS layer is transferred. Retransmission of SIP signaling (or IMS signaling) that has failed in may be attempted.
  • the IMS layer of the terminal may transmit a SIP signaling (or IMS signaling) message through the user plane of the activated IMS-related PDU session.
  • Degree 10 is It is an exemplary signal flow diagram illustrating a second example of the disclosure of the present specification.
  • FIG. 10 the operations illustrated in FIG. 10 are only examples, and the scope of the disclosure of the present specification for operations performed by the application layer, the NAS layer, the RRC layer, and the PDCP layer is not limited by the example of FIG. 10.
  • Step S807 of FIG. 10 may be performed in the same manner as step S807 of FIG. 8.
  • the IMS layer may store information that "SIP signaling for non-service attempt (or IMS signaling)" has failed.
  • the IMS layer may store information that IMS signaling (eg, "SIP signaling for non-service attempts (or IMS signaling)”) has failed in a flag form or in various forms.
  • the state of the terminal may transition from the IDLE state (e.g. CM-IDLE state) to the CONNECTED state (e.g. CM-CONNECTED) (may be changed. ).
  • the NAS layer of the terminal may recognize this state transition (or state change).
  • the NAS layer may transmit information indicating that the state of the terminal has changed (transitioned) to the CONNECTED state to the IMS layer.
  • the IMS layer may receive information on state transition (or state change) from the NAS layer.
  • state transition or state change
  • information indicating that "SIP signaling for non-service attempts (or IMS signaling)" has failed is stored at the time when the IMS layer recognizes the state transition (or state change) (for example, the "Signaling Transmission Failure” flag is When set to 1), the IMS layer of the terminal may attempt to retransmit the previously failed SIP signaling (or IMS signaling).
  • the IMS layer may transmit a second request message including information related to IMS signaling for a non-service attempt.
  • the information related to IMS signaling for a non-service attempt may be information related to "SIP signaling (or IMS signaling) for a non-service attempt" that has previously failed.
  • step S1002 is a case in which a user plane for a previously created (or established (esatablished)) IMS-related PUD session is re-activated in a procedure in which the state of the terminal is changed to a CONNECETED state. May be performed on.
  • the IMS layer may transmit a SIP signaling (or IMS signaling) message through the user plane of the activated IMS-related PDU session.
  • the NAS layer may attempt access based on information related to IMS signaling for non-service attempts. For example, the NAS layer may determine the access category of the second request message as the first access category (eg, access category 7) based on information related to IMS signaling for non-service attempts.
  • the access category of the second request message may be determined as the first access category (eg, access category 7) based on information related to IMS signaling for non-service attempts.
  • the NAS layer may transmit a second request message including information on the first access category (eg, access category 7) to the RRC layer.
  • the first access category eg, access category 7
  • the RRC layer may be in a state in which access control is being applied due to a network congestion situation or the like. Since the RRC layer has received information on the first access category (eg, access category 7) from the NAS layer, it will perform an access control check on the second request message based on the first access category (eg, access category 7). I can.
  • the first access category eg, access category 7
  • the RRC layer When access control is not applied to the first access category (e.g., access category 7) (e.g., when the priority of an access category blocked according to access control is lower than access category 7), the RRC layer receives from the NAS layer One request message can be accepted.
  • the RRC layer may transmit information (eg, "not barred” information) indicating that the request message is allowed to the NAS layer. If the request message is accepted, an operation related to case 1 may be performed.
  • the RRC layer When access control is applied to the first access category (e.g., access category 7) (e.g., when the priority of an access category blocked according to access control is higher than access category 7), the RRC layer receives from the NAS layer. You can block the request message. The RRC layer may transmit information (eg, "barred" information) that the request message has been blocked to the NAS layer. When the request message is blocked, an operation related to case 2 may be performed.
  • the first access category e.g., access category 7
  • the RRC layer receives from the NAS layer. You can block the request message.
  • the RRC layer may transmit information (eg, "barred" information) that the request message has been blocked to the NAS layer. When the request message is blocked, an operation related to case 2 may be performed.
  • the operation related to case 1 of FIG. 10 may be performed, and when the request message is blocked, case 2 of FIG. An operation related to can be performed.
  • an operation related to case 1 may be performed.
  • the RRC layer may transmit to an upper layer (eg, the NAS layer) that the access request due to the second request message is approved.
  • the RRC layer may transmit a response message including information that the second request message has been accepted (eg, information that the access request due to the request message has been approved) to the NAS layer.
  • the NAS layer may prioritize related NAS operations if necessary. For example, when the terminal is in the IDLE state, the NAS layer may perform a first service request procedure for IMS signaling transmission for non-service attempts. When the access is finally granted, for example, transition to the CONNECTED state (e.g., CM-CONNECTED state) to successfully activate the PDU session related to IMS signaling for non-service attempts, in step 1006a, the NAS layer May transmit a response message including information that the request message has been accepted to the IMS layer.
  • CONNECTED state e.g., CM-CONNECTED state
  • the IMS layer of the terminal may transmit a third request message including information related to IMS signaling for a non-service attempt to the IMS network through the packet data convergence protocol (PDCP) layer of the terminal.
  • the IMS layer of the terminal may transmit a third request message including information related to IMS signaling for a non-service attempt to the PDCP layer based on the response message received in step S1006a.
  • the PDCP layer can transmit the third request message to the IMS network through the RAN and UPF.
  • step S1007a For reference, a specific example in which the third request message of step S1007a is transmitted to the network will be described with reference to FIG. 11.
  • an operation related to case 2 may be performed.
  • the RRC layer may transmit a response message (including information that the request message has been blocked) to the NAS layer.
  • the NAS layer may transmit a response message (including information that the request message has been blocked) to the application layer.
  • FIG. 11 is an exemplary signal flow diagram illustrating operations according to case 1 of FIG. 9 or case 1 of FIG. 10.
  • step S907a of case 1 of FIG. 9 or the third request message of step S1007a of case 1 of FIG. 10 is transmitted to a network (eg, IMS network) Explain.
  • a network eg, IMS network
  • the IMS layer of the terminal sends a third request message including information related to IMS signaling for a non-service attempt through the packet data convergence protocol (PDCP) layer of the terminal.
  • PDCP packet data convergence protocol
  • CSCF Packet Control Function
  • the PDCP layer may transmit the third request message to the UPF node via the RAN, and the UPF node may transmit the third request message to the IMS network (eg, P-CSCF).
  • the IMS network eg P-CSCF
  • the terminal and the IMS network can perform procedures for initial registration, re-registration, or subscription refresh.
  • the IMS network may transmit a response message (eg, initial registration acceptance, re-registration acceptance, subscription refresh acceptance, etc.) to the third request message to the UPF node.
  • the UPF node may transmit the response message to the PDCP layer of the terminal through the RAN, and the PDCP layer may transmit the response message to the IMS layer.
  • the IMS layer of the terminal transmits a request message for re-registration, so that the terminal (eg, UE) in the IMS network can maintain the registered state in the registered IMS network as re-registration is successful. Since the terminal maintains the registered state in the IMS network, when an IMS service attempt such as voice call, video call, or SMS is required afterwards, the terminal can perform IMS signaling for an IMS service attempt.
  • access control when it is necessary to transmit IMS signaling for a non-service request in a situation in which access control is being applied due to a network congestion, etc., access control may be bypassed. This enables the user's terminal to continuously provide IMS services such as voice calls, video calls, and SMS that the user wants to use.
  • the operation of the UE described in this specification may be implemented by the devices of FIGS. 12 to 17 to be described below.
  • the UE may be the first wireless device 100 or the second wireless device 200 of FIG. 13.
  • the operation of the UE described herein may be processed by one or more processors 102 or 202.
  • the operation of the UE described herein may be stored in one or more memories 104 or 204 in the form of an instruction/program (e.g. instruction, executable code) executable by one or more processors 102 or 202.
  • One or more processors 102 or 202 control one or more memories 104 or 204 and one or more transceivers 106 or 206, and execute instructions/programs stored in one or more memories 104 or 204 to be used herein. It is possible to perform the operation of the UE described in the disclosure.
  • instructions for performing the operation of the UE described in the disclosure of the present specification may be stored in a recording nonvolatile computer-readable storage medium.
  • the storage medium may be included in one or more memories 104 or 204.
  • instructions recorded in the storage medium may be executed by one or more processors 102 or 202 to perform the operation of the UE described in the disclosure of the present specification.
  • a network node eg, P-CSCF, AMF, etc.
  • the network node may be the first wireless device 100 or the second wireless device 200 of FIG. 13.
  • the operations of the network nodes described herein may be processed by one or more processors 102 or 202.
  • the operations of the network nodes described herein may be stored in one or more memories 104 or 204 in the form of an instruction/program (e.g. instruction, executable code) executable by one or more processors 102 or 202.
  • One or more processors 102 or 202 control one or more memories 104 or 204 and one or more transceivers 106 or 206, and execute instructions/programs stored in one or more memories 104 or 204 to be used herein.
  • the operation of the network node described in the disclosure may be performed.
  • a 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 wireless access technology (eg, 5G NR (New RAT), LTE (Long Term Evolution)), and may be referred to as a communication/wireless/5G device.
  • wireless devices include robots 100a, vehicles 100b-1 and 100b-2, eXtended Reality (XR) devices 100c, hand-held devices 100d, and home appliances 100e. ), an Internet of Thing (IoT) device 100f, and an AI device/server 400.
  • the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, and a vehicle capable of performing inter-vehicle communication.
  • 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, including HMD (Head-Mounted Device), HUD (Head-Up Display), TV, smartphone, It can be implemented in the form of a computer, wearable device, home appliance, digital signage, vehicle, robot, and the like.
  • Portable devices may include smart phones, smart pads, wearable devices (eg, smart watches, smart glasses), computers (eg, notebook computers, etc.).
  • Home appliances may include TVs, refrigerators, and washing machines.
  • IoT devices may include sensors, smart meters, and the like.
  • the base station and the network may be implemented as a wireless device, and the specific wireless device 200a may operate as a base station/network node to another wireless device.
  • the wireless devices 100a to 100f may be connected to the network 300 through the base station 200.
  • AI Artificial Intelligence
  • the network 300 may be configured using a 3G network, a 4G (eg, LTE) network, or a 5G (eg, NR) network.
  • the wireless devices 100a to 100f may communicate with each other through the base station 200 / network 300, but may perform direct communication (e.g. sidelink communication) without going through the base station / network.
  • the vehicles 100b-1 and 100b-2 may perform direct communication (e.g.
  • V2V Vehicle to Vehicle
  • V2X Vehicle to Everything
  • the IoT device eg, sensor
  • the IoT device may directly communicate with other IoT devices (eg, sensors) or other wireless devices 100a to 100f.
  • Wireless communication/connections 150a, 150b, and 150c may be established between the wireless devices 100a to 100f / base station 200 and the base station 200 / base station 200.
  • the wireless communication/connection includes various wireless access such as uplink/downlink communication 150a, sidelink communication 150b (or D2D communication), base station communication 150c (eg relay, Integrated Access Backhaul). This can be achieved through technology (eg 5G NR)
  • the wireless communication/connection 150a, 150b, 150c may transmit/receive signals through various physical channels.
  • transmission/reception of radio signals At least some of a process of setting various configuration information for, a process of processing various signals (eg, channel encoding/decoding, modulation/demodulation, resource mapping/demapping, etc.), a resource allocation process, and the like may be performed.
  • FIG. 13 illustrates a wireless device applicable to the disclosure of the present specification.
  • the first wireless device 100 and the second wireless device 200 may transmit and receive wireless signals through various wireless access technologies (eg, LTE and NR).
  • ⁇ the first wireless device 100, the second wireless device 200 ⁇ is the ⁇ wireless device 100x, the base station 200 ⁇ and/or ⁇ wireless device 100x, wireless device 100x) of FIG. 12 ⁇ Can be matched.
  • it may correspond to the first wireless device 100 and the UE, AMF, SMF, or UPF described in the disclosure of the present specification.
  • the second wireless device 200 may correspond to a UE, AMF, SMF, or UPF that communicates with the first wireless device 100.
  • the first wireless device 100 includes one or more processors 102 and one or more memories.
  • the processor 102 controls the memory 104 and/or the transceiver 106 and may be configured to implement the descriptions, functions, procedures, suggestions, methods, and/or operational flowcharts disclosed herein.
  • the processor 102 may process information in the memory 104 to generate first information/signal, and then transmit a radio signal including the first information/signal through the transceiver 106.
  • the processor 102 may store information obtained from signal processing of the second information/signal in the memory 104 after receiving a radio signal including the second information/signal through the transceiver 106.
  • the memory 104 may be connected to the processor 102 and may store various information related to the operation of the processor 102.
  • the memory 104 may perform some or all of the processes controlled by the processor 102, or instructions for performing the descriptions, functions, procedures, suggestions, methods, and/or operational flow charts disclosed in this document. It can store software code including
  • the processor 102 and the memory 104 may be part of a communication modem/circuit/chip designed to implement wireless communication technology (eg, LTE, NR).
  • the transceiver 106 may be coupled with the processor 102 and may transmit and/or receive radio signals through one or more antennas 108.
  • the transceiver 106 may include a transmitter and/or a receiver.
  • the transceiver 106 may be mixed with an RF (Radio Frequency) unit.
  • a wireless device may mean a communication modem/circuit/chip.
  • the second wireless device 200 includes one or more processors 202 and one or more memories 204, and may further include one or more transceivers 206 and/or one or more antennas 208.
  • the processor 202 controls the memory 204 and/or the transceiver 206 and may be configured to implement the descriptions, functions, procedures, suggestions, methods, and/or operational flowcharts disclosed herein.
  • the processor 202 may process information in the memory 204 to generate third information/signal, and then transmit a wireless signal including the third information/signal through the transceiver 206.
  • the processor 202 may store information obtained from signal processing of the fourth information/signal in the memory 204 after receiving a radio signal including the fourth information/signal through the transceiver 206.
  • the memory 204 may be connected to the processor 202 and may store various information related to the operation of the processor 202.
  • the memory 204 may perform some or all of the processes controlled by the processor 202, or instructions for performing the descriptions, functions, procedures, suggestions, methods and/or operational flow charts disclosed in this document. It can store software code including
  • the processor 202 and the memory 204 may be part of a communication modem/circuit/chip designed to implement wireless communication technology (eg, LTE, NR).
  • the transceiver 206 may be connected to the processor 202 and may transmit and/or receive radio signals through one or more antennas 208.
  • the transceiver 206 may include a transmitter and/or a receiver.
  • the transceiver 206 may be used interchangeably with an RF unit.
  • a wireless device may mean a communication modem/circuit/chip.
  • one or more protocol layers may be implemented by one or more processors 102, 202.
  • one or more processors 102, 202 may implement one or more layers (eg, functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP).
  • One or more processors 102, 202 may be configured to generate one or more Protocol Data Units (PDUs) and/or one or more Service Data Units (SDUs) according to the description, functions, procedures, proposals, methods, and/or operational flow charts disclosed in this document. Can be generated.
  • PDUs Protocol Data Units
  • SDUs Service Data Units
  • One or more processors 102, 202 may generate messages, control information, data, or information according to the description, function, procedure, suggestion, method, and/or operational flow chart disclosed herein.
  • At least one processor (102, 202) generates a signal (e.g., a baseband signal) including PDU, SDU, message, control information, data or information according to the functions, procedures, proposals and/or methods disclosed herein. , It may be provided to one or more transceivers (106, 206).
  • One or more processors 102, 202 may receive signals (e.g., baseband signals) from one or more transceivers 106, 206, and the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed herein PDUs, SDUs, messages, control information, data, or information may be obtained according to the parameters.
  • signals e.g., baseband signals
  • One or more of the processors 102 and 202 may be referred to as a controller, microcontroller, microprocessor, or microcomputer.
  • One or more of the processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof.
  • ASICs Application Specific Integrated Circuits
  • DSPs Digital Signal Processors
  • DSPDs Digital Signal Processing Devices
  • PLDs Programmable Logic Devices
  • FPGAs Field Programmable Gate Arrays
  • the description, functions, procedures, suggestions, methods, and/or operational flow charts disclosed in this document may be implemented using firmware or software, and firmware or software may be implemented to include modules, procedures, functions, and the like.
  • the description, functions, procedures, proposals, methods and/or operational flow charts disclosed in this document are included in one or more processors 102, 202, or stored in one or more memories 104, 204, and are It may be driven by the above processors 102 and 202.
  • the descriptions, functions, procedures, proposals, methods and/or operational flowcharts disclosed in this document may be implemented using firmware or software in the form of codes, instructions and/or a set of instructions.
  • One or more memories 104 and 204 may be connected to one or more processors 102 and 202 and may store various types of data, signals, messages, information, programs, codes, instructions and/or instructions.
  • One or more memories 104 and 204 may be composed of ROM, RAM, EPROM, flash memory, hard drive, register, cache memory, computer readable storage medium, and/or combinations thereof.
  • One or more memories 104 and 204 may be located inside and/or outside of one or more processors 102 and 202.
  • one or more memories 104, 204 may be connected to one or more processors 102, 202 through various technologies such as wired or wireless connection.
  • the one or more transceivers 106 and 206 may transmit user data, control information, radio signals/channels, and the like mentioned in the methods and/or operation flow charts of this document to one or more other devices.
  • One or more transceivers (106, 206) may receive user data, control information, radio signals/channels, etc. mentioned in the description, functions, procedures, suggestions, methods and/or operation flow charts disclosed in this document from one or more other devices.
  • one or more transceivers 106 and 206 may be connected to one or more processors 102 and 202, and may transmit and receive wireless signals.
  • one or more processors 102, 202 may control one or more transceivers 106, 206 to transmit user data, control information, or radio signals to one or more other devices.
  • one or more processors 102, 202 may control one or more transceivers 106, 206 to receive user data, control information, or radio signals from one or more other devices.
  • one or more transceivers (106, 206) may be connected with one or more antennas (108, 208), and one or more transceivers (106, 206) through one or more antennas (108, 208), the description and functionality disclosed in this document. It may be set to transmit and receive user data, control information, radio signals/channels, and the like mentioned in a procedure, a proposal, a method and/or an operation flowchart.
  • one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (eg, antenna ports).
  • One or more transceivers (106, 206) in order to process the received user data, control information, radio signal / channel, etc. using one or more processors (102, 202), the received radio signal / channel, etc. in the RF band signal. It can be converted into a baseband signal.
  • One or more transceivers 106 and 206 may convert user data, control information, radio signals/channels, etc. processed using one or more processors 102 and 202 from a baseband signal to an RF band signal.
  • one or more of the transceivers 106 and 206 may include (analog) oscillators and/or filters.
  • FIG. 14 illustrates a signal processing circuit for a transmission signal.
  • the signal processing circuit 1000 may include a scrambler 1010, a modulator 1020, a layer mapper 1030, a precoder 1040, a resource mapper 1050, and a signal generator 1060.
  • the operations/functions of FIG. 14 may be performed in the processors 102 and 202 and/or the transceivers 106 and 206 of FIG. 13.
  • the hardware elements of FIG. 14 may be implemented in the processors 102 and 202 and/or the transceivers 106 and 206 of FIG. 13.
  • blocks 1010 to 1060 may be implemented in the processors 102 and 202 of FIG. 13.
  • blocks 1010 to 1050 may be implemented in the processors 102 and 202 of FIG. 13
  • block 1060 may be implemented in the transceivers 106 and 206 of FIG. 13.
  • the codeword may be converted into a wireless signal through the signal processing circuit 1000 of FIG. 14.
  • the codeword is an encoded bit sequence of an information block.
  • the information block may include a transport block (eg, a UL-SCH transport block, a DL-SCH transport block).
  • the radio signal may be transmitted through various physical channels (eg, PUSCH, PDSCH).
  • the codeword may be converted into a scrambled bit sequence by the scrambler 1010.
  • the scramble sequence used for scramble is generated based on an initialization value, and the initialization value may include ID information of a wireless device.
  • the scrambled bit sequence may be modulated by the modulator 1020 into a modulation symbol sequence.
  • the modulation scheme may include pi/2-Binary Phase Shift Keying (pi/2-BPSK), m-Phase Shift Keying (m-PSK), m-Quadrature Amplitude Modulation (m-QAM), and the like.
  • the complex modulation symbol sequence may be mapped to one or more transport layers by the layer mapper 1030.
  • the modulation symbols of each transport layer may be mapped to the corresponding antenna port(s) by the precoder 1040 (precoding).
  • the output z of the precoder 1040 can be obtained by multiplying the output y of the layer mapper 1030 by the N*M precoding matrix W.
  • N is the number of antenna ports
  • M is the number of transmission layers.
  • the precoder 1040 may perform precoding after performing transform precoding (eg, DFT transform) on complex modulation symbols. Also, the precoder 1040 may perform precoding without performing transform precoding.
  • the resource mapper 1050 may map modulation symbols of each antenna port to a time-frequency resource.
  • the time-frequency resource may include a plurality of symbols (eg, CP-OFDMA symbols, DFT-s-OFDMA symbols) in the time domain, and may include a plurality of subcarriers in the frequency domain.
  • CP Cyclic Prefix
  • DAC Digital-to-Analog Converter
  • the signal processing process for the received signal in the wireless device may be configured as the reverse of the signal processing process 1010 to 1060 of FIG. 14.
  • a wireless device eg, 100 and 200 in FIG. 13
  • the received radio signal may be converted into a baseband signal through a signal restorer.
  • the signal restorer may include a frequency downlink converter, an analog-to-digital converter (ADC), a CP canceller, and a Fast Fourier Transform (FFT) module.
  • ADC analog-to-digital converter
  • FFT Fast Fourier Transform
  • the baseband signal may be reconstructed into a codeword through a resource de-mapper process, a postcoding process, a demodulation process, and a de-scramble process.
  • a signal processing circuit for a received signal may include a signal restorer, a resource demapper, a postcoder, a demodulator, a descrambler, and a decoder.
  • 15 shows another example of a wireless device applied to the disclosure of the present specification.
  • the wireless device may be implemented in various forms according to use-examples/services (see FIG. 12).
  • the wireless devices 100 and 200 correspond to the wireless devices 100 and 200 of FIG. 13, and various elements, components, units/units, and/or modules ) Can be composed of.
  • the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130, and an additional element 140.
  • the communication unit may include a communication circuit 112 and a transceiver(s) 114.
  • the communication circuit 112 may include one or more processors 102 and 202 and/or one or more memories 104 and 204 of FIG. 13.
  • transceiver(s) 114 may include one or more transceivers 106,206 and/or one or more antennas 108,208 of FIG. 13.
  • the control unit 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional element 140 and controls all operations of the wireless device.
  • the controller 120 may control the electrical/mechanical operation of the wireless device based on the program/code/command/information stored in the memory unit 130.
  • the control unit 120 transmits the information stored in the memory unit 130 to an external (eg, other communication device) through the communication unit 110 through a wireless/wired interface, or through the communication unit 110 to the outside (eg, Information received through a wireless/wired interface from another communication device) may be stored in the memory unit 130.
  • the additional element 140 may be variously configured according to the type of wireless device.
  • the additional element 140 may include at least one of a power unit/battery, an I/O unit, a driving unit, and a computing unit.
  • wireless devices include robots (Figs. 12, 100a), vehicles (Figs. 12, 100b-1, 100b-2), XR devices (Figs. 12, 100c), portable devices (Figs. (Figs.12, 100e), IoT devices (Figs. 12, 100f), digital broadcasting terminals, hologram devices, public safety devices, MTC devices, medical devices, fintech devices (or financial devices), security devices, climate/environment devices, It may be implemented in the form of an AI server/device (FIGS. 12 and 400), a base station (FIGS. 12 and 200), and a network node.
  • the wireless device can be used in a mobile or fixed location depending on the use-example/service.
  • various elements, components, units/units, and/or modules within the wireless devices 100 and 200 may be connected to each other through a wired interface, or at least part of them may be wirelessly connected through the communication unit 110.
  • the control unit 120 and the communication unit 110 are connected by wire, and the control unit 120 and the first unit (eg, 130, 140) are connected through the communication unit 110.
  • the control unit 120 and the first unit eg, 130, 140
  • each element, component, unit/unit, and/or module in the wireless device 100 and 200 may further include one or more elements.
  • the controller 120 may be configured with one or more processor sets.
  • control unit 120 may be composed of a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphic processing processor, and a memory control processor.
  • memory unit 130 includes random access memory (RAM), dynamic RAM (DRAM), read only memory (ROM), flash memory, volatile memory, and non-volatile memory. volatile memory) and/or a combination thereof.
  • Degree 16 is It shows an example of a vehicle or an autonomous vehicle applied to the disclosure of the present specification.
  • the vehicle or autonomous vehicle may be implemented as a mobile robot, a vehicle, a train, an aerial vehicle (AV), or a ship.
  • AV aerial vehicle
  • the vehicle or autonomous vehicle 100 includes an antenna unit 108, a communication unit 110, a control unit 120, a driving unit 140a, a power supply unit 140b, a sensor unit 140c, and autonomous driving. It may include a unit (140d).
  • the antenna unit 108 may be configured as a part of the communication unit 110.
  • Blocks 110/130/140a to 140d correspond to blocks 110/130/140 of FIG. 15, respectively.
  • the communication unit 110 may transmit and receive signals (eg, data, control signals, etc.) with external devices such as other vehicles, base stations (e.g. base stations, roadside base stations, etc.), and servers.
  • the controller 120 may perform various operations by controlling elements of the vehicle or the autonomous vehicle 100.
  • the control unit 120 may include an Electronic Control Unit (ECU).
  • the driving unit 140a may cause the vehicle or the autonomous vehicle 100 to travel on the ground.
  • the driving unit 140a may include an engine, a motor, a power train, a wheel, a brake, a steering device, and the like.
  • the power supply unit 140b supplies power to the vehicle or the autonomous vehicle 100, and may include a wired/wireless charging circuit, a battery, and the like.
  • the sensor unit 140c may obtain vehicle status, surrounding environment information, user information, and the like.
  • the sensor unit 140c is an IMU (inertial measurement unit) sensor, a collision sensor, a wheel sensor, a speed sensor, an inclination sensor, a weight detection sensor, a heading sensor, a position module, and a vehicle advancement. /Reverse sensor, battery sensor, fuel sensor, tire sensor, steering sensor, temperature sensor, humidity sensor, ultrasonic sensor, illumination sensor, pedal position sensor, etc. may be included.
  • the autonomous driving unit 140d is a technology for maintaining a driving lane, a technology for automatically adjusting the speed such as adaptive cruise control, a technology for automatically driving along a predetermined route, and for driving by automatically setting a route when a destination is set. Technology, etc. can be implemented.
  • the communication unit 110 may receive map data and traffic information data from an external server.
  • the autonomous driving unit 140d may generate an autonomous driving route and a driving plan based on the acquired data.
  • the controller 120 may control the driving unit 140a so that the vehicle or the autonomous driving vehicle 100 moves along the autonomous driving path according to the driving plan (eg, speed/direction adjustment).
  • the communication unit 110 asynchronously/periodically acquires the latest traffic information data from an external server, and may acquire surrounding traffic information data from surrounding vehicles.
  • the sensor unit 140c may acquire vehicle state and surrounding environment information.
  • the autonomous driving unit 140d may update the autonomous driving route and the driving plan based on the newly acquired data/information.
  • the communication unit 110 may transmit information about a vehicle location, an autonomous driving route, and a driving plan to an external server.
  • the external server may predict traffic information data in advance using AI technology or the like based on information collected from the vehicle or autonomously driving vehicles, and may provide the predicted traffic information data to the vehicle or autonomously driving vehicles.
  • FIG 17 illustrates an AI device applied to the disclosure of the present specification.
  • AI devices are fixed devices such as TVs, projectors, smartphones, PCs, notebooks, digital broadcasting terminals, tablet PCs, wearable devices, set-top boxes (STBs), radios, washing machines, refrigerators, digital signage, robots, vehicles, etc. It can be implemented with possible devices.
  • the AI device 100 includes a communication unit 110, a control unit 120, a memory unit 130, an input/output unit 140a/140b, a running processor unit 140c, and a sensor unit 140d. It may include. Blocks 110 to 130/140a to 140d correspond to blocks 110 to 130/140 of FIG. 15, respectively.
  • the communication unit 110 uses wired/wireless communication technology to provide external devices such as other AI devices (eg, FIGS. 12, 100x, 200, 400) or AI servers (eg, 400 in FIG. 12) and wired/wireless signals (eg, sensor information). , User input, learning model, control signals, etc.). To this end, the communication unit 110 may transmit information in the memory unit 130 to an external device or may transmit a signal received from the external device to the memory unit 130.
  • AI devices eg, FIGS. 12, 100x, 200, 400
  • AI servers eg, 400 in FIG. 12
  • wired/wireless signals eg, sensor information
  • the communication unit 110 may transmit information in the memory unit 130 to an external device or may transmit a signal received from the external device to the memory unit 130.
  • the controller 120 may determine at least one executable operation of the AI device 100 based on information determined or generated using a data analysis algorithm or a machine learning algorithm. In addition, the controller 120 may perform a determined operation by controlling the components of the AI device 100. For example, the control unit 120 may request, search, receive, or utilize data from the learning processor unit 140c or the memory unit 130, and may be a predicted or desirable operation among at least one executable operation. Components of the AI device 100 can be controlled to execute the operation. In addition, the control unit 120 collects history information including the operation content or user's feedback on the operation of the AI device 100 and stores it in the memory unit 130 or the running processor unit 140c, or the AI server ( 12 and 400). The collected history information can be used to update the learning model.
  • the memory unit 130 may store data supporting various functions of the AI device 100.
  • the memory unit 130 may store data obtained from the input unit 140a, data obtained from the communication unit 110, output data from the running processor unit 140c, and data obtained from the sensing unit 140.
  • the memory unit 130 may store control information and/or software codes necessary for the operation/execution of the controller 120.
  • the input unit 140a may acquire various types of data from the outside of the AI device 100.
  • the input unit 140a may acquire training data for model training and input data to which the training model is to be applied.
  • the input unit 140a may include a camera, a microphone, and/or a user input unit.
  • the output unit 140b may generate output related to visual, auditory or tactile sense.
  • the output unit 140b may include a display unit, a speaker, and/or a haptic module.
  • the sensing unit 140 may obtain at least one of internal information of the AI device 100, surrounding environment information of the AI device 100, and user information by using various sensors.
  • the sensing unit 140 may include a proximity sensor, an illuminance sensor, an acceleration sensor, a magnetic sensor, a gyro sensor, an inertial sensor, an RGB sensor, an IR sensor, a fingerprint recognition sensor, an ultrasonic sensor, an optical sensor, a microphone, and/or a radar. have.
  • the learning processor unit 140c may train a model composed of an artificial neural network using the training data.
  • the running processor unit 140c may perform AI processing together with the running processor unit of the AI server (FIGS. 12 and 400 ).
  • the learning processor unit 140c may process information received from an external device through the communication unit 110 and/or information stored in the memory unit 130.
  • the output value of the learning processor unit 140c may be transmitted to an external device through the communication unit 110 and/or may be stored in the memory unit 130.
  • the claims set forth herein may be combined in a variety of ways.
  • the technical features of the method claims of the present specification may be combined to be implemented as a device, and the technical features of the device claims of the present specification may be combined to be implemented by a method.
  • the technical characteristics of the method claim of the present specification and the technical characteristics of the device claim may be combined to be implemented as a device, and the technical characteristics of the method claim of the present specification and the technical characteristics of the device claim may be combined to be implemented by a method.

Landscapes

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

Abstract

Un mode de réalisation de la présente invention concerne un procédé au moyen duquel un terminal effectue une communication relative à un IMS. Le procédé peut comprendre les étapes dans lesquelles : une couche IMS transmet, à une couche NAS du terminal, un premier message de requête comprenant des informations relatives à une signalisation IMS pour une tentative de non-service ; la couche IMS du terminal reçoit, de la couche NAS du terminal, un message de réponse indiquant que le premier message de requête a été bloqué ; et des informations indiquant que la transmission des informations relatives à la signalisation IMS pour la tentative de non-service a échoué, sont stockées.
PCT/KR2020/010269 2019-08-07 2020-08-04 Signalisation ims WO2021025432A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR10-2019-0096052 2019-08-07
KR20190096052 2019-08-07

Publications (1)

Publication Number Publication Date
WO2021025432A1 true WO2021025432A1 (fr) 2021-02-11

Family

ID=74503474

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2020/010269 WO2021025432A1 (fr) 2019-08-07 2020-08-04 Signalisation ims

Country Status (1)

Country Link
WO (1) WO2021025432A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114157535A (zh) * 2021-10-15 2022-03-08 北京国电通网络技术有限公司 双责任链微服务网关系统及其处理方法
WO2023177085A1 (fr) * 2022-03-14 2023-09-21 Samsung Electronics Co., Ltd. Procédé et dispositif de récupération de service d'appel dans un système de communication mobile

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160127422A1 (en) * 2014-10-31 2016-05-05 Intel Corporation Apparatus, system and method of differentiating between an ims connection and a non-ims connection
KR101698285B1 (ko) * 2012-11-27 2017-01-19 엘지전자 주식회사 Ims 기반 서비스 연결 방법
US20170086064A1 (en) * 2015-09-23 2017-03-23 Htc Corporation Device and Method of Handling Non Access Stratum Procedure
WO2018005419A1 (fr) * 2016-06-30 2018-01-04 Intel IP Corporation Mécanisme de radiorecherche optimisé destiné à un sous-système multimédia ip (ims)
WO2018128456A1 (fr) * 2017-01-06 2018-07-12 엘지전자 주식회사 Procédé et terminal pour effectuer une commande d'accès dans un système de communication mobile de 5ème génération

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101698285B1 (ko) * 2012-11-27 2017-01-19 엘지전자 주식회사 Ims 기반 서비스 연결 방법
US20160127422A1 (en) * 2014-10-31 2016-05-05 Intel Corporation Apparatus, system and method of differentiating between an ims connection and a non-ims connection
US20170086064A1 (en) * 2015-09-23 2017-03-23 Htc Corporation Device and Method of Handling Non Access Stratum Procedure
WO2018005419A1 (fr) * 2016-06-30 2018-01-04 Intel IP Corporation Mécanisme de radiorecherche optimisé destiné à un sous-système multimédia ip (ims)
WO2018128456A1 (fr) * 2017-01-06 2018-07-12 엘지전자 주식회사 Procédé et terminal pour effectuer une commande d'accès dans un système de communication mobile de 5ème génération

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114157535A (zh) * 2021-10-15 2022-03-08 北京国电通网络技术有限公司 双责任链微服务网关系统及其处理方法
CN114157535B (zh) * 2021-10-15 2024-03-12 北京国电通网络技术有限公司 双责任链微服务网关系统及其处理方法
WO2023177085A1 (fr) * 2022-03-14 2023-09-21 Samsung Electronics Co., Ltd. Procédé et dispositif de récupération de service d'appel dans un système de communication mobile

Similar Documents

Publication Publication Date Title
WO2021029512A1 (fr) Communication liée à une modification de serveur d'application
WO2020184956A1 (fr) Gestion de session d'unité de données de protocole d'accès multiple
WO2021034093A1 (fr) Authentification pour relais
WO2021015598A1 (fr) Communication basée sur une pluralité de sim
WO2021241905A1 (fr) Sélection efficace de plmn lors d'une défaillance d'authentification pour chaque tranche de réseau dans un réseau d'itinérance
WO2019190166A1 (fr) Procédé, équipement utilisateur et nœud de réseau pour mise en œuvre d'une procédure d'établissement de session de pdu pour ladn
WO2021025428A1 (fr) Vérification d'informations d'appelant basée sur une pluralité de sim
WO2018169244A1 (fr) Procédé de notification d'événement de mobilité dans un système de communication sans fil et dispositif correspondant
WO2020251293A1 (fr) Signalisation ims
WO2017095204A1 (fr) Procédé permettant de fournir un service de communication et passerelle de réseau de données par paquets
WO2021049841A1 (fr) Procédé permettant de déplacer une session vocale ims sur un accès non 3gpp vers un accès 3gpp
WO2021096193A1 (fr) Communication à relais
WO2020036466A1 (fr) Procédé, dispositif de communication, et nœud de réseau pour transmettre ou recevoir un message de radiomessagerie
WO2021162393A1 (fr) Communication liée à des sessions de pdu multi-accès
WO2021025308A1 (fr) Procédé de traitement d'amf pour prendre en charge de multiples usim
WO2021162500A1 (fr) Communication liée à une session pdu multi-accès
WO2020060007A1 (fr) Procédé et dispositif sans fil pour gérer une session de pdu dans une communication mobile 5g
WO2021066346A1 (fr) Procédé permettant de déplacer une session de pdu sur un accès non 3gpp vers un accès 3gpp
WO2021167304A1 (fr) Communication relative à un état de désactivation du service de données ps
WO2022215909A1 (fr) Procédé de gestion de sessions pdu
WO2022014981A1 (fr) Procédé pour permettre une continuité de service lorsqu'une situation de catastrophe est terminée, et dispositif prenant en charge celui-ci
WO2021040463A1 (fr) Communication relative à un état de désactivation du service de données ps 3gpp
WO2022035257A1 (fr) Traitement d'une défaillance de nssaa provoquée par une erreur de réseau ou une expiration de délai
WO2020251226A1 (fr) Procédé d'accès à un npn dans un système de communication mobile 5g et équipement utilisateur
WO2021025432A1 (fr) Signalisation ims

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

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

Country of ref document: EP

Kind code of ref document: A1