+

WO2018151546A1 - Procédé et dispositif d'amélioration de sécurité dans un système de communication sans fil - Google Patents

Procédé et dispositif d'amélioration de sécurité dans un système de communication sans fil Download PDF

Info

Publication number
WO2018151546A1
WO2018151546A1 PCT/KR2018/001963 KR2018001963W WO2018151546A1 WO 2018151546 A1 WO2018151546 A1 WO 2018151546A1 KR 2018001963 W KR2018001963 W KR 2018001963W WO 2018151546 A1 WO2018151546 A1 WO 2018151546A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
terminal
pdcp entity
security key
pdcp
Prior art date
Application number
PCT/KR2018/001963
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 WO2018151546A1 publication Critical patent/WO2018151546A1/fr

Links

Images

Classifications

    • 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
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]

Definitions

  • the present invention relates to a method of operating a base station and a terminal for managing the RRC connection state for low power low latency.
  • a 5G communication system or a pre-5G communication system is called a system after a 4G network (Beyond 4G Network) or a system after an LTE system (Post LTE).
  • 5G communication systems are being considered for implementation in the ultra-high frequency (mmWave) band (eg, such as the 60 Gigabit (60 GHz) band).
  • FD-MIMO massive array multiple input / output
  • FD-MIMO massive array multiple input / output
  • FD-MIMO massive array multiple input / output
  • FD-MIMO massive array multiple input / output
  • FD-MIMO massive array multiple input / output
  • Array antenna, analog beam-forming, and large scale antenna techniques are discussed.
  • 5G communication systems have advanced small cells, advanced small cells, cloud radio access network (cloud RAN), ultra-dense network (ultra-dense network) , Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, Coordinated Multi-Points (CoMP), and interference cancellation
  • cloud RAN cloud radio access network
  • D2D Device to Device communication
  • D2D Device to Device communication
  • CoMP Coordinated Multi-Points
  • Hybrid FSK and QAM Modulation FQAM and QAM Modulation
  • SWSC Slide Window Superposition Coding
  • ACM Advanced Coding Modulation
  • FBMC Fan Bank Multi Carrier
  • NOMA NOMA
  • SAP non-orthogonal multiple access
  • SCMA sparse code multiple access
  • IoT Internet of Things
  • IoE Internet of Everything
  • M2M machine to machine
  • MTC Machine Type Communication
  • IT intelligent Internet technology services can be provided that collect and analyze data generated from connected objects to create new value in human life.
  • IoT is a field of smart home, smart building, smart city, smart car or connected car, smart grid, health care, smart home appliances, advanced medical services, etc. through convergence and complex of existing information technology (IT) technology and various industries. It can be applied to.
  • the design of the RRC state for the wireless communication terminal to transmit and receive data was overly conservative due to the design philosophy of the previous generation focused on voice calls. For example, even after no traffic arrives for a certain period of time after receiving traffic, power consumption is severely maintained due to the RRC connected state (Connected discontinuous reception, Connected DRX, C-DRX). In addition, in case of a smart phone user, keep alive messages are frequently generated as data, irrespective of the user's quality of service (QoS). When the RRC connection is designed based on the voice call service, the terminal power consumption may be worsened. .
  • An embodiment of the present invention provides a method for setting a security key for data transmission when a base station in which a terminal is located is changed in consideration of mobility of the terminal in a situation in which data transmission is performed without an RRC state transition in an RRC INACTIVE state. .
  • an embodiment of the present invention provides a method for determining and applying a security key according to whether a packet data convergence protocol (PDCP) entity is changed.
  • PDCP packet data convergence protocol
  • An embodiment of the present invention for solving the above problems is a radio resource including a packet data convergence protocol (PDCP) entity related information and a deactivation counter information from a first base station in a method of operating a terminal in a wireless communication system; control) receiving a connection stop message, storing the first security key and the deactivation counter information currently being used by the terminal, moving the terminal to a second base station, and checking uplink data to be transmitted by the terminal. And generating a second security key based on the PDCP entity related information and the deactivation counter information and transmitting the uplink data encrypted with the second security key to the second base station.
  • PDCP packet data convergence protocol
  • a radio resource control (RRC) connection stop including a packet data convergence protocol (PDCP) entity-related information and a deactivation counter information from a transceiver for transmitting and receiving a signal and a first base station Receive a message, and stores the first security key and the deactivation counter information currently being used by the terminal, the terminal moves to the second base station, confirms the uplink data to be transmitted by the terminal, the PDCP entity related information and And a control unit generating a second security key based on the deactivation counter information and controlling to transmit the uplink data encrypted with the second security key to the second base station.
  • RRC radio resource control
  • the communication system of the terminal and the base station transitions to the RRC Connected_Active (RRC_CONNECTED) state when transmitting data directly in an Inactive (RRC_INACTIVE) state while selecting an RRC state for data transmission and performing a procedure therefor. Since the transition is not performed, the standby time (C-DRX, Radio tail) in the Active (RRC_CONNECTED) state is kept to a minimum, so the power consumption saving effect of the terminal is expected.
  • RRC_INACTIVE Inactive
  • RRC_CONNECTED Connected_Active
  • FIG. 1 is a diagram schematically illustrating a structure of a (5G, NR) communication system according to an embodiment of the present invention.
  • FIG. 2 is a diagram illustrating an example of operations of three RRC states, Connected_Active (RRC_CONNECTED), Connected_Inactive, and Idle, which are to be applied in a (5G, NR) communication system according to an exemplary embodiment of the present invention.
  • FIG. 3 is a diagram illustrating an exemplary state of a terminal, a base station, and a core-network (MME) in an inactive (RRC_INACTIVE) state in a communication system according to an embodiment of the present invention.
  • MME core-network
  • FIG. 4 is a diagram illustrating an example of a UE operating in an RRC Inactive state according to an embodiment of the present invention a) within a cell, b) within the same PDCP, within an entity, and c) another PDCP entity.
  • FIG. 5 is a diagram illustrating a generation and application of a security key for a data transmission operation in an Inactive (RRC_INACTIVE) state of a terminal in a communication system according to an embodiment of the present invention.
  • FIG. 6 illustrates an RRC field for transmitting an Enable PDCP_entity info and an INACTIVE counter when transmitting an RRC Connection suspend in a communication system according to an embodiment of the present invention.
  • FIG. 7 illustrates a generation and application of a security key for a data transmission operation in an Inactive (RRC_INACTIVE) state of a terminal in a communication system according to an embodiment of the present invention.
  • FIG. 8 is a diagram illustrating an example of notation of corresponding information when the communication system transmits PDCP entity information in a communication system according to an embodiment of the present invention.
  • FIG. 9 is a diagram illustrating a generation and application of a security key for a data transmission operation in an Inactive (RRC_INACTIVE) state of a terminal in a communication system according to an embodiment of the present invention.
  • FIG. 10 illustrates generation and application of a security key for a data transmission operation in an Inactive (RRC_INACTIVE) state in a communication system according to an embodiment of the present invention.
  • FIG. 11 is a diagram illustrating a security key generation and application for a data transmission operation in an Inactive (RRC_INACTIVE) state of a terminal in a communication system according to an embodiment of the present invention.
  • FIG. 12 is a view showing the structure of another terminal according to an embodiment of the present invention.
  • FIG. 13 is a diagram showing the structure of another base station according to an embodiment of the present invention.
  • FIG. 14 is a diagram showing the structure of a core network node according to an embodiment of the present invention.
  • An embodiment of the present invention relates to an operation method of a base station and a terminal which are discussed in 3GPP RAN 5G.
  • the standard defines energy-efficient operation with the main goal of improving the power efficiency [bit / J] of the terminal and base station networks more than 1000 times within the next 10 years.
  • a control for reducing the active (RRC_CONNECTED) operation time of the UE has been started to solve the possibility of additional power consumption due to the beamforming transmission method required for mmW operation of the high frequency band.
  • the technique proposed in the embodiment of the present invention is a technique for controlling and maintaining an RRC connection based on three RRC states, Connected_Active (RRC_CONNECTED), Connected_Inactive, and Idle, which are to be applied in a mobile communication system (5G or NR).
  • RRC_CONNECTED Connected_Active
  • Connected_Inactive Connected_Inactive
  • Idle which are to be applied in a mobile communication system
  • the spectral efficiency improvement and the channel access method are improved for the RRC state (Inactive and (or) Active (RRC_CONNECTED)) determination method for data transmission and efficient transmission in the RRC inactive state when transmitting traffic of the UE. It covers how to support the feature.
  • the RRC state (Inactive and (or) Active (RRC_CONNECTED)) determination method for transmitting data and the spectral efficiency improvement and channel access method improvement for efficiently transmitting the traffic of the UE in the RRC Inactive state are improved. Deal with.
  • the embodiment of the present invention deals with the improvement of the security method according to the change of the PDCP entity.
  • FIG. 1 is a diagram schematically illustrating a structure of a 5G NR communication system according to an embodiment of the present invention.
  • a base station (gNB or base station, 110, 115, 120, and 125) is connected to a terminal (UE or terminal, 105) through a wireless channel, and performs a more complicated role than that of a conventional (UMTS) NodeB and an eNodeB base station of LTE. .
  • the S-GW 130 is a device for providing a data bearer, and generates or removes a data bearer under the control of the MME 140.
  • the MME 140 is a device that is responsible for various control functions as well as mobility management function for the terminal 105 is connected to a plurality of base stations.
  • FIG. 2 is a diagram illustrating three RRC states, Connected_Active (RRC_CONNECTED) 205, Connected_Inactive 210, and Idle 215, which are applied in a 5G NR communication system according to an exemplary embodiment of the present invention.
  • the connected Active (RRC_CONNECTED) state 205 may be referred to as an RRC connected mode, and is a wireless connection state in which a terminal can transmit and receive data.
  • the idle state 215 may be referred to as a standby mode or an RRC standby mode, and is a wireless access state in which the terminal monitors whether paging is transmitted to the terminal.
  • the two modes are in a wireless access state that is also applied to the LTE system, and the detailed technology is the same as that of the existing LTE system.
  • the Connected_inactive state 210 is newly defined and may be named as the RRC_INACTIVE state. In the RRC inactive state, the UE context is maintained in the base station and the terminal, RAN-based paging is supported.
  • the UE may transition to the connected mode or the standby mode by using a specific procedure.
  • the mode is changed from the inactive (RRC_INACTIVE) mode to the connected mode, and the mode is changed from the connected mode to the inactive (RRC_INACTIVE) mode using the connection inactivation procedure.
  • the connection activation / inactivation procedure is one or more RRC messages transmitted and received between the terminal and the base station, characterized in that composed of one or more steps. You can also switch from Inactive (RRC_INACTIVE) mode to Standby mode according to a specific procedure.
  • various methods such as specific message exchange or timer-based or event-based may be considered.
  • the transition between connected and standby mode follows existing LTE technology. That is, switching between the modes is performed through a connection establishment or release procedure.
  • the 3GPP NR operates three RRC states by adding an Inactive (RRC_INACTIVE) state to two existing RRC states, and the UE operates as one RRC state at a time.
  • RRC_INACTIVE Inactive
  • FIG. 3 is a diagram illustrating an example of states of a terminal, a base station, and an MME in an inactive state in an NR communication system according to an exemplary embodiment of the present invention.
  • Inactive is a new RRC state
  • the air interface of the terminal 305 and the base station 310 is not connected, but the core network of the base station 310 and the MME 315 maintains the connected state.
  • the terminal 305 releases the RRC Connected_Active (RRC_CONNECTED) state with the base station 310
  • the base station 310 and the MME 315 are in the ECM Connected state
  • the context of the terminal 305 is the base station 310 and the MME ( Assume that 315 is storing.
  • the Anchor eNB stores the UE context including the resume ID for UE confirmation.
  • the mobile station transmits a corresponding ID to check the identity of the mobile station.
  • the new base station retrieves the UE context based on the terminal ID and then performs an access procedure.
  • the transmission operation of cellular-internet of things (C-IoT) and narrow band-internet of things (NB-IoT) in the standard 3GPP Release 13 transmits (RRC resume) data after transitioning to the RRC connected state. There is no need to set up a separate data radio bearer (DRB).
  • RRC_INACTIVE the MAC design related to the Inactive (RRC_INACTIVE) state is needed as an enhancement to the limitations of the control plane (CP) / user plane (UP) -solution agreed to the NB-IoT.
  • CP-solution it is necessary to solve SRB-based MME-gNB load increase problem, delay resolution, and QoS discrimination by transmitting initial small data based on NAS security (SRB, signaling radio bearer) in idle state.
  • SRB signaling radio bearer
  • UP-solution operates to minimize CN (core network) burden and delay due to RRC signaling through RRC connection resume / suspend procedure, but because of data transmission in connected state, there is a problem of standby power consumption such as C-DRX. .
  • RRC_INACTIVE Inactive
  • Idle-based NB-IoT operation aperiodic CQI (channel quality indicator), BSR (buffer status report) related information, new monitoring timer, etc.
  • RRC_INACTIVE RRC Inactive
  • PDCP entities may be the same or different in the same base station, and even if different cells, PDCP entities may be the same or different.
  • an embodiment of the present invention may consider the following operation according to the necessity of a new security key when the terminal moves to a different cell / PDCP entity.
  • the UE identifies / detects movement to different cell / PDCP entities
  • RRC signaling (RRC connection request, or RRC connection resume request) includes UE_ID and MAC-I.
  • the terminal derives a new security key based on INACTIVE_count, and in this case, the corresponding data + RRC signaling is ciphered based on the new key, integrity protected, and includes an operation of transmitting MAC-I and INACTIVE_count.
  • Another embodiment of the present invention includes transmitting data to a DRB when RRC signaling is not needed.
  • a new MAC CE (MAC header) format indicating RRC resume is required for data transmission. This includes the operation of transmitting corresponding information by defining a new MAC-CE format in addition to the existing MAC-CE as follows.
  • a new MAC-CE may be indicated by selecting one bit string from among reserved bits (01011-11001).
  • 01011 includes an example of operating as a MAC CE indicating UL data transmission transmitted during an Inactive (RRC_INACTIVE) state.
  • RRC_INACTIVE Inactive
  • the specific index number may be changed.
  • the corresponding information of UL data transmission in Inactive includes an operation of setting a window for continuously monitoring a physical downlink control channel (PDCCH) and waiting time for the terminal and the base station.
  • PDCCH physical downlink control channel
  • the method includes a method of referring to TA information or BSR information channel CQI information acquired from previous UL data in Inactive (RRC_INACTIVE).
  • MAC CE new MAC header format
  • DL ACK for UL data in Inactive RRC_INACTIVE
  • it includes an operation of increasing the low power efficiency of the UE by setting a window for continuously monitoring a short PDCCH.
  • a method of operating when the target base station is different from the anchor base station is as shown in the following embodiment.
  • the anchor base station transmits security key related information for generating a new security key to the target base station.
  • the anchor base station omits the operation of transmitting the security key related information for generating the new security key to the target base station.
  • the method includes using a security key (old) by lowering the NG changing counter (NCC) again.
  • Anchor Because it forwards the entire encrypted data to the base station, it consumes resources of backhaul (X2, Xn, etc.), and delay occurs because data is transmitted to Core-network (S-GW) via Anchor base station (PDCP entity).
  • S-GW Core-network
  • PDCP entity Anchor base station
  • UE_ID In order to support UE specific anchor, UE_ID must be deciphered at target base station. Therefore, security key to be applied to UE_ID is commonly used between anchor base station at target base station so that only the corresponding part can be deciphered at target.
  • the anchor base station can be fixed within a certain area (network-wise paging area or tracking area) set by the network, and forwarded to the fixed anchor base station as a whole.
  • a target base station for transmitting data in an Inactive (RRC_INACTIVE) state transmits data directly to a core network (S-GW) without data forwarding to an existing anchor base station.
  • target base station for transmitting data in Inactive (RRC_INACTIVE) state forwards all encrypted data to existing anchor base station through Core-network (S- How to send to GW)
  • Service requirements of the terminal service type, use case, ultra reliable low latency communication (URLLC), enhanced mobile broadband (eMBB), massive machine type communications (MMTC) or radio access network (RAN) slice information, network slice)
  • URLLC ultra reliable low latency communication
  • eMBB enhanced mobile broadband
  • MMTC massive machine type communications
  • RAN radio access network
  • NSSAI network slice selection assistance information
  • the NSSAI is network slice related information corresponding to the terminal and can be used as additional information in the DRB configuration by transmitting the corresponding information to the base station.
  • One embodiment includes the following operations because data deciphering and CN (S-GW, etc.) are required without data forwarding from the target cell to the anchor base station;
  • data deciphering includes a security key application method and a deciphering analysis method including each or all of ciphering and integrality protection.
  • This operation may include an operation applied differently according to UE capability or applied to all Inactive (RRC_INACTIVE) state terminals.
  • PA zone is fixed to the network
  • PA region is UE-specific
  • TA zone is fixed to the network
  • TA area is UE-specific
  • a CU is a control unit
  • a DU is an RF related processing unit
  • a PDCP is assumed to be located in a CU.
  • RLC / MAC may be located in CU / DU and PHY is assumed to be located in DU.
  • the term itself includes various extended versions in addition to the CU and DU, and is applicable to the separation and extension structure of the control unit and the RF.
  • FIG. 5 is a diagram illustrating a generation and application of a security key for a data transmission operation in an Inactive (RRC_INACTIVE) state of a terminal in a communication system according to an embodiment of the present invention.
  • Enable PDCP_entity info is a parameter indicating whether PDCP_entity ID information is transmitted to the UE, and may be used as a criterion for determining whether PDCP_entity is the same as or different from the anchor PDCP storing the UE context when the UE is suspended.
  • the INACTIVE counter is a security key generation related parameter for generating a new key when the PDCP_entity is different from the anchor PDCP storing the UE context or when the change is unknown when the terminal is suspend.
  • the mobile communication system may include a terminal 505, an anchor cell 510, a new cell 515, and a core network node 520.
  • the core network node 520 may include an MME and / or an S-GW.
  • the fixed cell 510 may be named a fixed base station
  • the new cell 515 may be named a new base station.
  • the transmission / reception operation of the cell may be understood as the transmission / reception operation of the base station corresponding to the cell.
  • the core network node 520 may transmit an INACTVE message to the fixed cell 510.
  • the INACTIVE message may include INACTIVE_NH and INACTIVE_NCC.
  • the fixed cell 510 receiving the INACTIVE message may transmit an RRC connection suspend message to the terminal 505 (operation 533).
  • the terminal 505 may store a UE context.
  • the UE context may include an old key (A_KeNB) and INACTIVE_counter.
  • the fixed cell 510 may store a UE context.
  • the UE context may include an old key (A_KeNB) and INACTIVE_counter.
  • the terminal 505 may move to a new cell 515 or a new base station.
  • the terminal 505 may receive at least one of system information, SRS, or RS from the moved new cell 515.
  • At least one of the system information, the SRS, or the RS may include the PDCP entity ID of the new cell 515 (operation 541).
  • the uplink data transmitted by the terminal 505 may be generated.
  • the terminal 505 may increase the INACTIVE counter. For example, you can increase the counter value by one.
  • the terminal 505 may derive a new security key (T_KeNB) and apply it. A new security key can be derived / generated from the INACTIVE_counter.
  • the UE 505 may transmit an RRC connection resume request message to the new cell 515.
  • the UE may transmit uplink data (UL data) together with the RRC connection resumption request message.
  • the UL data may include a UE ID and / or an inactive counter and may be encrypted with a new security key (cyphered and integrity protected).
  • the new cell 515 may identify the fixed cell 510 or the fixed base station.
  • the new cell 515 may identify the fixed cell 510 using the UE ID, which may be a Resume ID.
  • the Resume ID may be provided to the terminal 505 in operation 533.
  • the new cell 515 transmits a UE Context Search request to the fixed cell 510.
  • the terminal context search request may include a UE_ID.
  • the fixed cell 510 transmits a UE Context Response to a new cell 515.
  • the terminal context search response may include T_KeNB and INACTIVE_NCC.
  • the new cell 515 stores the terminal context.
  • the terminal context may include information (T_KeNB, INACITVE_NCC) about a new security key received from the fixed cell 510.
  • the new cell 515 transmits an RRC connection response message to the terminal 505.
  • the RRC connection response message may include resume / suspend information and ACK / NACK information.
  • the terminal 505 transmits an RRC connection reconfig complete message to the new cell 515.
  • the new cell 515 sends a path switch request message to the core network node 520.
  • the core network node 520 sends a path switch response message to the new cell 515.
  • the new cell 515 transmits a context release message to the fixed cell 510.
  • PDCP_entity_Indication indicates that the network provides PDCP entity information.
  • NULL indicates that the network does not provide PDCP entity information.
  • Enable PDCP_entity info PDCP_entity_Indication
  • the UE and the base station can know whether the network provides PDCP entity information.Based on this, the ID itself can be transmitted as System Information (mandatory or on). Method of transmitting as data through -demand SI, mapping to radio resources (time of TTI, frequency of subcarrier, space such as beam index, scrambling sequence, etc.) to inform the terminal of ID information of PDCP entity It includes a method.
  • the terminal receives ID related information of the PDCP entity based on the corresponding PDCP_entity_method and determines whether to use the NCC value of the security key to be applied as it is or whether to generate a new security key by NCC + and apply the corresponding security key to Inactive ( RRC_Inactive) state can transmit data.
  • RRC release message RRC Connection suspend
  • security key information to be applied to inactive data transmission such as Inactive_counter is transmitted.
  • the security key can be common for the Inactive (RRC_INACTIVE) state within cell-specific or configured areas based on MME / PA / TA or cell list.
  • Connected_key is an operation that uses the security key used by the corresponding gNB and transmits the security key related information.
  • Inactive_Key A security key used in the Inactive (RRC_INACTIVE) state separately from the security key used by the gNB in the connected state. This is an operation for transmitting related information, and NULL indicates that there is no need to transmit security key related information in a corresponding network.
  • the UE transmits inactive data only within a serving (anchor) base station (cell, PDCP entity). If the mobile station moves out of the serving (anchor) base station (cell, PDCP entity), it performs an operation of updating the security key after the transition to the connected state. In this case, the RRC connection request or the RRC resume request applies NAS security, thereby indicating that the security key update is not necessary in the Inactive (RRC_INACTIVE) state.
  • a method for indicating PDCP Change Indication in a control signal between base stations corresponding to a cell is included.
  • PDCP Change Indication indicates the PDCP information for the corresponding DU / corresponding cell that the UE moves to request an RRC connection or add or handover to a cell.
  • the terminal indicates whether a new security key to be used by the 5G base station gNB newly accessed by the UE through (RRC connection, cell addition, handover), etc. is indicated by a field 'KgNB update required'.
  • the terminal informs whether the PDCP recovery should be performed in the newly-connected 5G base station gNB through RRC connection, cell addition, handover), etc. as a 'PDCP data recovery required' field.
  • FIG. 7 illustrates generation and application of a security key for a data transmission operation in an Inactive (RRC_INACTIVE) state in a communication system according to an exemplary embodiment of the present invention.
  • a method of transmitting security key information to be applied to inactive data transmission such as Inactive_counter.
  • the security key may be common for the purpose of Inactive (RRC_INACTIVE) state within the region specific to the cell specific or configured based on MME / PA / TA or cell list as described above.
  • the UE determines whether to generate a new security key (operation of generating and applying a new key when PDCP_entity is changed), and DATA, UE_ID (eg resume_ID, S-TMSI (SAE-temporary) to transmit the corresponding security key. mobile subscriber identity), T-RNTI, etc.) and the new base station receives the data and processes the data at the target (security key decoding and CN (S-GW)) or forwarding to the anchor cell.
  • S-GW security key decoding and CN
  • a method of transmitting an RRC connection request by adding a bit indicating whether forwarding is necessary to an anchor base station or whether an old key is used or not is forwarded to an anchor base station in a new MAC CE format.
  • the mobile communication system may include a terminal 705, an anchor cell 710, a new cell 715, and a core network node 720.
  • Core network node 720 may include an MME and / or an S-GW.
  • the core network node 520 may transmit an INACTVE message to the fixed cell 710.
  • the INACTIVE message may include INACTIVE_NH and INACTIVE_NCC.
  • the fixed cell 710 receiving the INACTIVE message may transmit an RRC connection suspend message to the terminal 705 (operation 733).
  • the terminal 705 may store a UE context.
  • the UE context may include an old key (A_KeNB) and INACTIVE_counter.
  • the fixed cell 710 may store a UE context.
  • the UE context may include an old key (A_KeNB) and INACTIVE_counter.
  • the terminal 705 may move to a new cell 515 or a new base station.
  • the terminal 705 may receive at least one of system information, SRS, or RS from the moved new cell 715.
  • At least one of the system information, the SRS or the RS may include the PDCP entity ID of the new cell 715 (operation 741).
  • the uplink data transmitted by the terminal 705 may be generated.
  • the terminal 705 checks whether the PDCP entity is different. That is, in operation 733, the terminal 705 checks whether the PDCP entity of the cell transmitting the message is different from the PDCP entity of the currently moved cell. If the PDCP entity is different, the operation proceeds to operation 745.
  • the terminal 705 may increase the INACTIVE counter. For example, you can increase the counter value by one.
  • the terminal 705 may derive a new security key (T_KeNB) and apply it. A new security key can be derived / generated from the INACTIVE_counter.
  • T_KeNB new security key
  • the UE 705 may transmit an RRC connection resume request message to the new cell 715.
  • the UE may transmit uplink data (UL data) together with the RRC connection resumption request message.
  • the UL data may include a UE ID and / or an inactive counter and may be encrypted with a new security key (cyphered and integrity protected).
  • the RRC connection resumption request message may include information indicating whether to forward the UL data to the fixed cell 710 and information indicating whether to use an old key. A bit of information indicating whether forwarding of the UL data is required or a bit indicating information indicating whether to use an old key may be added to a new MAC CE format.
  • the new cell 715 may attempt to send UL data to the core network node 720 and forward to the fixed cell 710 if it fails.
  • the new cell 715 may identify the fixed cell 710 or the fixed base station.
  • the new cell 715 may identify the fixed cell 710 using the UE ID, which may be at least one of Resume ID, S-TMSI, and T-RNTI.
  • the Resume ID may be provided to the terminal 705 in operation 733.
  • the new cell 715 transmits a UE Context Search request to the fixed cell 710.
  • the terminal context search request may include a UE_ID.
  • the fixed cell 710 transmits a UE Context Response to a new cell 715.
  • the terminal context search response may include T_KeNB and INACTIVE_NCC.
  • the new cell 715 stores the terminal context.
  • the terminal context may include information (T_KeNB, INACITVE_NCC) about a new security key received from the fixed cell 710.
  • the new cell 715 transmits an RRC connection response message to the terminal 705.
  • the RRC connection response message may include resume / suspend information and ACK / NACK information.
  • the terminal 705 transmits an RRC connection reconfig complete message to the new cell 715.
  • the new cell 715 transmits a path switch request message to the core network node 720.
  • the core network node 720 transmits a path switch response message to the new cell 715.
  • the new cell 715 transmits a context release message to the fixed cell 710.
  • FIG. 8 is a diagram illustrating an example of notation of corresponding information when a communication system transmits PDCP entity information in a communication system according to an embodiment of the present invention.
  • an embodiment of the present invention provides a method for the base station to further transmit PDCP entity information to the corresponding terminal.
  • a method for the base station may be a method of additionally transmitting the entire ID of the PDCP entity or the ID of the PDCP entity uniquely defined within the tracking area or the paging area as an additional field in addition to the existing cell ID (PCell ID).
  • PCell ID existing cell ID
  • some information of the PDCP entity may be included as an additional field in an existing cell ID.
  • the same security key is used when the same DU is used even if the DU is changed in a relatively wide area.
  • whether or not the same PDCP can be indicated using only some bits of the PCDP ID, and through this, it can be indicated whether to change the PDCP.
  • the ID itself is transmitted as data through system information (mandatory or on-demand SI), radio resources (time of TTI, frequency of subcarrier, beam index, etc.). It is possible to use a method of informing the terminal of ID information of the PDCP entity by mapping the space, a scrambling sequence, etc.).
  • system information managed or on-demand SI
  • radio resources time of TTI, frequency of subcarrier, beam index, etc.
  • RS Reference signal
  • FIG. 9 is a diagram illustrating a generation and application of a security key for a data transmission operation in an INACTIVE state in a communication system according to an embodiment of the present invention.
  • Enable PDCP_entity info 1
  • a method of transmitting this by marking the RRC connection suspend which is transitioned to RRC INACTIVE and transmitting a new security key based on this method (when PDCP_entity is changed)
  • a method of generating a new security key in the process of generating a new key based on Inactive_Conter ie, depending on whether the PDCP_entity has been changed using the old key (A_KeNB) and INACTIVE_counter included in the stored UE context as input values. Determine whether to generate a new key.
  • the operation includes using an existing old key without increasing the inactive counter, and generating a new new key based on the existing old key by increasing the inactive counter when the PDCP_entity is changed.
  • RRC connection request and RACH transition from RRC_Inactive to RRC_Connected state include the operation of using the old key without increasing the inactive counter at all times.
  • the Inactive counter is always increased during the RRC connection request and the RACH operation that transitions from the RRC_Inactive to the RRC_Connected state according to the base station configuration or the terminal configuration. It includes the operation of generating.
  • the present invention includes a method of separating and using a security key to be used in RRC_connected and a security key to be used in an RRC INACTIVE state.
  • an access stratum (AS) security for INACTIVE data transmission is used.
  • the key can be applied in common between the target base station and the anchor base station.
  • PA paging area
  • FIG. 10 illustrates generation and application of a security key for a data transmission operation in an Inactive (RRC_INACTIVE) state in a communication system according to an embodiment of the present invention.
  • the present invention relates to a method and a method of determining whether to generate a new security key based on the method.
  • the embodiment of FIG. 10 includes an operation of applying an existing key when the PDCP_entity of the moved cell is the same and a method of transmitting a DL ACK / NACK in an RRC connection response.
  • a mobile communication system may include a terminal 1005, an anchor cell 1010, a new cell 1015, and a core network node 1020.
  • the core network node 1020 may include an MME and / or an S-GW.
  • the core network node 1020 may transmit an INACTVE message to the fixed cell 710.
  • the INACTIVE message may include INACTIVE_NH and INACTIVE_NCC.
  • the fixed cell 1010 receiving the INACTIVE message may transmit an RRC connection suspend message to the terminal 1005 (operation 1033).
  • the terminal 1005 may store a UE context.
  • the UE context may include an old key (A_KeNB) and INACTIVE_counter.
  • the fixed cell 1010 may store a UE context.
  • the UE context may include an old key (A_KeNB) and INACTIVE_counter.
  • the terminal 1005 may move to a new cell 1015 or a new base station.
  • the terminal 1005 may receive at least one of system information, SRS, or RS from the moved new cell 1015.
  • At least one of the system information, the SRS, or the RS may include a PDCP entity ID of the new cell 1015 (operation 1041).
  • the UE 1005 may generate uplink data to be transmitted.
  • the terminal 1005 checks whether the PDCP entity is different. That is, in operation 1033, the terminal 1005 checks whether the PDCP entity of the cell transmitting the message is different from the PDCP entity of the currently moved cell. If the PDCP entities are identical, the operation proceeds to operation 1045. In operation 1045, the terminal 1005 maintains the INACTIVE counter without increasing it. In operation 1047, the terminal 1005 uses the old key (A_KeNB) previously used as a security key.
  • A_KeNB old key
  • the UE 1005 may transmit UL data to the new cell 1015 when transmitting an RRC Connection request message.
  • the UL data may include a UE ID and may be encrypted with an old key.
  • the new cell 1015 may identify the fixed cell 1010 or the fixed base station.
  • the new cell 1015 may identify the fixed cell 1010 using the UE ID, which may be at least one of Resume ID, S-TMSI, and T-RNTI.
  • the Resume ID may be provided to the terminal 1005 in operation 1033.
  • the new cell 1015 transmits a UE Context Search request to the fixed cell 1010.
  • the terminal context search request may include a UE_ID.
  • the fixed cell 1010 transmits a UE Context Response to a new cell 1015.
  • the UE context search response may include a PDCP sequence number (SN).
  • the new cell 1015 stores the terminal context.
  • the UE context may include an old key, Inactive_counter, and the new cell 1015 may update the PDCP SN.
  • the new cell 1015 transmits an RRC connection response message to the terminal 1005.
  • the RRC connection response message may include resume / suspend information, UE context update information, and ACK / NACK information.
  • the terminal 1005 transmits an RRC connection reconfig complete message to the new cell 1015.
  • the new cell 1015 transmits a path switch request message to the core network node 1020.
  • the core network node 1020 transmits a path switch response message to the new cell 1015.
  • the new cell 1015 transmits a context release message to the fixed cell 1010.
  • FIG. 11 is a diagram illustrating a security key generation and application for a data transmission operation in an Inactive (RRC_INACTIVE) state of a terminal in a communication system according to an embodiment of the present invention.
  • the embodiment of FIG. 11 includes a method of applying an existing key and piggybacking to paging for transmission of DL ACK / NACK when PDCP_entity of the moved cell is the same.
  • a mobile communication system may include a terminal 1105, an anchor cell 1110, a new cell 1115, and a core network node 1120.
  • the core network node 1120 may include an MME and / or an S-GW.
  • the core network node 1120 may transmit an INACTVE message to the fixed cell 1110.
  • the INACTIVE message may include INACTIVE_NH and INACTIVE_NCC.
  • the fixed cell 1110 having received the INACTIVE message may transmit an RRC connection suspend message to the UE 1105 (operation 1133).
  • the UE 1105 may store a UE context.
  • the UE context may include an old key (A_KeNB) and INACTIVE_counter.
  • the fixed cell 1110 may store a UE context.
  • the UE context may include an old key (A_KeNB) and INACTIVE_counter.
  • the terminal 1105 may move to a new cell 1115 or a new base station.
  • the terminal 1105 may receive at least one of system information, SRS, or RS from the moved new cell 1115.
  • At least one of the system information, the SRS or the RS may include the PDCP entity ID of the new cell 1115 (operation 1141).
  • uplink data transmitted by the terminal 1105 may be generated.
  • the terminal 1105 checks whether the PDCP entity is different. That is, the UE 1105 checks whether the PDCP entity of the cell which has transmitted the message is different from the PDCP entity of the cell which is currently moved in operation 1133. If the PDCP entities are identical, the operation proceeds to operation 1145. In operation 1145, the terminal 1105 maintains the INACTIVE counter without increasing it. In operation 1147, the terminal 1105 uses an old key (A_KeNB) previously used as a security key.
  • A_KeNB old key
  • the UE 1105 may transmit UL data to the new cell 1115 without RRC signaling.
  • the UL data may include a UE ID and may be encrypted with an old key.
  • the new cell 1115 may identify the fixed cell 1110 or the fixed base station.
  • the new cell 1115 may identify the fixed cell 1110 using the UE ID, and the UE ID may be at least one of Resume ID, S-TMSI, and T-RNTI.
  • the Resume ID may be provided to the terminal 1105 in operation 1133.
  • the new cell 1115 transmits a UE Context Search request to the fixed cell 1110.
  • the terminal context search request may include a UE_ID.
  • the fixed cell 1110 transmits a UE Context Response to a new cell 1115.
  • the UE context search response may include a PDCP sequence number (SN).
  • the new cell 1115 stores the terminal context.
  • the UE context may include an old key, Inactive_counter, and the new cell 1015 may update the PDCP SN.
  • the new cell 1115 transmits a path switch request message to the core network node 1120.
  • the core network node 1120 transmits a path switch response message to the new cell 1115.
  • the new cell 1115 transmits a context release message to the fixed cell 1110.
  • the core network node 1120 transmits a paging message to the fixed cell 1110.
  • the fixed cell 1110 may transmit a paging message to the terminal 1105, and piggyback ACK / NACK on the paging message.
  • FIG. 12 is a diagram illustrating a structure of a terminal according to an embodiment of the present invention.
  • the terminal may include a transceiver 1210, a controller 1220, and a storage 1230.
  • the controller 1220 may be defined as a circuit or an application specific integrated circuit or at least one processor.
  • the transceiver 1210 may exchange a signal with another network entity.
  • the transceiver 1210 may receive system information from, for example, a base station, and may receive a synchronization signal or a reference signal.
  • the controller 1220 may control the overall operation of the terminal according to the embodiment proposed by the present invention.
  • the storage unit 1230 may store at least one of information transmitted and received through the transceiver 1210 and information generated through the controller 1220.
  • the control unit 1220 receives a radio resource control (RRC) connection stop message including packet data convergence protocol (PDCP) entity related information and deactivation counter information from a first base station, Stores the first security key and the deactivation counter information being used, the terminal moves to a second base station, identifies uplink data to be transmitted by the terminal, and based on the PDCP entity related information and deactivation counter information.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • a security key may be generated, and the uplink data encrypted with the second security key may be transmitted to the second base station.
  • the controller 1220 determines whether the PDCP entity of the first base station and the PDCP entity of the second base station are the same when the ID of the PDCP entity is provided according to the PDCP entity related information.
  • the deactivation counter may be updated to generate the second security key. If the PDCP entities of the first base station and the second base station are the same, the second security key may be the same as the first security key.
  • the controller 1220 updates the deactivation counter regardless of whether the PDCP entity of the first base station and the PDCP entity of the second base station are the same.
  • the second security key may be generated.
  • the controller 1220 may control to transmit the uplink data together with the RRC connection resumption request message. In addition, the controller 1220 may control to transmit the identifier of the terminal and the deactivation counter used to generate the second security key together with the uplink data. In addition, the control unit 1220 receives system information including the cell identifier of the second base station and the PDCP entity identifier of the second base station from the second base station, and based on the PDCP entity identifier of the second base station; The PDCP entity of the first base station and the PDCP entity of the second base station may be controlled to determine whether the same.
  • FIG. 13 is a diagram illustrating a structure of a base station according to an embodiment of the present invention.
  • the base station may include a transceiver 1310, a controller 1320, and a storage 1330.
  • the controller 1320 may be defined as a circuit or application specific integrated circuit or at least one processor.
  • the transceiver 1310 may transmit and receive signals with other network entities.
  • the transceiver 1310 may transmit system information to the terminal, and may transmit a synchronization signal or a reference signal.
  • the controller 1320 may control the overall operation of the base station according to the embodiment proposed by the present invention.
  • the storage unit 1330 may store at least one of information transmitted and received through the transceiver 1310 and information generated through the controller 1320.
  • the core network node may be an MME or an S-GW, or may be a function corresponding to an MME or a function corresponding to an S-GW.
  • the core network node may include a transceiver 1410, a controller 1420, and a storage 1430.
  • the controller 1420 may be defined as a circuit or an application specific integrated circuit or at least one processor.
  • the transceiver 1410 may transmit and receive signals with other network entities.
  • the transceiver 1410 may transmit system information to the terminal, and may transmit a synchronization signal or a reference signal.
  • the controller 1420 may control the overall operation of the core network node according to the embodiment proposed by the present invention.
  • the storage 1430 may store at least one of information transmitted and received through the transceiver 1410 and information generated through the controller 1420.

Landscapes

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

Abstract

L'invention concerne un technique de communication permettant de fusionner, à une technologie de l'Internet des objets (IOT), un système de communication 5G destiné à prendre en charge un débit de transmission de données supérieur à celui d'un système 4G, et un système associé. L'invention peut être appliquée à des services intelligents (par exemple, une maison intelligente, un bâtiment intelligent, une ville intelligente, une voiture intelligente ou une voiture connectée, des soins de santé, l'enseignement numérique, le commerce de détail, les services de sécurité et de sûreté, ou autres) sur la base d'une technologie de communication 5G et d'une technologie liée à l'IoT. De plus, l'invention concerne un procédé par lequel un terminal fonctionne dans un système de communication sans fil, le procédé comprenant les étapes consistant à : recevoir un message d'arrêt de connexion de commande de ressource radio (RRC) comprenant des informations relatives à une entité de protocole de convergence de données par paquets (PDCP) et des informations de compteur d'inactivation et provenant d'une première station de base ; stocker une première clé de sécurité actuellement utilisée par le terminal, et les informations de compteur d'inactivation ; permettre au terminal de se déplacer vers une seconde station de base ; permettre au terminal de vérifier des données de liaison montante à transmettre ; générer une seconde clé de sécurité sur la base des informations relatives à l'entité PDCP et des informations de compteur d'inactivation ; et transmettre les données de liaison montante chiffrées à l'aide de la seconde clé de sécurité à la seconde station de base.
PCT/KR2018/001963 2017-02-20 2018-02-14 Procédé et dispositif d'amélioration de sécurité dans un système de communication sans fil WO2018151546A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR20170022541 2017-02-20
KR10-2017-0022541 2017-02-20

Publications (1)

Publication Number Publication Date
WO2018151546A1 true WO2018151546A1 (fr) 2018-08-23

Family

ID=63169565

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2018/001963 WO2018151546A1 (fr) 2017-02-20 2018-02-14 Procédé et dispositif d'amélioration de sécurité dans un système de communication sans fil

Country Status (1)

Country Link
WO (1) WO2018151546A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113273234A (zh) * 2019-01-18 2021-08-17 联想（新加坡）私人有限公司 针对小数据业务的密钥刷新
CN114071803A (zh) * 2020-07-31 2022-02-18 中国移动通信有限公司研究院 数据传输方法、终端及网络侧设备
WO2023004594A1 (fr) * 2021-07-27 2023-02-02 Huawei Technologies Co.,Ltd. Dispositifs et procédé de configuration d'un dispositif utilisateur pendant une transmission de petites données
US20230209415A1 (en) * 2017-06-15 2023-06-29 Qualcomm Incorporated Techniques and apparatuses for user equipment mobility in multi-connectivity mode

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140087743A1 (en) * 2012-02-28 2014-03-27 Sierra Wireless Method and device for controlling the access of equipment for a network of the machine-to-machine type to the resources of a cellular telephony network
WO2017025144A2 (fr) * 2015-08-13 2017-02-16 Nokia Solutions And Networks Oy Évaluation d'horloge d'inactivité

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140087743A1 (en) * 2012-02-28 2014-03-27 Sierra Wireless Method and device for controlling the access of equipment for a network of the machine-to-machine type to the resources of a cellular telephony network
WO2017025144A2 (fr) * 2015-08-13 2017-02-16 Nokia Solutions And Networks Oy Évaluation d'horloge d'inactivité

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
OPPO: "Discussion on IDLE/INACTIVE UE Mobility", R2-1700957, 3GPP TSG-RAN2#97, 4 February 2017 (2017-02-04), Athens, Greece, XP051223315 *
PATRICK MARSCH: "5G Radio Access Network Architecture: Design Guidelines and Key Considerations", IEEE COMMUNICATIONS MAGAZINE, vol. 54, no. 11, XP011634866 *
SAMSUNG: "Overview of the NR RRC state machine and modelling of the INACTIVE state", R2-167493, 3GPP TSG-RAN WG2 MEETING #96, 5 November 2016 (2016-11-05), XP051177409 *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230209415A1 (en) * 2017-06-15 2023-06-29 Qualcomm Incorporated Techniques and apparatuses for user equipment mobility in multi-connectivity mode
US12075289B2 (en) * 2017-06-15 2024-08-27 Qualcomm Incorporated Techniques and apparatuses for user equipment mobility in multi-connectivity mode
CN113273234A (zh) * 2019-01-18 2021-08-17 联想（新加坡）私人有限公司 针对小数据业务的密钥刷新
CN114071803A (zh) * 2020-07-31 2022-02-18 中国移动通信有限公司研究院 数据传输方法、终端及网络侧设备
CN114071803B (zh) * 2020-07-31 2025-04-01 中国移动通信有限公司研究院 数据传输方法、终端及网络侧设备
WO2023004594A1 (fr) * 2021-07-27 2023-02-02 Huawei Technologies Co.,Ltd. Dispositifs et procédé de configuration d'un dispositif utilisateur pendant une transmission de petites données

Similar Documents

Publication Publication Date Title
WO2020209620A1 (fr) Procédé et ue de gestion de procédure de radiomessagerie dans un réseau de communication sans fil
WO2020045969A1 (fr) Procédé et équipement d'utilisateur pour optimiser des ressources d'un réseau de communication sans fil tout en fournissant des services 5g
WO2019194641A1 (fr) Procédé et appareil de mise en œuvre de couche de protocole de terminal dans un mode inactif de système de communications mobile de prochaine génération
WO2019190205A1 (fr) Procédé et appareil pour effectuer une réception discontinue dans un système de communication sans fil
WO2018128477A1 (fr) Procédé et appareil de commande de transport de données entre des systèmes de réseau sans fil
WO2017171529A1 (fr) Procédé destiné à la sélection de ressources de transmission v2x au moyen d'un terminal dans un système de communication sans fil et terminal utilisant ledit procédé
WO2017164674A1 (fr) Procédé pour changer un mode de connexion dans une station de base, et station de base associée, et procédé pour changer un mode de connexion dans un équipement utilisateur, et équipement utilisateur associé
WO2015020449A1 (fr) Procédé de génération et de gestion de clé de sécurité d'une structure distribuée pdcp pour prise en charge d'une double connectivité
WO2019160327A1 (fr) Procédé et dispositif permettant d'effectuer une resélection de cellule dans un système de communication mobile
WO2019074347A1 (fr) Équipement d'utilisateur (ue) et réseau central permettant de gérer une congestion de tranche de réseau dans un système de communication sans fil
WO2017126928A1 (fr) Procédé de changement de mode de connexion et entité de gestion de mobilité
WO2019194528A1 (fr) Procédé et appareil pour l'exécution d'une transmission
WO2018038490A1 (fr) Procédé et système de configuration de réseau de données régional dans un réseau de communication sans fil
WO2016190639A1 (fr) Procédé et dispositif pour rapporter un état de tampon durant une combinaison de lte et lan sans fil dans un système de communications sans fil
WO2020251240A1 (fr) Procédé et appareil pour améliorer la fiabilité de service dans un système de communications sans fil
WO2018070845A1 (fr) Procédé de transmission de signal de synchronisation de liaison latérale exécuté par un terminal dans un système de communications sans fil, et terminal utilisant ledit procédé
WO2018174638A1 (fr) Procédé et dispositif de gestion d'état de session en fonction de la position d'un terminal dans un système de communication sans fil
WO2017126942A1 (fr) Procédé et équipement utilisateur permettant de recevoir des données, et procédé et station de base permettant de transmettre des données
WO2017030399A1 (fr) Procédé et appareil d'accès d'ue
WO2012141480A2 (fr) Procédé et appareil de transmission et de réception de données dans un système de communication mobile
WO2017030427A1 (fr) Procédé et appareil d'accès, de transfert et de commande de chiffrement d'un ue
WO2017131479A1 (fr) Procédé et appareil permettant de réduire le surdébit de signalisation et la batterie du terminal
WO2018151546A1 (fr) Procédé et dispositif d'amélioration de sécurité dans un système de communication sans fil
WO2019221493A1 (fr) Procédé de commande de terminal pour service ido cellulaire dans un système de communication mobile 5g
WO2019209032A1 (fr) Terminal de véhicule pour commander une transmission de messages v2x entre des terminaux de véhicule via un service v2x dans un système de communication sans fil, et procédé de commande de communication associé

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

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

Country of ref document: EP

Kind code of ref document: A1

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载