US20220159537A1 - Apparatus, system and method for dual connectivity - Google Patents
Apparatus, system and method for dual connectivity Download PDFInfo
- Publication number
- US20220159537A1 US20220159537A1 US17/587,228 US202217587228A US2022159537A1 US 20220159537 A1 US20220159537 A1 US 20220159537A1 US 202217587228 A US202217587228 A US 202217587228A US 2022159537 A1 US2022159537 A1 US 2022159537A1
- Authority
- US
- United States
- Prior art keywords
- senb
- menb
- mme
- message
- mobile communication
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 41
- 230000009977 dual effect Effects 0.000 title claims description 27
- 238000012986 modification Methods 0.000 claims description 34
- 230000004048 modification Effects 0.000 claims description 34
- 238000010295 mobile communication Methods 0.000 claims description 14
- 238000012795 verification Methods 0.000 abstract description 15
- NRNCYVBFPDDJNE-UHFFFAOYSA-N pemoline Chemical compound O1C(N)=NC(=O)C1C1=CC=CC=C1 NRNCYVBFPDDJNE-UHFFFAOYSA-N 0.000 description 8
- 238000004891 communication Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 7
- 230000004044 response Effects 0.000 description 4
- 238000012790 confirmation Methods 0.000 description 3
- 238000009795 derivation Methods 0.000 description 3
- 230000011664 signaling Effects 0.000 description 2
- 101001100327 Homo sapiens RNA-binding protein 45 Proteins 0.000 description 1
- 102100038823 RNA-binding protein 45 Human genes 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/04—Key management, e.g. using generic bootstrapping architecture [GBA]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/24—Reselection being triggered by specific parameters
- H04W36/26—Reselection being triggered by specific parameters by agreed or negotiated communication parameters
- H04W36/28—Reselection being triggered by specific parameters by agreed or negotiated communication parameters involving a plurality of connections, e.g. multi-call or multi-bearer connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/04—Key management, e.g. using generic bootstrapping architecture [GBA]
- H04W12/041—Key generation or derivation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/04—Key management, e.g. using generic bootstrapping architecture [GBA]
- H04W12/043—Key management, e.g. using generic bootstrapping architecture [GBA] using a trusted network node as an anchor
- H04W12/0433—Key management protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/08—Load balancing or load distribution
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0055—Transmission or use of information for re-establishing the radio link
- H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
- H04W36/00695—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink using split of the control plane or user plane
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- 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
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/12—Detection or prevention of fraud
- H04W12/121—Wireless intrusion detection systems [WIDS]; Wireless intrusion prevention systems [WIPS]
- H04W12/122—Counter-measures against attacks; Protection against rogue devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0055—Transmission or use of information for re-establishing the radio link
- H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/08—Access point devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/16—Interfaces between hierarchically similar devices
- H04W92/20—Interfaces between hierarchically similar devices between access points
Definitions
- the present invention relates to an apparatus, a system and a method for DC (Dual Connectivity) or SCE (Small Cell Enhancement), and particularly to a technique to secure SeNB (Secondary eNB (evolved Node B)) Addition/Modification procedure in order to provide security in dual connectivity for the given UE (User Equipment).
- DC Direct Connectivity
- SCE Small Cell Enhancement
- SeNB Secondary eNB (evolved Node B)
- Addition/Modification procedure in order to provide security in dual connectivity for the given UE (User Equipment).
- the SCE or DC was defined in 3GPP (3rd Generation Partnership Project) RAN (Radio Access Network) working groups, and it has initiated a study on security aspect and impact on the architecture 1 A defined in NPL 1.
- 3GPP 3rd Generation Partnership Project
- RAN Radio Access Network
- RRC Radio Resource Control
- each UE is connected to one MeNB and one SeNB. There can be multiple bearers between SeNB and UE.
- the key for UE and SeNB user plane communication protection, denoted as S-KUPenc, is derived at SeNB and UE from a key S-KeNB shared between UE and SeNB.
- the S-KeNB is derived at MeNB and sent to SeNB.
- UE derives the same S-KeNB at its side.
- NPL 1 3GPP TR 36.842, “Study on Small Cell enhancements for E-UTRA and E-UTRAN; Higher layer aspects (Release 12)”, V12.0.0, 2013-12
- NPL 2 S3-140211, 3GPP TSG SA WG 3 (Security) Meeting # 74
- NPL 3 S3-140209, 3GPP TSG SA WG 3 (Security) Meeting # 74
- NPL 4 S3-140210, 3GPP TSG SA WG 3 (Security) Meeting # 74
- the key S-KeNB is sent in SeNB “Addition/Modification Request” as disclosed in NPLs 2 to 4 . That is, the key S-KeNB is sent before SeNB is configured.
- SeNB rejects the configuration (due to its capability or some other reason), or the configuration fails, the MeNB has to derive a new S-KeNB for the next SeNB it attempts to configure, meanwhile increases the counter.
- SeNB DRB Data Radio Bearer
- SeNB may serve more than one UEs, and UE may connect to more than one SeNBs at different times or at same time (potential future architecture), giving a KSI (Key Set Identifier) can ensure UE and SeNB identify the key.
- KSI Key Set Identifier
- a mobile communication system for dual connectivity includes: a first Node B; a second Node B; a mobility management apparatus; and a gateway.
- the first Node B sends a Modification Indication message including information on dual connectivity or information on the second Node B to the mobility management apparatus.
- the mobility management apparatus sends a Modify Bearer Request message including the information on dual connectivity or the information on the second Node B to the gateway.
- a communication method for dual connectivity having a first Node B and a second Node B.
- This communication method includes: sending a Modification Indication message including information on dual connectivity or information on the second Node B from the first Node B to a mobility management apparatus; and sending a Modify Bearer Request message including the information on dual connectivity or the information on the second Node B from the mobility management apparatus to a gateway.
- a base station used in dual connectivity includes: sending means for sending a Modification Indication message including information on dual connectivity or information on a second base station for dual connectivity to a mobility management apparatus; and receiving means for receiving a Modification Confirmation message from the mobility management apparatus.
- This mobility management apparatus includes: receiving means for receiving a
- Modification Indication message including information on dual connectivity or information on a second Node B from a first Node B; and sending means for sending a Modify Bearer Request message including the information on dual connectivity or the information on the second Node B to a gateway.
- FIG. 1 is a block diagram showing a configuration example of a system according to an exemplary embodiment of the present invention.
- FIG. 2 is a sequence diagram showing an example of optimized SeNB Addition/Modification procedure in the system according to the exemplary embodiment.
- FIG. 3 is a sequence diagram showing a first example of bearer modification and SeNB verification at S-GW in the system according to the exemplary embodiment.
- FIG. 4 is a sequence diagram showing a second example of bearer modification and SeNB verification at S-GW in the system according to the exemplary embodiment.
- FIG. 5 is a sequence diagram showing a third example of bearer modification and SeNB verification at S-GW in the system according to the exemplary embodiment.
- FIG. 6 is a block diagram showing a configuration example of an MeNB according to the exemplary embodiment.
- FIG. 7 is a block diagram showing a configuration example of an MME according to the exemplary embodiment.
- FIG. 1 shows a configuration example of a system according to this exemplary embodiment, taking as an example the architecture where there is one SeNB per UE.
- This system includes a UE 10 , an MeNB 20 , an SeNB 30 , an MME (Mobility Management Entity) 40 , and an S-GW (Serving Gateway) 50 .
- a P-GW PDN (Public Data Network) Gateway) 60 as shown in FIGS. 4 to 6 .
- the UE 10 communicates with the MeNB 20 through a Uu interface.
- the MeNB 20 communicates with the SeNB 30 through an X2-C interface, and communicates with the MME 40 through an S 1 -MME interface.
- the S 1 -MME interface does not exist between the SeNB 30 and the MME 40 .
- U-Plane User-Plane
- Each of the MeNB 20 and the SeNB 30 communicates with the S-GW 50 through an S 1 -U interface.
- U-Plane traffic between the UE 10 and the S-GW 50 is transmitted through the MeNB 20 and the SeNB 30 in parallel for the purpose of offloading the MeNB 20 (in other words, for the purpose of offloading the backhaul S 1 -U interface between the MeNB 20 and the S-GW 50 ).
- one or more bearers DRB 1 to DRBn are established between the UE 10 and the SeNB 30 .
- this exemplary embodiment proposes that:
- S-KeNB is sent after step S 4 “SeNB Addition/Modification Command” shown in FIG. 2 .
- the SeNB 30 informs that it can configure bearers for the given UE 10 .
- the MeNB 20 manages the DRB status.
- the MeNB 20 sends KSI to both of the UE 10 and the SeNB 30 .
- FIG. 2 is based on the scenario disclosed in NPL 1 that there is only one MeNB and SeNB per UE. Note that processes at step S 4 , S 6 and S 7 are novel part in this invention.
- Step S 4 The SeNB 30 sends to the MeNB 20 its capabilities, if it is different from standard.
- the capabilities of the SeNB 30 are included in SeNB Addition/Modification Command.
- Step S 6 The MeNB 20 sends the S-KeNB and KSI after receiving the SeNB Addition/Modification Command.
- a new message for sending the S-KeNB and the KSI can be defined as Key Update.
- the reason for performing this step is: reduce the counter value usage. If the MeNB 20 sends the S-KeNB in the SeNB Addition/Modification Request at step S 2 , and the SeNB 30 does not have radio resource for the UE 10 , the MeNB 20 will have to derive a new key and send to next SeNB till it finds the capable SeNB.
- Step S 7 the MeNB 20 sends a KSI of S-KeNB to the UE 10 with the counter. This is to make sure that the UE 10 will use the same key as the SeNB 30 .
- the “update of the UP path towards the EPC is performed” as described in NPL 1.
- the MeNB 20 should inform the MME 40 and the S-GW 50 about the new bearer configured at the SeNB 30 , such that the S-GW 50 can start offloading the bearer(s) to the SeNB 30 .
- the network entity (MME 40 or S-GW 50 ) should perform verification that: 1) whether the request is coming from authenticated source (MeNB); and 2) whether SeNB is a valid eNB to which the traffic can be offload.
- the network entity (MME 40 or S-GW 50 ) can be pre-configured with information for the verification, or it can interact with another entity requesting for verification.
- the SeNB 30 or the MeNB 20 should indicate the DC configuration information (contains the configured DRB information, SeNB ID and SeNB IP address) to the S-GW 50 , such that the S-GW 50 knows that dual connectivity is being activated and a new bearer is added to the SeNB 30 , and the S-GW 50 should not release the bearer in the MeNB 20 .
- the MME 40 should also be informed that dual connectivity is being activated, such that it can behave accordingly including forwarding the S-GW 50 the information and should not behave same as in handover procedure when Path Switch Request message is received from the MeNB 20 .
- FIGS. 3 to 5 show alternatives 1 to 3 for the bearer modification and SeNB verification at the S-GW 50 , respectively.
- the MeNB 20 informs the MME 40 about newly configured SeNB and DRB, includes 1) DC configuration information (contains the configured DRB information, SeNB ID and SeNB IP address), and 2) indicator to show this is for DC.
- the MME 40 can forward the S-GW 50 the information in Step S 12 .
- Step S 12 The MME 40 sends bearer modification to the S-GW 50 indicating that this is a DC case together with information that the given DRB of a UE should be sent to the SeNB 30 .
- the network entity (MME 40 or S-GW 50 ) verifies: 1) whether the MeNB 20 is allowed to configure the SeNB 30 for the given UE 10 ; 2) whether the SeNB 30 is a valid network element; and 3 ) whether the SeNB 30 is authorized to provide dual connectivity.
- MME 40 the verification is done at the MME 40 , it should be after the MME 40 receives Step Sli message.
- S-GW 50 it can happen after it receives the message from the MME 40 .
- the procedure uses Path Switch procedure as indicated in G 1 of NPL 1. Note that it is initiated by the MeNB 20 .
- the MeNB 20 sends Path Switch Request message to the MME 40 , includes 1) DC configuration information (contains the configured DRB information, SeNB ID and SeNB IP address), and 2) indicator to show this is for DC. This is to inform that there is a new bearer from a SeNB has been configured not that UE has changed cell in handover procedure.
- Step S 22 When the MME 40 receives Path Switch Request, it determines whether this message is for DC or handover. If it is for DC, it will not compute NH (Next Hop) and not increase the NCC (Next-hop Chaining Counter) value it keeps. The MME 40 then sends Modify Bearer Request message to the S-GW 50 , includes the DC configuration information (contains the configured DRB information, SeNB ID and SeNB IP address) it received above.
- NH Next Hop
- NCC Next-hop Chaining Counter
- Step S 23 The S-GW 50 sends Modify Bearer Response to the MME 40 , if the verification is successfully completed.
- Step S 24 The MME 40 sends Path Switch Request Ack (Acknowledgement) to the MeNB 20 .
- the MME 40 should include an indicator to inform the MeNB 20 this is for DC.
- the MME 40 should not include any NCC value in this message since this is not for handover.
- Step S 25 The S-GW 50 and the P-GW 60 exchange the Modify Bearer Request/Response messages.
- Step S 26 The P-GW 60 starts Downlink data.
- the network entity (MME 40 or S-GW 50 ) should perform the verification as in Alternative 1.
- the procedure also uses Path Switch procedure as indicated in G 1 of NPL 1. Note that it is initiated by the SeNB 30 .
- the SeNB 30 sends Path Switch Request message to the MME 40 via the MeNB 20 , includes 1) DC configuration information (contains the configured DRB information, SeNB ID and SeNB IP address), and 2) indicator to show this is for DC. This is to inform that there is a new bearer from a SeNB has been configured not that UE has changed cell in handover procedure.
- Step S 33 When the MME 40 receives Path Switch Request, it determines whether this message is for DC or handover. If it is for DC, it will not compute NH and not increase the NCC value it keeps. The MME 40 then sends Modify
- Bearer Request message to the S-GW 50 includes the DC configuration information (contains the configured DRB information, SeNB ID and SeNB IP address) it received above.
- Step S 34 The S-GW 50 sends Modify Bearer Response to the MME 40 , if the verification is successfully completed.
- Steps S 35 -S 36 The MME 40 sends Path Switch Request Ack to the SeNB 30 via the MeNB 20 .
- the MME 40 should include an indicator to inform the MeNB 20 this is for DC.
- the MME 40 should not include any NCC value in this message since this is not for handover.
- Step S 37 The S-GW 50 and the P-GW 60 exchange the Modify Bearer Request/Response messages.
- Step S 38 The P-GW 60 starts Downlink data.
- the network entity (MME 40 or S-GW 50 ) should perform the verification as in Alternative 1.
- the MeNB 20 includes a sending unit 21 and a receiving unit 22 .
- the sending unit 21 sends, to the MME 40 , the E-RAB Modification Indication message as shown at step Sli in FIG. 3 , which includes the DC configuration information and/or the indicator.
- the receiving unit 22 receives, from the MME 40 , the E-RAB Modification Confirmation message as shown at step S 13 in FIG. 3 .
- these units 21 and 22 as well as other element(s) of the MeNB 20 can be implemented by at least hardware such as a transceiver which conducts communication with the SeNB 30 , the MME 40 and the S-GW 50 , a transceiver which conducts wireless communication with the UE 10 , as well as a controller like a CPU (Central Processing Unit) which control these transceivers to execute the processes shown in each of FIGS. 2 to 5 or processes equivalent thereto.
- the MeNB 20 can also be implemented by the combination of such hardware, and software (e.g., a program as stored in a memory and executed by the CPU).
- the MME 40 includes at least a receiving unit 41 and a sending unit 42 .
- the receiving unit 41 receives, from the MeNB 20 , the E-RAB Modification Indication message including the DC configuration information and/or the indicator.
- the sending unit 42 sends, to the S-GW 50 , the Modify Bearer Request message as shown at step S 22 in FIG. 4 , which includes the DC configuration information and/or the indicator.
- the sending unit 42 may be further configured to send the E-RAB Modification Confirmation message to the MeNB 20 .
- the MME 40 may further include a verifying unit 43 .
- the verifying unit 43 is triggered by the E-RAB Modification Indication message to verify the MeNB 20 and the SeNB 30 for the dual connectivity, as mentioned above.
- the Modify Bearer Request message may trigger the S-GW 50 to perform such verification.
- these units 41 to 43 as well as other element(s) of the MME 40 can be implemented by at least hardware such as a transceiver which conducts communication with the MeNB 20 and the S-GW 50 , as well as a controller like a CPU which control this transceiver to execute the processes shown in each of FIGS. 2 to 5 or processes equivalent thereto.
- the transceiver which conducts communication with the MeNB 20 and the S-GW 50
- a controller like a CPU which control this transceiver to execute the processes shown in each of FIGS. 2 to 5 or processes equivalent thereto.
- MME 40 can also be implemented by the combination of such hardware, and software (e.g., a program as stored in a memory and executed by the CPU).
- An MeNB that sends S-KeNB identity to both of an SeNB and a UE.
- a system that re-uses a Path Switch Request message to inform an EPC (MME and/or S-GW) about the SeNB/new bearer configuration.
- An S-GW that verifies whether an MeNB and an SeNB are authorized to carry the dual connectivity.
- Path Switch procedure is updated for DC that it contains:
- DC configuration information (contains the configured DRB information, SeNB ID and SeNB IP address);
- a system wherein an MME and an S-GW behavior in this procedure are updated for dual connectivity that:
- the MME should include an indicator to inform an MeNB the Path Switch Request Ack message is for DC;
- the MME should not include any NCC value in Path Switch Request Ack message since this is not for handover;
- the S-GW will not release the bearer in the MeNB as in handover procedure.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
- The present application is a continuation application of U.S. patent application Ser. No. 16/354,273 filed on Mar. 15, 2019, which is a continuation application of U.S. patent application Ser. No. 15/123,494 filed on Sep. 2, 2016, which issued as U.S. Pat. No. 10,375,614, which is a National Stage Entry of international application PCT/JP2015/001164, filed on Mar. 5, 2015, which claims the benefit of priority from Japanese Patent Application 2014-043929 filed on Mar. 6, 2014, the disclosures of all of which are incorporated in their entirety by reference herein.
- The present invention relates to an apparatus, a system and a method for DC (Dual Connectivity) or SCE (Small Cell Enhancement), and particularly to a technique to secure SeNB (Secondary eNB (evolved Node B)) Addition/Modification procedure in order to provide security in dual connectivity for the given UE (User Equipment).
- The SCE or DC was defined in 3GPP (3rd Generation Partnership Project) RAN (Radio Access Network) working groups, and it has initiated a study on security aspect and impact on the architecture 1A defined in
NPL 1. - For user plane data transmission between UE and SeNB, a new key for the confidentiality protection is needed. The RRC (Radio Resource Control) signaling terminates in the MeNB (Master eNB), thus it is responsible for the key management.
- In current architecture disclosed in
NPL 1, each UE is connected to one MeNB and one SeNB. There can be multiple bearers between SeNB and UE. The key for UE and SeNB user plane communication protection, denoted as S-KUPenc, is derived at SeNB and UE from a key S-KeNB shared between UE and SeNB. The S-KeNB is derived at MeNB and sent to SeNB. UE derives the same S-KeNB at its side. - NPL 1: 3GPP TR 36.842, “Study on Small Cell enhancements for E-UTRA and E-UTRAN; Higher layer aspects (Release 12)”, V12.0.0, 2013-12
- NPL 2: S3-140211, 3GPP TSG SA WG3 (Security) Meeting #74
- NPL 3: S3-140209, 3GPP TSG SA WG3 (Security) Meeting #74
- NPL 4: S3-140210, 3GPP TSG SA WG3 (Security) Meeting #74
- However, the inventors of this application have found that in the current solution, there are the following problems a) to c).
- a) The key S-KeNB is sent in SeNB “Addition/Modification Request” as disclosed in
NPLs 2 to 4. That is, the key S-KeNB is sent before SeNB is configured. Consider when a SeNB rejects the configuration (due to its capability or some other reason), or the configuration fails, the MeNB has to derive a new S-KeNB for the next SeNB it attempts to configure, meanwhile increases the counter. - b) There is no information of SeNB DRB (Data Radio Bearer) configuration at MeNB. This may cause improper key derivation and management, i.e., whether a new key S-KeNB should be derived when a new DRB is configured in SeNB.
- c) S-KeNB identity: SeNB may serve more than one UEs, and UE may connect to more than one SeNBs at different times or at same time (potential future architecture), giving a KSI (Key Set Identifier) can ensure UE and SeNB identify the key. Accordingly, an exemplary object of the present invention is to provide a solution for solving at least one of the above-mentioned problems.
- In order to achieve the above-mentioned object, each of an apparatus, a system and a method according to exemplary aspects of the present invention gives more details on:
- 1) Optimized SeNB Addition/Modification procedure based on security: key derivation and allocation; and
- 2) Secure SeNB Addition/Modification.
- According to first exemplary aspect of the present invention, there is provided a mobile communication system for dual connectivity. This mobile communication system includes: a first Node B; a second Node B; a mobility management apparatus; and a gateway. The first Node B sends a Modification Indication message including information on dual connectivity or information on the second Node B to the mobility management apparatus. The mobility management apparatus sends a Modify Bearer Request message including the information on dual connectivity or the information on the second Node B to the gateway.
- According to second exemplary aspect of the present invention, there is provided a communication method for dual connectivity having a first Node B and a second Node B. This communication method includes: sending a Modification Indication message including information on dual connectivity or information on the second Node B from the first Node B to a mobility management apparatus; and sending a Modify Bearer Request message including the information on dual connectivity or the information on the second Node B from the mobility management apparatus to a gateway.
- According to third exemplary aspect of the present invention, there is provided a base station used in dual connectivity. This base station includes: sending means for sending a Modification Indication message including information on dual connectivity or information on a second base station for dual connectivity to a mobility management apparatus; and receiving means for receiving a Modification Confirmation message from the mobility management apparatus.
- According to fourth exemplary aspect of the present invention, there is provided a mobility management apparatus used in dual connectivity. This mobility management apparatus includes: receiving means for receiving a
- Modification Indication message including information on dual connectivity or information on a second Node B from a first Node B; and sending means for sending a Modify Bearer Request message including the information on dual connectivity or the information on the second Node B to a gateway.
- According to the present invention, it is possible to solve at least one of the above-mentioned problems.
-
FIG. 1 is a block diagram showing a configuration example of a system according to an exemplary embodiment of the present invention. -
FIG. 2 is a sequence diagram showing an example of optimized SeNB Addition/Modification procedure in the system according to the exemplary embodiment. -
FIG. 3 is a sequence diagram showing a first example of bearer modification and SeNB verification at S-GW in the system according to the exemplary embodiment. -
FIG. 4 is a sequence diagram showing a second example of bearer modification and SeNB verification at S-GW in the system according to the exemplary embodiment. -
FIG. 5 is a sequence diagram showing a third example of bearer modification and SeNB verification at S-GW in the system according to the exemplary embodiment. -
FIG. 6 is a block diagram showing a configuration example of an MeNB according to the exemplary embodiment. -
FIG. 7 is a block diagram showing a configuration example of an MME according to the exemplary embodiment. - Hereinafter, an exemplary embodiment of an apparatus, a system and a method according to the present invention, will be described with the accompanying drawings.
-
FIG. 1 shows a configuration example of a system according to this exemplary embodiment, taking as an example the architecture where there is one SeNB per UE. - This system includes a UE 10, an MeNB 20, an SeNB 30, an MME (Mobility Management Entity) 40, and an S-GW (Serving Gateway) 50. Note that although the illustration is omitted in
FIG. 1 , the system also includes a P-GW (PDN (Public Data Network) Gateway) 60 as shown inFIGS. 4 to 6 . - As shown by solid lines in
FIG. 1 , there are provided several interfaces for C-Plane (Control-Plane) signaling. The UE 10 communicates with the MeNB 20 through a Uu interface. The MeNB 20 communicates with the SeNB 30 through an X2-C interface, and communicates with theMME 40 through an S1-MME interface. The S1-MME interface does not exist between the SeNB 30 and theMME 40. - Further, as shown by dotted lines in
FIG. 1 , there are also provided several interfaces for U-Plane (User-Plane) communication. Each of theMeNB 20 and theSeNB 30 communicates with the S-GW 50 through an S1-U interface. In this architecture, U-Plane traffic between theUE 10 and the S-GW 50 is transmitted through theMeNB 20 and theSeNB 30 in parallel for the purpose of offloading the MeNB 20 (in other words, for the purpose of offloading the backhaul S1-U interface between theMeNB 20 and the S-GW 50). Moreover, one or more bearers DRB1 to DRBn are established between theUE 10 and theSeNB 30. - Next, there will be described operation examples of this exemplary embodiment with reference to
FIGS. 2 to 5 . - To counter the problems a) to c) given above, this exemplary embodiment proposes that:
- S-KeNB is sent after step S4 “SeNB Addition/Modification Command” shown in
FIG. 2 . At step S4, theSeNB 30 informs that it can configure bearers for the givenUE 10. - The
MeNB 20 manages the DRB status. - The
MeNB 20 sends KSI to both of theUE 10 and theSeNB 30. -
FIG. 2 is based on the scenario disclosed inNPL 1 that there is only one MeNB and SeNB per UE. Note that processes at step S4, S6 and S7 are novel part in this invention. - New step/parameter in key derivation and allocation are as follows.
- Step S4: The
SeNB 30 sends to theMeNB 20 its capabilities, if it is different from standard. The capabilities of theSeNB 30 are included in SeNB Addition/Modification Command. - Step S6: The
MeNB 20 sends the S-KeNB and KSI after receiving the SeNB Addition/Modification Command. A new message for sending the S-KeNB and the KSI can be defined as Key Update. - The reason for performing this step is: reduce the counter value usage. If the
MeNB 20 sends the S-KeNB in the SeNB Addition/Modification Request at step S2, and theSeNB 30 does not have radio resource for theUE 10, theMeNB 20 will have to derive a new key and send to next SeNB till it finds the capable SeNB. - Step S7: the
MeNB 20 sends a KSI of S-KeNB to theUE 10 with the counter. This is to make sure that theUE 10 will use the same key as theSeNB 30. - After the SeNB Addition/Modification procedure, the “update of the UP path towards the EPC is performed” as described in
NPL 1. TheMeNB 20 should inform theMME 40 and the S-GW 50 about the new bearer configured at theSeNB 30, such that the S-GW 50 can start offloading the bearer(s) to theSeNB 30. - Before doing the offloading, the network entity (
MME 40 or S-GW 50) should perform verification that: 1) whether the request is coming from authenticated source (MeNB); and 2) whether SeNB is a valid eNB to which the traffic can be offload. The network entity (MME 40 or S-GW 50) can be pre-configured with information for the verification, or it can interact with another entity requesting for verification. - In order to offload the traffic to the
correct SeNB 30, the S-GW 50 needs to know that there is offload bearer configured in theSeNB 30 and traffic from theSeNB 30 to theUE 10, on top of SeNB ID (identity) & IP (Internet Protocol) address. Therefore, theSeNB 30 or theMeNB 20 should indicate the DC configuration information (contains the configured DRB information, SeNB ID and SeNB IP address) to the S-GW 50, such that the S-GW 50 knows that dual connectivity is being activated and a new bearer is added to theSeNB 30, and the S-GW 50 should not release the bearer in theMeNB 20. TheMME 40 should also be informed that dual connectivity is being activated, such that it can behave accordingly including forwarding the S-GW 50 the information and should not behave same as in handover procedure when Path Switch Request message is received from theMeNB 20. -
FIGS. 3 to 5 show alternatives 1 to 3 for the bearer modification and SeNB verification at the S-GW 50, respectively. - This alternative follows the current procedure in
NPL 1,FIG. 1-1 , Steps 11-13. The changes are given below: - At step S11 shown in
FIG. 3 , theMeNB 20 informs theMME 40 about newly configured SeNB and DRB, includes 1) DC configuration information (contains the configured DRB information, SeNB ID and SeNB IP address), and 2) indicator to show this is for DC. TheMME 40 can forward the S-GW 50 the information in Step S12. - Step S12: The
MME 40 sends bearer modification to the S-GW 50 indicating that this is a DC case together with information that the given DRB of a UE should be sent to theSeNB 30. - The network entity (
MME 40 or S-GW 50) verifies: 1) whether theMeNB 20 is allowed to configure theSeNB 30 for the givenUE 10; 2) whether theSeNB 30 is a valid network element; and 3) whether theSeNB 30 is authorized to provide dual connectivity. When the verification is done at theMME 40, it should be after theMME 40 receives Step Sli message. When the verification is done at the S-GW 50, it can happen after it receives the message from theMME 40. - The procedure uses Path Switch procedure as indicated in G1 of
NPL 1. Note that it is initiated by theMeNB 20. - At step S21 shown in
FIG. 4 , theMeNB 20 sends Path Switch Request message to theMME 40, includes 1) DC configuration information (contains the configured DRB information, SeNB ID and SeNB IP address), and 2) indicator to show this is for DC. This is to inform that there is a new bearer from a SeNB has been configured not that UE has changed cell in handover procedure. - Step S22: When the
MME 40 receives Path Switch Request, it determines whether this message is for DC or handover. If it is for DC, it will not compute NH (Next Hop) and not increase the NCC (Next-hop Chaining Counter) value it keeps. TheMME 40 then sends Modify Bearer Request message to the S-GW 50, includes the DC configuration information (contains the configured DRB information, SeNB ID and SeNB IP address) it received above. - Step S23: The S-
GW 50 sends Modify Bearer Response to theMME 40, if the verification is successfully completed. - Step S24: The
MME 40 sends Path Switch Request Ack (Acknowledgement) to theMeNB 20. TheMME 40 should include an indicator to inform theMeNB 20 this is for DC. TheMME 40 should not include any NCC value in this message since this is not for handover. - Step S25: The S-
GW 50 and the P-GW 60 exchange the Modify Bearer Request/Response messages. - Step S26: The P-
GW 60 starts Downlink data. - The network entity (
MME 40 or S-GW 50) should perform the verification as inAlternative 1. - The procedure also uses Path Switch procedure as indicated in G1 of
NPL 1. Note that it is initiated by theSeNB 30. - At steps S31-S32 shown in
FIG. 5 , theSeNB 30 sends Path Switch Request message to theMME 40 via theMeNB 20, includes 1) DC configuration information (contains the configured DRB information, SeNB ID and SeNB IP address), and 2) indicator to show this is for DC. This is to inform that there is a new bearer from a SeNB has been configured not that UE has changed cell in handover procedure. - Step S33: When the
MME 40 receives Path Switch Request, it determines whether this message is for DC or handover. If it is for DC, it will not compute NH and not increase the NCC value it keeps. TheMME 40 then sends Modify - Bearer Request message to the S-
GW 50, includes the DC configuration information (contains the configured DRB information, SeNB ID and SeNB IP address) it received above. - Step S34: The S-
GW 50 sends Modify Bearer Response to theMME 40, if the verification is successfully completed. - Steps S35-S36: The
MME 40 sends Path Switch Request Ack to theSeNB 30 via theMeNB 20. TheMME 40 should include an indicator to inform theMeNB 20 this is for DC. TheMME 40 should not include any NCC value in this message since this is not for handover. - Step S37: The S-
GW 50 and the P-GW 60 exchange the Modify Bearer Request/Response messages. - Step S38: The P-
GW 60 starts Downlink data. - The network entity (
MME 40 or S-GW 50) should perform the verification as inAlternative 1. - Next, there will be described configuration examples of the
MeNB 20 and theMME 40 with reference toFIGS. 6 and 7 , respectively. - As shown in
FIG. 6 , theMeNB 20 includes a sendingunit 21 and a receivingunit 22. The sendingunit 21 sends, to theMME 40, the E-RAB Modification Indication message as shown at step Sli inFIG. 3 , which includes the DC configuration information and/or the indicator. The receivingunit 22 receives, from theMME 40, the E-RAB Modification Confirmation message as shown at step S13 inFIG. 3 . Note that theseunits MeNB 20 can be implemented by at least hardware such as a transceiver which conducts communication with theSeNB 30, theMME 40 and the S-GW 50, a transceiver which conducts wireless communication with theUE 10, as well as a controller like a CPU (Central Processing Unit) which control these transceivers to execute the processes shown in each ofFIGS. 2 to 5 or processes equivalent thereto. TheMeNB 20 can also be implemented by the combination of such hardware, and software (e.g., a program as stored in a memory and executed by the CPU). - As shown in
FIG. 7 , theMME 40 includes at least a receivingunit 41 and a sendingunit 42. The receivingunit 41 receives, from theMeNB 20, the E-RAB Modification Indication message including the DC configuration information and/or the indicator. The sendingunit 42 sends, to the S-GW 50, the Modify Bearer Request message as shown at step S22 inFIG. 4 , which includes the DC configuration information and/or the indicator. The sendingunit 42 may be further configured to send the E-RAB Modification Confirmation message to theMeNB 20. TheMME 40 may further include a verifyingunit 43. The verifyingunit 43 is triggered by the E-RAB Modification Indication message to verify theMeNB 20 and theSeNB 30 for the dual connectivity, as mentioned above. Alternatively, the Modify Bearer Request message may trigger the S-GW 50 to perform such verification. Note that theseunits 41 to 43 as well as other element(s) of theMME 40 can be implemented by at least hardware such as a transceiver which conducts communication with theMeNB 20 and the S-GW 50, as well as a controller like a CPU which control this transceiver to execute the processes shown in each ofFIGS. 2 to 5 or processes equivalent thereto. The -
MME 40 can also be implemented by the combination of such hardware, and software (e.g., a program as stored in a memory and executed by the CPU). - Note that the present invention is not limited to the above-mentioned exemplary embodiment, and it is obvious that various modifications can be made by those of ordinary skill in the art based on the recitation of the claims.
- The whole or part of the exemplary embodiment disclosed above can be described as, but not limited to, the following supplementary notes.
- (Supplementary note 1)
- An MeNB that sends out a key S-KeNB after reception of “SeNB Addition/Modification Command”, thereby to:
- 1) prevent the S-KeNB being maliciously used by an SeNB that received but the bearer will not be configured for a given UE; and/or
- 2) prevent increase of counter value.
- (Supplementary note 2)
- An MeNB that sends S-KeNB identity to both of an SeNB and a UE.
- (Supplementary note 3)
- A system that re-uses a Path Switch Request message to inform an EPC (MME and/or S-GW) about the SeNB/new bearer configuration.
- (Supplementary note 4)
- An S-GW that verifies whether an MeNB and an SeNB are authorized to carry the dual connectivity.
- (Supplementary note 5)
- A system, wherein Path Switch procedure is updated for DC that it contains:
- 1) DC configuration information (contains the configured DRB information, SeNB ID and SeNB IP address); and
- 2) indicator to show this is for DC.
- (Supplementary note 6)
- A system, wherein an MME and an S-GW behavior in this procedure are updated for dual connectivity that:
- 1) the MME will not compute NH and not increase the NCC value it keeps;
- 2) the MME should include an indicator to inform an MeNB the Path Switch Request Ack message is for DC;
- 3) the MME should not include any NCC value in Path Switch Request Ack message since this is not for handover; and/or
- 4) the S-GW will not release the bearer in the MeNB as in handover procedure.
- This application is based upon and claims the benefit of priority from Japanese patent application No. 2014-043929 filed on Mar. 6, 2014, the disclosures of which is incorporated herein in its entirety by reference.
-
- 10 UE
- 20 MeNB
- 21, 42 SENDING UNIT
- 22, 41 RECEIVING UNIT
- 43 VERIFYING UNIT
- 30 SeNB
- 40 MME
- 50 S-GW
- 60 P-GW
Claims (6)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US17/587,228 US20220159537A1 (en) | 2014-03-06 | 2022-01-28 | Apparatus, system and method for dual connectivity |
Applications Claiming Priority (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2014-043929 | 2014-03-06 | ||
JP2014043929 | 2014-03-06 | ||
PCT/JP2015/001164 WO2015133144A1 (en) | 2014-03-06 | 2015-03-05 | Apparatus, system and method for small cell enhancement / dual connectivity |
US201615123494A | 2016-09-02 | 2016-09-02 | |
US16/354,273 US11246075B2 (en) | 2014-03-06 | 2019-03-15 | Apparatus, system and method for dual connectivity |
US17/587,228 US20220159537A1 (en) | 2014-03-06 | 2022-01-28 | Apparatus, system and method for dual connectivity |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/354,273 Continuation US11246075B2 (en) | 2014-03-06 | 2019-03-15 | Apparatus, system and method for dual connectivity |
Publications (1)
Publication Number | Publication Date |
---|---|
US20220159537A1 true US20220159537A1 (en) | 2022-05-19 |
Family
ID=52814162
Family Applications (5)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/123,494 Active US10375614B2 (en) | 2014-03-06 | 2015-03-05 | Apparatus, system and method for dual connectivity |
US16/354,273 Active US11246075B2 (en) | 2014-03-06 | 2019-03-15 | Apparatus, system and method for dual connectivity |
US16/413,643 Active US11284322B2 (en) | 2014-03-06 | 2019-05-16 | Apparatus, system and method for dual connectivity |
US16/540,636 Active US10856197B2 (en) | 2014-03-06 | 2019-08-14 | Apparatus, system and method for dual connectivity |
US17/587,228 Pending US20220159537A1 (en) | 2014-03-06 | 2022-01-28 | Apparatus, system and method for dual connectivity |
Family Applications Before (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/123,494 Active US10375614B2 (en) | 2014-03-06 | 2015-03-05 | Apparatus, system and method for dual connectivity |
US16/354,273 Active US11246075B2 (en) | 2014-03-06 | 2019-03-15 | Apparatus, system and method for dual connectivity |
US16/413,643 Active US11284322B2 (en) | 2014-03-06 | 2019-05-16 | Apparatus, system and method for dual connectivity |
US16/540,636 Active US10856197B2 (en) | 2014-03-06 | 2019-08-14 | Apparatus, system and method for dual connectivity |
Country Status (5)
Country | Link |
---|---|
US (5) | US10375614B2 (en) |
EP (1) | EP3114880A1 (en) |
JP (4) | JP2017502571A (en) |
KR (1) | KR101819409B1 (en) |
WO (1) | WO2015133144A1 (en) |
Families Citing this family (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104936173B (en) * | 2014-03-18 | 2022-02-25 | 华为技术有限公司 | Key generation method, main base station, auxiliary base station and user equipment |
GB2528913B (en) * | 2014-08-04 | 2017-03-01 | Samsung Electronics Co Ltd | Signalling in dual connectivity mobile communication networks |
PL2983439T3 (en) * | 2014-08-06 | 2021-05-31 | Alcatel Lucent | Special cell selection at secondary network nodes supporting dual connectivity |
US11178558B2 (en) * | 2015-05-22 | 2021-11-16 | Parallel Wireless, Inc. | Wireless backhaul resiliency |
US10849178B2 (en) * | 2016-09-22 | 2020-11-24 | Lg Electronics Inc. | Handling of conflict configuration in dual connectivity |
WO2018174654A1 (en) * | 2017-03-24 | 2018-09-27 | 주식회사 케이티 | Method for controlling mobility of terminal in heterogeneous network and apparatus therefor |
KR102174936B1 (en) | 2017-03-24 | 2020-11-05 | 주식회사 케이티 | Methods for controlling a mobility of UE for inter-Network and Apparatuses thereof |
CN109246765B (en) * | 2017-06-13 | 2023-12-29 | 中兴通讯股份有限公司 | User plane data session management method and device |
EP3930417B1 (en) | 2017-06-16 | 2023-08-09 | Samsung Electronics Co., Ltd. | Apparatus and method for managing connections in wireless communication system |
CN109246173B (en) * | 2017-06-16 | 2023-02-17 | 北京三星通信技术研究有限公司 | Session operation control method and device |
WO2018230982A1 (en) | 2017-06-16 | 2018-12-20 | Samsung Electronics Co., Ltd. | Apparatus and method for managing connections in wireless communication system |
WO2019063086A1 (en) * | 2017-09-28 | 2019-04-04 | Nokia Technologies Oy | Context transfer via last visited ran node |
CN109788577A (en) * | 2017-11-10 | 2019-05-21 | 华为技术有限公司 | Dual link communication means, device, base station and user face nodes |
JP7081613B2 (en) | 2017-12-13 | 2022-06-07 | 日本電気株式会社 | Wireless communication system, main base station, secondary base station, and wireless communication method |
KR102425582B1 (en) * | 2018-05-11 | 2022-07-26 | 삼성전자주식회사 | Apparatus and method for security protection in wireless communication system |
WO2020024296A1 (en) * | 2018-08-03 | 2020-02-06 | Oppo广东移动通信有限公司 | Base station switching method and apparatus, and network device |
KR102604283B1 (en) * | 2018-10-05 | 2023-11-20 | 삼성전자주식회사 | Apparatus and method for information protection |
CN112312585B (en) * | 2019-08-02 | 2023-10-20 | 华为技术有限公司 | Method for controlling access to user equipment, network system and related equipment |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR101931601B1 (en) | 2011-11-17 | 2019-03-13 | 삼성전자주식회사 | Method and apparatus for handling security key to authenticate with a mobile station in a radio communication system |
CN102892114B (en) * | 2012-09-28 | 2015-07-15 | 大唐移动通信设备有限公司 | Method and device for checking equipment validity |
EP2946491A4 (en) * | 2013-01-17 | 2016-09-14 | Intel Ip Corp | Method, apparatus and system for managing bearers in a wireless communication system |
CN110087272B (en) * | 2013-02-22 | 2021-10-08 | 三星电子株式会社 | Method and system for providing simultaneous connections between multiple E-node bs and user equipment |
KR102078866B1 (en) | 2013-08-09 | 2020-02-19 | 삼성전자주식회사 | SCHEME FOR Security key management for PDCP distribution in dual connectivity |
ES2890499T3 (en) | 2013-09-11 | 2022-01-20 | Samsung Electronics Co Ltd | Procedure and system to enable secure communication for inter-eNB transmission |
US10028212B2 (en) * | 2013-11-22 | 2018-07-17 | Qualcomm Incorporated | Techniques for provisioning configuration information based on cell characteristics |
WO2015108389A1 (en) * | 2014-01-17 | 2015-07-23 | Samsung Electronics Co., Ltd. | Dual connectivity mode of operation of a user equipment in a wireless communication network |
WO2015108291A1 (en) * | 2014-01-17 | 2015-07-23 | Lg Electronics Inc. | Bearer setup method and apparatus in wierless communication system supporting dual connectivity |
-
2015
- 2015-03-05 US US15/123,494 patent/US10375614B2/en active Active
- 2015-03-05 EP EP15712436.3A patent/EP3114880A1/en not_active Withdrawn
- 2015-03-05 KR KR1020167027649A patent/KR101819409B1/en active IP Right Grant
- 2015-03-05 WO PCT/JP2015/001164 patent/WO2015133144A1/en active Application Filing
- 2015-03-05 JP JP2016535196A patent/JP2017502571A/en active Pending
-
2017
- 2017-02-09 JP JP2017022334A patent/JP6399117B2/en active Active
-
2018
- 2018-09-04 JP JP2018165147A patent/JP2018207528A/en active Pending
-
2019
- 2019-03-15 US US16/354,273 patent/US11246075B2/en active Active
- 2019-05-16 US US16/413,643 patent/US11284322B2/en active Active
- 2019-08-14 US US16/540,636 patent/US10856197B2/en active Active
- 2019-11-06 JP JP2019201310A patent/JP2020022204A/en active Pending
-
2022
- 2022-01-28 US US17/587,228 patent/US20220159537A1/en active Pending
Also Published As
Publication number | Publication date |
---|---|
KR20160132052A (en) | 2016-11-16 |
US20190215748A1 (en) | 2019-07-11 |
JP2017085667A (en) | 2017-05-18 |
EP3114880A1 (en) | 2017-01-11 |
US11284322B2 (en) | 2022-03-22 |
WO2015133144A1 (en) | 2015-09-11 |
JP6399117B2 (en) | 2018-10-03 |
KR101819409B1 (en) | 2018-01-16 |
US20190281521A1 (en) | 2019-09-12 |
JP2017502571A (en) | 2017-01-19 |
JP2020022204A (en) | 2020-02-06 |
US11246075B2 (en) | 2022-02-08 |
JP2018207528A (en) | 2018-12-27 |
US20190373529A1 (en) | 2019-12-05 |
US10375614B2 (en) | 2019-08-06 |
US10856197B2 (en) | 2020-12-01 |
US20170078940A1 (en) | 2017-03-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20220159537A1 (en) | Apparatus, system and method for dual connectivity | |
US11711736B2 (en) | Apparatus, system and method for DC (dual connectivity) | |
US10869342B2 (en) | Radio bearer establishment method and base station | |
US10320754B2 (en) | Data transmission method and apparatus | |
WO2019062996A1 (en) | Method, apparatus, and system for security protection | |
US20170359719A1 (en) | Key generation method, device, and system | |
US20170245181A1 (en) | Apparatus for dual connectivity | |
KR20190082869A (en) | Method and system for establishing a connection between a remote UE and a communication network via a relayable user equipment (UE) | |
TW201828736A (en) | Base station and communication device can switch between two base stations | |
AU2018404377B2 (en) | Methods and computing device for splitting traffic across multiple accesses | |
WO2020056433A2 (en) | SECURE COMMUNICATION OF RADIO RESOURCE CONTROL (RRC) REQUEST OVER SIGNAL RADIO BEARER ZERO (SRBo) | |
JP2024026229A (en) | Improvement of security in sl unicast |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |