DE112018000199T5 - Registration management for new radio - Google Patents

Registration management for new radio

Info

Publication number
DE112018000199T5
DE112018000199T5 DE112018000199.7T DE112018000199T DE112018000199T5 DE 112018000199 T5 DE112018000199 T5 DE 112018000199T5 DE 112018000199 T DE112018000199 T DE 112018000199T DE 112018000199 T5 DE112018000199 T5 DE 112018000199T5
Authority
DE
Germany
Prior art keywords
ue
access point
network
registration
utran
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
Application number
DE112018000199.7T
Other languages
German (de)
Inventor
Robert Zaus
Ahmed Soliman
Raimund Wloka
Roland Gruber
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Intel IP Corp
Original Assignee
Intel IP Corp
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
Priority to US201762544281P priority Critical
Priority to US62/544,281 priority
Application filed by Intel IP Corp filed Critical Intel IP Corp
Priority to PCT/US2018/045534 priority patent/WO2019032532A1/en
Publication of DE112018000199T5 publication Critical patent/DE112018000199T5/en
Application status is Pending legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W60/00Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration

Abstract

Described herein are apparatus, systems, and methods for managing network connections within mobile networks having multiple radio access technologies. In embodiments, instructions may be stored on one or more computer-readable media, wherein the instructions in response to execution by user equipment (UE) may cause the UE to generate a registration request for transmission to a network to identify a registration-reject message from the network was received in response to the registration request, wherein the registration denial message includes an indication that the N1 mode is not allowed and the N1 mode cell capability is disabled based on the display. Other embodiments may be described and / or claimed.

Description

  • Related applications
  • The present application claims priority over the provisional one U.S. Patent Application No. 62 / 544,281 filed on August 11, 2017, entitled "HANDLING ROAMING RESTRICTIONS IN A MOBILE NETWORK", the entire disclosure of which is incorporated herein by reference.
  • Technical part
  • The present disclosure relates to the field of mobile networks. More particularly, the present disclosure relates to the management of network connections within multiple mobile radio access technology networks.
  • General state of the art
  • The description of the general state of the art provided herein is for the purpose of generally illustrating the context of the disclosure. Unless otherwise stated herein, the materials described in this section are not prior art to the claims of this application and will not become part of the prior art by inclusion in this section.
  • The introduction of new radio ( NO ) Technology (otherwise known as fifth generation ( 5G) or 5G NR technology) leads to changes in the mobile network architecture. These changes in mobile network architecture may lead mobile network architectures to support multiple radio access technologies, such as NR technology, packet kernel (e.g. EPC ) Technology, "Evolved Universal Mobile Telecommunication System Terrestrial Radio Access Network" - ( E-UTRAN ) Technology, "Global System for Mobile Communications Evolution Radio Access Network" - ( GERAN ) Technology and "Universal Mobile Telecommunication System Terrestrial Radio Access Network" ( UTRAN ). Management of user equipment ( UE Connections within these mobile network architectures to support multiple radio access technologies can introduce situations that did not need to be addressed in legacy mobile architectures network architectures.
  • Brief Description of the Drawings Embodiments will be readily understood by the following detailed description in conjunction with the accompanying drawings. To simplify this description, like reference numerals designate like structural elements. Embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings.
    • 1 illustrates an example mobile network scenario according to various embodiments.
    • 2 illustrates an example network architecture according to various embodiments.
    • 3 illustrates a message flow of an example registration request method according to various embodiments.
    • 4 illustrates a message flow of an example registration request method according to various embodiments.
    • 5 illustrates an exemplary connection method according to various embodiments.
    • 6 illustrates another exemplary connection method according to various embodiments.
    • 7 illustrates an architecture of a system of a network according to some embodiments.
    • 8th illustrates an architecture of a system of a network according to some embodiments.
    • 9 illustrates exemplary components of a device according to some embodiments.
    • 10 illustrates exemplary interfaces of baseband circuits according to some embodiments.
    • 11 FIG. 10 is an illustration of a control plane protocol stack according to some embodiments. FIG.
    • 12 FIG. 10 is an illustration of a user-level protocol stack according to some embodiments. FIG.
    • 13 illustrates components of a core network according to some embodiments.
    • 14 FIG. 10 is a block diagram illustrating components of a system according to some exemplary embodiments to support network health virtualization (NFV).
    • 15 FIGURE 10 is a block diagram illustrating components in accordance with some example embodiments that are capable of reading instructions from a machine-readable or computer-readable medium (eg, a non-transitory machine-readable storage medium) and executing any one or more of the methodologies discussed herein.
  • Detailed description
  • Described herein are apparatus, methods and storage media associated with the management of network connections within multiple mobile networks with radio access technologies. In embodiments, instructions may be stored on one or more computer-readable media, the instructions responsive to execution by user equipment ( UE ) the UE may cause to generate a registration request for transmission to a network, to identify a registration denial message received from the network in response to the registration request, the registration denial message including an indication that the N1 mode is not allowed, and the N1 Mode capability is disabled based on the display.
  • In the following detailed description, reference is made to the accompanying drawings, which form a part hereof, wherein like numerals indicate like parts throughout, and in which is shown by way of illustration embodiments which may be practiced. It is understood that other embodiments may be utilized and that structural or logical changes may be made without departing from the scope of the present disclosure. Therefore, the following detailed description is not to be understood in a limiting sense, and the scope of the embodiments is defined by the appended claims and their equivalents.
  • Aspects of the disclosure are disclosed in the accompanying description. Alternative embodiments of the present disclosure and equivalents thereof may be made without departing from the spirit or scope of the present invention. It should be noted that like elements disclosed below are indicated by like reference numerals in the drawings.
  • Various functions may be described as multiple discrete actions or functions in succession in a manner most helpful in understanding the claimed content. The order of the description, however, should not be construed as implying that the functions are necessarily order-dependent. In particular, these functions may not be executed in the order shown. Described functions may be performed in a different order than described in the embodiment. Various other functions may be performed and / or described functions may be omitted in further embodiments.
  • For purposes of the present disclosure, the phrase " A and or B " For ( A ) B ), or ( A and B ). For purposes of the present disclosure, the phrase " A . B and or C " For ( A ) B ) C ) A and B ) A and C ) B and C ) or ( A . B and C ).
  • The description may include the terms "in one embodiment" or "in embodiments", which may each refer to one or more of the same or different embodiments. Further, the terms "comprising," "including," "having," and the like are synonymous in use with respect to the embodiments of the present disclosure.
  • As used herein, the term "circuit" may refer to an "Application Specific Integrated Circuit" (US Pat. ASIC ), an electronic circuit, a processor (shared, dedicated or grouped) and / or a memory (shared, dedicated or grouped) each executing one or more software or firmware programs, a combinatorial logic circuit and / or other suitable components, Be part of or contain this part, which provide the described function.
  • With the advent of fifth generation network technology ( 5G) At the same time, mobile network configurations support user equipment ( UEs ) with different capabilities within a single mobile network. For example, it can be expected that a single mobile network can handle both evolved packet core ( EPC ) and core networks of the fifth generation (which 5G CN "Or" 5GC Supported ").
  • 1 illustrates an exemplary mobile network scenario 100 according to various embodiments. In particular, the mobile network scenario contains 100 a mobile network 102 containing one or more UEs 104 supported.
  • The mobile network 102 is an example of a standardized network deployment that uses both "Evolved Packet Core" ( EPC ) as well as 5GC protocols. The mobile network 102 contains a combined Home Subscriber Server ( HSS ) and Unified Data Management ( UDM ) 106 (which also as " UDM "Can be designated). The combined HSS and UDM 106 stores information regarding user subscriptions. For example, the combined stores HSS and UDM 106 Information about which radio access technology ( ADVICE ), which radio access network ( RAN ), which tracking area and / or which other network services may use a UE associated with a user based on a user subscription for the user. Accordingly, the mobile network 102 restrict access to network services for users with subscriptions to these network services.
  • The mobile network 102 also contains a EPC 108 , The EPC 108 is combined with the HSS and UDM 106 coupled. The EPC 108 supports the EPC protocol. Accordingly, that supports EPC 108 UEs that run with the EPC protocol. The EPC 108 can provide information regarding user subscriptions for UEs which has a radio resource control ( RRC ) Connection with the EPC 108 build up.
  • The mobile network 102 also contains a 5GC 110 , also known as "Next Generation Core" - ( NGC ) or "New Generation Core" ( NGC ). The 5GC 110 is combined with the HSS and UDM 106 coupled. The 5GC 110 supports that 5GC -Protocol. Accordingly, that supports 5GC 110 UEs that run with the EPC protocol. The 5GC 110 can provide information regarding user subscriptions for UEs retrieve an RRC connection with the 5GC 110 build up.
  • The mobile network 102 also includes one or more access points 112 , In the illustrated embodiment, a mobile network includes a first Evolved Universal Mobile Telecommunications System Terrestrial Radio Access Network (E-UTRAN) access point 112a , a second E-UTRAN access point 112b and a "New Radio" ( NO ) Access point 112c , In some embodiments, the first E-UTRAN access point comprises 112a and the second E-UTRAN access point 112b possibly developed knot bs ( eNBs ), and the NR access point 112c possibly includes a node B the next generation (gNB).
  • The first E-UTRAN access point 112a is with the EPC 108 connected. In particular, the first E-UTRAN access point 112a with the EPC 108 via an S1 interface 114 connected. The S1 -Interface 114 Provides communication between the first E-UTRAN access point 112a and the EPC 108 ready. Furthermore, the first E-UTRAN access point generates 112a an E-UTRAN cell. The first E-UTRAN access point 112a can send an indication in the E-UTRAN cell that the first E-UTRAN access point 112a with the EPC 108 connected and / or that the first E-UTRAN access point 112a supports the EPC protocol. UEs within the E-UTRAN cell may connect to the first E-UTRAN access point 112a connect, or with the EPC 108 communicate via the EPC protocol.
  • The second E-UTRAN access point 112b is with the EPC 108 and the 5GC 110 coupled. In particular, the second E-UTRAN access point 112b with the EPC 108 over a S1 interface 116 coupled and with the 5GC 110 via an N2 / N3 interface 118 coupled. The S1 -Interface 116 Provides communication between the second E-UTRAN access point 112b and the EPC 108 ready. Furthermore, the N2 / N3 interface provides 118 a communication between the second E-UTRAN access point 112b and the 5GC 110 ready. The second E-UTRAN 112b creates an E-UTRAN cell. The second E-UTRAN access point 112b can send an indication within the E-UTRAN cell that the second E-UTRAN access point 112b with the EPC 108 and the 5GC 110 connected and / or that the second E-UTRAN access point 112b the EPC protocol and the 5GC Protocol supported. UEs within the E-UTRAN cell can connect to the second E-UTRAN access point 112 connect and with the EPC 108 via the EPC protocol and / or with the 5GC 110 about the 5GC Protocol.
  • The NR access point 112c is with the 5GC 110 coupled. In particular, the NR access point 112c with the 5GC 110 via an N2 / N3 interface 120 coupled. The N2 / N3 -Interface 120 Provides communication between the NR access point 112c and the 5GC 110 ready. The NR access point 112c generates an NR cell. The NR access point 112c can radiate an indication in the NR cell that the NR access point 112c with the 5GC 110 connected and / or that the NR access point 112c the 5GC Protocol supported. UEs within the NR cell may associate with the NR access point 112c connect and with the 5GC 110 about the 5GC Protocol.
  • The second E-UTRAN access point 112b and the NR access point 112c are also coupled together. In particular, the second E-UTRAN access point 112b and the NR access point 112c in non-standalone ( NSA ), Double connectivity ( DC ) Configuration operated while the first E-UTRAN access point 112a in standalone ( SA ) Configuration is operated. The second E-UTRAN access point 112b and the NR access point 112c be coupled, what DC with the second E-UTRAN access point 112b and the NR access point 112c provides. When access points are operated in a DC configuration, a UE may be simultaneously connected to more than one access point running in the DC configuration. For example, the second E-UTRAN access point becomes 112b and the NR access point 112c in NSA , DC configuration configured. Accordingly, a UE may simultaneously with the second E-UTRAN access point 112b and the NR access point 112c be connected and data and signals via the second E-UTRAN access point 112b and the NR access point 112c send and receive at the same time. The second E-UTRAN access point 112b is about the S1 -Interface 116 with the EPC coupled and has the NR access point 112c in DC configuration over the interface 122 on. The second E-UTRAN access point 112b is also via the N2 / N3 interface 118 with the 5GC 110 coupled and has the NR access point 112c in DC configuration via the interface 124 on. The NR access point 112c is via the N2 / N3 interface 120 with the 5GC 110 coupled and has the second E-UTRAN access point 112b in DC configuration via the interface 126 on.
  • The UEs 104 the mobile network scenario 100 contain a first UE 104a , a second UE 104b , a third UE 104c , and a fourth UE 104d , Each of the UEs 104 has other abilities that affect which of the access points 112 and / or which of EPC 108 and 5GC 110 are connected. Furthermore, each of the UEs 104 perform various procedures, depending on which of EPC 108 and 5GC 110 the UE combines.
  • The first UE 104a only has one EPC Non-access stratum ( NAS ) Ability on. Accordingly, the first UE 104a only with the EPC 108 connect. Furthermore, the first one supports UE 104a Not DC and / or is configured in SA configuration. Therefore, the first UE 104a only with the EPC 108 connect. For example, the first one UE 104a with the EPC 108 over the second E-UTRAN access point 112b connected in the illustrated embodiment, as by line 128 illustrated. The first UE 104a uses EPC NAS procedures and EPC protocols for communicating with the EPC 108 ,
  • The second UE 104b only has one EPC NAS capability. Accordingly, the second UE 104b only with the EPC 108 connect. Furthermore, the second one supports UE 104b DC and / or is configured in DC configuration. Therefore, the second UE 104b only with the EPC 108 connect, but they also with the EPC 108 over one or more access points 112 can connect. For example, the second one UE 104b with the EPC 108 in the illustrated embodiment, via the first E-UTRAN access point 112a connected as by line 130 illustrated, and via the second E-UTRAN access point 112b as by line 132 illustrated. The second UE 104b uses EPC NAS procedures and EPC protocols for communicating with the EPC 108 , Due to the double connectivity, the second UE 104b with the EPC 108 simultaneously via the first E-UTRAN access point 112a and the second E-UTRAN access point 112b communicate.
  • The third UE 104c has one EPC NAS capability and one 5GC NAS capability on. Therefore, the third can UE 104c with the EPC 108 or the 5GC 110 connect. The third UE 104c tries to connect to the highest quality network available, which connects to the 5GC 110 in the illustrated embodiment. The third UE 104c can via the second E-UTRAN access point 112b or the NR access point 112c With 5GC 110 be connected. The third UE 104c is with the 5GC 110 via the second E-UTRAN access point 112b connected, as in the illustrated embodiment by line 134 illustrated. The third UE 104c uses 5GC NAS method and 5GC Protocols for communication with the 5GC 110 ,
  • The fourth UE 104d has one EPC NAS capability and one 5GC NAS capability on. Therefore, the fourth can UE 104d with the EPC 108 or the 5GC 110 connect. The fourth UE 104d tries to connect to the network providing the best possible service, which in the illustrated embodiment connects to the 5GC 110 would include. The fourth UE 104d can via the second E-UTRAN access point 112b or the NR access point 112c With 5GC 110 be connected. The fourth UE 104d is with the 5GC 110 via the NR access point 112c connected, as in the illustrated embodiment by line 136 illustrated. The fourth UE 104d uses 5GC NAS method and 5GC Protocols for communication with the 5GC 110 ,
  • While the UEs 104 in the illustrated embodiment, the arrangement of the mobile network 102 with the second E-UTRAN 112b represent a compilation. In particular, this is what the EPC 108 and the 5GC 110 on the combined HSS and UDM 106 too, to determine if one UE with the EPC 108 and the 5GC based on user data with the UE are allowed to associate. The EPC 108 and the 5GC 110 use the user data that comes with the UE associated to a user subscription for a user of UE to determine. The user subscription can prevent the UE with the EPC 108 and / or the 5GC 110 connects and / or registers there. In instances where the subscription prevents the UE with the EPC 108 and / or the 5GC 110 connects and / or registers there, the access point (such as the access points 112 ) the UE has used to try to deal with the EPC 108 and / or the 5GC 110 to connect and / or register a registration reject message to the UE. Using some legacy logs, the registry revocation message indicates that the use of a particular type of access point is due to the UE not allowed. For example, the registry reject message indicates that E-UTRAN is not allowed or NO based on the type of access point that the UE used is not allowed. Using other legacy logs, the registry revocation message indicates that the specific access point is being used by the UE not allowed. For example, the registry reject message would indicate that the UE may not use a tracking area, where the tracking area corresponds to the specific access point.
  • Considering the arrangement of the mobile network scenario 100 the complication can arise from that third UE 104c tries to connect with the mobile network 102 connect to. In particular, the third could UE 104c try to deal with that 5GC 110 via the second E-UTRAN access point 112b connect to. If that 5GC 110 based on the subscription information that comes with the third UE 104c associated in the combined HSS and UDM 106 are stored, determines that the third UE 104c was not allowed to join the 5GC 110 to register that would 5GC 110 the second E-UTRAN access point 112b cause a registry reject message to the third UE 104c to send.
  • In instances where legacy logs have a registry reject message that indicates that the use of a particular type of access point is not through the third UE 104c is allowed, the second E-UTRAN access point 112b submit a registry reject message indicating that the third one UE 104c was not allowed to connect to E-UTRAN access points. In response to receiving the registration denial message, the third would be UE 104c avoid trying to connect via E-UTRAN access points, including the first E-UTRAN access point 112a and the second E-UTRAN access point 112b , This is for the mobile network 102 not desirable because the third UE 104c This would prevent the subscription restriction from interfering with the 5GC 110 to connect, and would be prevented from dealing with the EPC 108 because only E-UTRAN access points have connectivity to the EPC 108 provide.
  • In instances where legacy logs have a registry disapproval message indicating that use of the specific access point is not through the third UE 104c is allowed, the second E-UTRAN access point 112b submit a registry reject message indicating that the third one UE 104c not with the second one E-UTRAN 112b was allowed to connect. In response to receiving the registration denial message, the third would be UE 104c Avoid trying to connect via the second E-UTRAN access point 112b connect to. This is for the mobile network 102 not desirable because the second E-UTRAN access point 112b still a connectivity with the EPC 108 for the third UE 104c which attempts to connect to another access point by the proximity of other access points of the third UE 104c may not be available. Furthermore, the third UE 104c keep trying with the 5GC 110 through other access points because the registration denial message indicates that only a particular access point was not allowed.
  • The mobile network 102 Here, a protocol is implemented in which the registration revocation message indicates that the N1 Mode is not allowed, with the N1 Mode the connection with the 5GC 110 about the N1 Interface included, indicated by line 134 and line 136 , In particular, the third could UE 104c a connection and / or registration with the 5GC 110 via the second E-UTRAN access point 112b Request. The 5GC 110 can notice that the third UE 104c based on subscription information associated with the third UE 104c connected in the combined HSS and UDM 106 are not saved with that 5GC 110 connect and / or register there. In response to that 5GC 110 determines that the third UE 104c not with the 5GC 110 connect and / or register there, that causes 5GC 110 the second E-UTRAN access point 112b to submit the refusal denial message indicating that the N1 Mode for the third UE 104c is not allowed. The third UE 104c deactivates his N1 Mode radio based on the display. With disabled N1 Mode radio tries the third one UE 104c to deal with the access points 112 to connect, which indicate that the access point with the EPC 108 connected and / or support EPC support protocol leaves one N1 Ability display from the registration attempts, or a combination thereof. Accordingly, the third UE 104c still the first E-UTRAN access point 112a and the second E-UTRAN access point 112b use to deal with the EPC 108 connect to. In other embodiments, the registration denial message may indicate that 5GC is not allowed.
  • In some embodiments, the third UE 104c a "Public Land Mobile" (PLMN) identity ( ID ) or a tracking area ID ( TAI ) associated with the registration denial message. The PLMN-ID and TAI can be used with the access point (such as the access points 112 ) or the cell provided by the access point. In embodiments in which the third UE 104c identifies the PLMN ID, stores the third UE 104c the PLMN ID in a list of PLMNs in which the N1 Mode is not allowed. In embodiments in which the third UE 104c the TAI identifies stores the third one UE 104c the TAI in a list of TAIs in which the N1 Mode is not allowed. For example, the one UE NAS the third UE 104c the PLMN ID or the TAI in the list of PLMNs in which the N1 Mode is not allowed, or the list of TAIs store in which N1 not allowed. The list of PLMNs or the list of TAIs can in the third UE 104c or a Universal Subscriber Identity Module ( USIM ) get saved. The list can be sent internally to an access stratum ( AS ) the third UE 104c forwarded so that the AS can use the list, for example, to determine if a cell (either an E-UTRAN cell or an NR cell) is suitable for camping.
  • Furthermore, in some embodiments, the third UE 104c the IDs in the list of PLMNs delete in which the N1 Mode is not allowed, or the IDs in the list of TAIs in which the N1 Mode is not allowed. For example, the IDs be deleted in one of the lists when the UE is switched off or a time interval has expired. The time interval can be fixed, chosen at random from certain intervals (such as between 12 Hours and 24 Hours), or through the mobile network 102 be signaled.
  • 2 illustrates an exemplary network architecture 200 according to various embodiments. The network architecture 200 supports NO (otherwise referred to as a 5G system ( 5GS ), EPC / E-UTRAN and the Global Mobile Communication / Enhanced Data Rate System for the Global System for Mobile Communications Evolution Radio Access Network (GERAN) / Universal Mobile Telecommunications System Terrestrial Radio Access Network (UTRAN). In particular, the network architecture illustrates 200 an embodiment of a non-roaming architecture for collaboration between NR and EPC / E-UTRAN and between EPC / E-UTRAN and GERAN / UTRAN.
  • The network architecture 200 contains an HSS 202 , Of the HSS 202 supports the sections GERAN / UTRAN and EPC / E-UTRAN of the network architecture 200 , The HSS 202 may be prior to the introduction of NR into the network architecture 200 with GERAN / UTRAN and EPC / E-UTRAN sections of the network architecture 200 be implemented. Of the HSS 202 stores user subscription information for the GERAN / UTRAN and EPC / E-UTRAN sections of the network architecture 200 , The HSS 202 can store user subscription information prior to the implementation of NO generated and / or stored in the network. Furthermore, the HSS 202 Store user subscription information for the GERAN / UTRAN and EPC / E-UTRAN sections of the network that were created and / or saved after the NR network was implemented.
  • The network architecture 200 contains a first packet data network ( PDN ) 204 , The first PDN 204 supports the sections GERAN / UTRAN and EPC / E-UTRAN of the network architecture 200 , The first PDN 204 can provide connectivity to the GERAN / UTRAN and EPC / E-UTRAN sections of the network architecture 200 with other pact data networks, such as on the Internet and session initiation protocol ( SIP ) based internet protocol ( IP ) Multimedia Subsystems ( IMS ).
  • The network architecture 200 contains one PDN Gateway ( PGW ) 206 , Of the PGW 206 is with the first one PDN 204 coupled. Of the PGW 206 acts as an interface between the first PDN 204 and the GERAN / UTRAN and EPC / E-UTRAN sections of the network architecture 200 , Of the PGW 206 can make requests for connection with the first one PDN 204 from UEs receive and assign IP addresses to the UEs. In particular, the PGW 206 Inquiries for the connection with the first PDN 204 received from UEs included in the GERAN / UTRAN and / or EPC / E UTRAN to run.
  • The network architecture 200 contains a server gateway ( SGW ) 208 , Of the SGW 208 is with the first one PGW 206 coupled. Of the SGW 208 serves as an interface with the first PGW 206 , Of the SGW 208 manages packet routing for the first one PGW 206 , Furthermore manages the SGW 208 the transfer under access points of the GERAN / UTRAN and / or EPC / E-UTRAN sections of the network architecture 200 ,
  • The network architecture 200 contains a combined UDM and HSS 210 , The combined UDM and HSS 210 supports the EPC / E-UTRAN and NR sections of the network architecture 200 , The combined UDM and HSS can with the NR section of the network architecture 200 be implemented after the implementation of the GERAN / UTRAN and / or the EPC / E-UTRAN sections of the network architecture 200 may have occurred. The combined UDM and HSS 210 stores user subscription information for the EPC / E-UTRAN sections of the network architecture 200 , Through the later implementation of the combined UDM and HSS 210 For example, a network operator can initially do the combined UDM and HSS 210 with user subscription information for users who combined the NR over the one UDM and HSS 210 subscribe (ie 5GS to be able to use). Accordingly missing the combined UDM and HSS 210 possibly user subscription information for users who are on GERAN / UTRAN and EPC / E-UTRAN but can not access NO have subscribed.
  • The network architecture 200 contains a second PDN 212 , The second PDN 212 can the GERAN / UTRAN . EPC / E-UTRAN and NR sections of the network architecture 200 support. The second PDN 212 can connectivity for the GERAN / UTRAN . EPC / E-UTRAN and NR sections of the network architecture 200 with other packet data networks, such as the Internet and SIP based IMS ,
  • The network architecture 200 Contains a session management function ( SMF ) / Control- PGW ( PGW-C ) 214 (which as a " SMF "Can be designated). Of the SMF / PGW-C 214 is combined with the UDM and HSS 210 coupled. Of the SMF / PGW-C 214 can make requests for connection with the second PDN 212 from UEs receive and the UEs Assign IP addresses. In particular, the SMF 214 Inquiries for connection with the second PDN 212 UEs received in the GERAN / UTRAN, EPC / E-UTRAN and / or NR sections of the network architecture 200 to run.
  • The network architecture 200 Contains a user-level function ( UPF ) / a user-level PGW ( PGW-U ) 216 (which as a " UPF "Can be designated). Of the UPF / PGW-U 216 is with the second PDN 212 and the SMF / PGW-C 214 coupled. Of the UPF / PGW-U 216 manages packet routing for the second PDN 212 , Furthermore, the UPF / PGW-U 216 the transfer under the access points of the GERAN / UTRAN, EPC / E-UTRAN and NR sections of the network architecture 200 ,
  • The network architecture 200 contains a "Serving General Packet Radio Service Support Node" ( SGSN ) 218 , Of the SGSN 218 is part of the GERAN / UTRAN section of the network architecture 200 and supports the GERAN / UTRAN service. Of the SGSN 218 is with the HSS 202 and the SGW 208 coupled. Of the SGSN 218 may be packet switched data in the GERAN / UTRAN such as mobility management and authentication of users of the GERAN / UTRAN.
  • The network architecture 200 contains a GERAN / UTRAN access point 220 , The GERAN / UTRAN access point 220 is with the SGSN 218 coupled. The GERAN / UTRAN access point 220 provides access to the GERAN / UTRAN advised for UEs. The GERAN / UTRAN access point 220 can be a node B include.
  • The network architecture 200 contains a Mobility Management Entity (MME) 222 , The MME 222 is part of the EPC / E-UTRAN section of the network architecture 200 and supports the EPC / E-UTRAN service. The MME 222 is with the HSS 202 , the combined UDM and HSS 210 , and the SGW 208 coupled. The MME 222 , of the SGW 208 , of the PGW 206 and / or the HSS 202 can be part of one EPC be like (like the EPC 108 ( 1 )). The MME 222 can packet switching data within the EPC / E-UTRAN such as mobility management and authentication of users of the EPC / E-UTRAN ,
  • The network architecture 200 contains an E-UTRAN access point 224 , The E UTRAN access 224 is with the MME 222 and the SGW 208 coupled. The E-UTRAN access point 224 provides access for the EPC / E-UTRAN ready for UEs. The E-UTRAN access point 224 may include an eNB.
  • The network architecture 200 contains an access and a mobility management function ( AMF ) 226 , The AMF 226 is part of the NR section of the network architecture 200 and supports the NR service. The AMF 226 is combined with the UDM and HSS 210 and the SMF / PGW-C 214 coupled. The AMF 226 , of the UPF / PGW-U 216 , the SMF / PGW-C 214 and / or the combined UDM and HSS 210 can be part of one 5GC be like (like 5GC 110 ( 1 )). The AMF 226 can perform registration management, connection management, mobility management, and access authentication and authorization for NR.
  • The network architecture 200 contains an NR access point 228 (who as " 5G RAN Access point "can be designated). The NR access point 228 is with the UPF / PGW-U 216 and the AMF 226 coupled. The NR access point 228 provides access to the NR for UEs. The NR access point 228 can include a gNB.
  • The network architecture 200 contains one or more UEs 230 , The network architecture 200 contains a first UE 230a , a second UE 230b and a third UE 230c in the illustrated embodiment. The first UE 230a is with the GERAN / UTRAN access point 220 connected and on the GERAN / UTRAN accessible illustrated. The second UE 230b is with the E-UTRAN access point 224 connected and on the EPC / E-UTRAN accessible illustrated. The third UE 230c is with the NR access point 228 and on the NO accessible illustrated. While the UEs 230 with certain access points and RANs are illustrated, it should be understood that the UEs 230 the connections with other access points and others RANs can change. For example, the first UE 230a connected to the GERAN / UTRAN access point 220 connected to the E-UTRAN access point 224 and / or the NR access point 228 or for access to EPC / E-UTRAN and or NO go over at different times.
  • Interfaces between the SGSN 218 and the MME 222 , and between the MME 222 and the AMF 226 , the handovers of UEs 230 from one of the networks to another of the networks. For example, an interface 232 (as S3 -Interface) between the SGSN 218 and the MME 222 the transfer of the UEs between the GERAN / UTRAN and the EPC / E-UTRAN simplify. Furthermore, an interface 234 (which may be referred to as an N26 interface) handing over the UEs between the EPC / E-UTRAN and the NO simplify. The interfaces may include the transmission of UE context and PDN connections between the SGSN 218 and the MME 222 , and between the MME 222 and the AMF 226 support. The Interfaces may provide for easier transmission of the UE context and the PDN connections, with less interruptions between them SGSN 218 and the MME 222 , and between the MME 222 and the AMF 226 as if the interfaces were not present. The transmission of the UE context via the interfaces can be faster than a reconnection process for establishing new PDN connections. Furthermore, can UEs that use the inter-network interfaces to associate an IP address associated with a PDN connection when transmitting between the networks, providing seamless service continuity for UEs and / or applications running on the UE using PDN connections. However, it should be noted that an interface that directly the SGSN 218 and the AMF 226 couples, does not exist.
  • A default configuration of a UE can contain that UE Attempts to connect to the network configuration, providing the best service possible, connecting with NO about the AMF 226 in the network architecture 200 includes. However, this can in some cases with the network architecture 200 not optimal. For example, transmitting the connection would be the first UE 230a of the SGSN 218 on the AMF 226 not optimal. In particular, because there is no interface that deals directly with the SGSN 218 and the AMF 226 It may not be possible to associate UE context with the first one UE 230a is associated, between the SGSN 218 and the AMF 226 transferred to. Due to the last transmission of the UE context, the first UE 230a a new connection method with the AMF 226 and rebuild the PDN connections. Furthermore, the first UE 230a be assigned to a new IP address while being between the SGSN 218 and the AMF 226 switches, depending on the network configuration of the GERAN / UTRAN and / or the NO , Performing the new connection procedure, rebuilding the PDN connections, and / or assigning the new IP address can lead to a service interruption that would not be desirable. Accordingly, it would be preferable that the first UE 230a the connection transfer to the MME 222 if the service interruption is the correct operation of the first UE 230a would disturb, so the first UE 230a the interface 232 use and service interruption is avoided or at least restricted.
  • In some embodiments, an operator of a network may decide to use PDN connections over the network GERAN / UTRAN have been activated over the PGW 206 and a PDN connection over the UPF / PGW-U 216 build up when connecting via the E-UTRAN access point 224 is enabled, and the user who is using the UE associated with a subscription to the NR owns. The operator can implement this because the resources of the UPF / PGW-U 216 are restricted, and therefore may want the resources for UEs reserve and be able to and have permission NO to use. For example, the UPF / PGW-U 216 have limited memory, a number of IP addresses, user-level bandwidth, and / or signaling processing power. Each of the PGW 206 and everyone UPF / PGW-U 216 are assigned their own range of IP addresses, so it may not be possible to keep the IP address if the endpoint of the PDN connection is between the IP addresses PGW 206 and the UPF / PGW-U 216 is moved.
  • Trying to connect to the NO also may not be optimal for instances when subscription information is for a user who is using a UE is associated with trying to search with the AMF 226 to connect, not on the combined UDM and HSS 210 get saved. This can happen if a network operator combined that UDM and HSS 210 has not yet updated with subscription information for the user. In particular, the tried AMF 226 , in response to a completion message for an RRC connection establishment from the UE Get subscription information that comes with a UE from the combined UDM and HSS 210 are associated. In the case where the combined UDM and HSS 210 no saved subscription information for the UE has, is the AMF 226 unable to get the subscription information from the combined UDM and HSS 210 retrieve. Furthermore, the AMF 226 no direct interface between the AMF 226 and the HSS 202 is not able to retrieve subscription data. For such a user for whom no subscription information on the combined UDM and HSS 210 stored an RRC connection setup completion message could be from the UE Associated with the user UDM and HSS 210 which could not find the subscription information and could respond with a cause of error indicating that the user does not have a subscription to NR services. The AMF could a registration reject message with an appropriate mobility management ( MM Cause cause that prevents the UE tried again at the AMF 226 to register after the cause of failure of the combined UDM and HSS 210 was received.
  • To treat such cases in which the attempt of connection with the NO is not optimal, the UE be configured to register at the EPC / E UTRAN about the registration on NO to prioritize. For example, for a UE , the GERAN . UTRAN or GERAN and UTRAN equally beside NO supported, the UE Priorities between the registration on EPC / E-UTRAN and the registration on NO based on that change that UE receives a denial cause indicating that NO is not allowed when trying to network in a network NO to register. For example, if a UE on E-UTRAN campt and the E-UTRAN access point 224 of the UE indicates that the E-UTRAN access point 224 Connections with a EPC (as EPC 108 ( 1 )) and one 5GC (like that 5GC 110 ( 1 )), the UE may register with the EPC to prefer. Furthermore, the draws UE , if the UE performs a reselection of the cell and determines that E-UTRAN cells only one 5GC Connection and other cells connect to one EPC offer reselection to the cell before that connects to the EPC offering.
  • 3 illustrates a message flow of an exemplary registration request process 300 according to various embodiments. In particular, illustrated 3 the signal flow under one UE 302 (like the UEs 104 ( 1 ) and / or the UEs 230 ( 2 )), an E-UTRAN access point 304 (such as the second E-UTRAN access point 112b ( 1 ) and / or the E-UTRAN access point 224 ( 2 )), one AMF 306 (like the AMF 226 ( 2 )) and one MME 308 (like the MME 222 ( 2 )). The E-UTRAN access point 304 In the illustrated embodiment, connections with the AMF 306 and the MME 308 provide. The exemplary registration request process 300 illustrates an unsuccessful registration with a 5GC ,
  • The UE 302 initially camps on an E-UTRAN cell and listens to the system information broadcast from the E-UTRAN access point 304 , In particular, the E-UTRAN access point generates and radiates 304 a system information signal 310 out through the UE 302 Will be received. The system information signal 310 indicates that the E-UTRAN access point 304 a connection with 5GC and EPC offering. In particular, the system information signal 310 " N1 / 5GC supported "to indicate that the E-UTRAN access point 304 a connection with 5GC offers, and " S1 / EPC supports "to indicate that the E-UTRAN access point 304 a connection with EPC offering. In other embodiments, the display of EPC be given implicitly, such as by the UE 302 assumes that EPC supported, and the E-UTRAN access point 304 only expressly indicates if EPC not supported.
  • The UE 302 builds an RRC connection with the E-UTRAN access point 304 on. In particular, the UE generates and transmits 302 an RRC connection request message 312 to the E-UTRAN access point 304 and the E-UTRAN access point 304 responds with an RRC connection setup message 314 , The UE 302 generates and transmits an RRC connection setup completion message 316 to the E-UTRAN access point 304 in response to the identification of the RRC connection setup message 314 , The RRC connection setup completion message 316 contains an ad that the UE 302 the N1 Interface, for example by including "N1 capability" in the RRC connection setup completion message 316 , It also contains the RRC connection setup completion message 316 the 5GC -NAS message "Registration request."
  • The E-UTRAN access point 304 identifies the RRC connection setup completion message 316 with the 5GC -NAS message "Registration request." The E-UTRAN access point 304 determined from the indication that the UE 302 the N1 Interface in the RRC connection setup completion message 316 is included that the UE 302 a connection with a 5GC wants to build up (such as the 5GC 110 ( 1 )). The E-UTRAN access point 304 choose the AMF 306 and generates and transmits an N2AP start UE message 318 to the AMF 306 , The N2AP initial UE message 318 contains the 5GC NAS "Registration Request."
  • The AMF 306 gets the subscription information that comes with the UE 302 are associated, from a combined UDM and HSS (like the combined UDM and HSS 106 ( 1 ) and / or the combined UDM and HSS 210 ( 2 )). The AMF 306 determines that the UE 302 does not have a subscription to NR based on the subscription information. Therefore, the decides AMF 306 to reject the registration request. The AMF 306 generates and transmits an N2AP downlink NAS transport message 320 to the E-UTRAN access point 304 , The N2AP Downlink NAS Transport Message 320 contains an MM reason that indicates that the N1 Mode is not allowed based on that AMF 306 decides to decline the registration request.
  • The E-UTRAN access point 304 identifies the N2AP downlink NAS transport message 320 by the AMF 306 Will be received. The E-UTRAN access point 304 directs the registration deny from the N2AP downlink NAS transport message 320 to the UE 302 in a RRC downlink information transfer message 322 further. The registry rejection contains the MM reason that indicates that N1 not allowed. In some embodiments, the E-UTRAN access point determines 304 by 5GC by routing the "registration request" to the AMF 306 and Identification of Registration Deny in the N2AP Downlink NAS transport message 320 that the registration request is not accepted.
  • A N2 Connection and the RRC connection will be after transmission of the RRC downlink information transmission message 322 Approved. The release of the N2 Connection and the RRC connection may include the execution of a release procedure. The AMF 306 directs the release process by creating and transmitting an N2AP context release command message 324 to the E-UTRAN access point 304 one. The E-UTRAN access point 304 identifies the N2AP context release command message 324 and generates and transmits an RRC connection release message 326 in response to the identification of the N2AP context release message 324 , Furthermore, the E-UTRAN access point generates and transmits 304 an N2AP UE context release completion message 328 to the AMF 306 to complete the release process.
  • The UE 302 deactivates the N1 Mode via a deactivation procedure 330 in the RRC downlink information transmission message 322 , in response to the identification of the ad that the N1 Mode is not allowed. In some embodiments, the UE 302 the N1 Mode upon receiving the registration deny with the MM cause that the N1 Mode is not allowed, disable. If the N1 Mode is off, the remains UE in the current PLMN and do not try to deal with the AMF 306 to connect (ie do not try to 5GC Initiate NAS procedure). Furthermore, contains the UE 302 none N1 Capability display in RRC messages when requesting the establishment or rebuilding of an RRC connection during the N1 Mode is disabled.
  • Furthermore, this informs NAS the AS that the use of N1 in the PLMN which is an E-UTRAN access point 304 corresponds, is not allowed. Accordingly considered that AS E-UTRAN cells for which the E-UTRAN access point 304 indicates that he is only connecting with one 5GC can offer as not "suitable" for camping. Furthermore, this shows AS , if that AS decides to camp on a cell that connects to a cell 5GC and a connection with one EPC offers that NAS just the opportunity to connect with one EPC connect to.
  • In response to the identification of the ad that the N1 Mode is not allowed in the RRC downlink information transfer message 322 , the UE can 302 a registration procedure with the EPC (such as a connection procedure or tracking area update ( DEW ) Procedure). In particular, the UE 302 initiate the registration process as the E-UTRAN access point 304 a connection with the EPC via the MME 308 offering. In embodiments in which the E-UTRAN access point 304 no connection with the EPC offers, leads the UE 302 Do a cell selection to try to choose a different cell (potentially on a different cell) ADVICE can be located).
  • The UE 302 initiates the registration process by generating and transmitting another RRC connection request message 332 to the E-UTRAN access point 304 , The UE 302 creates and transmits the RRC connection request message 332 in an attempt to join in EPC about the MME 308 to register. The E-UTRAN access point 304 identifies the RRC connection request message 332 , and generates and transmits an RRC connection setup message 334 in response to the identification of the RRC connection request message 332 , The UE 302 identifies the RRC connection setup message 334 , In response to the identification of the RRC connection setup message 334 generates and transmits the UE 302 an RRC connection setup completion message 336 to the E-UTRAN access point 304 , The RRC connection setup completion message 336 contains an EPC NAS completion request for registration with the EPC about the MME 308 , The N1 -Assistibility indicator will be out of the RRC connection setup completion message 336 omitted. The N1 Ability display can be based on disabling the N1 Ability by the UE 302 be omitted during the deactivation process 330 occured. In other embodiments, where the UE is already using the EPC is registered, the RRC connection setup completion message 336 include an EPC NAS TAU request message.
  • The E-UTRAN access point 304 may be the RRC connection setup completion message 336 Identify by the UE 302 was received. The E-UTRAN access point 304 determines that the N1 Capability indication from the RRC connection setup completion message 336 is missing. Accordingly, the E-UTRAN access point determines 304 based on the absence of N1 Ability indicator that the UE 302 a connection with a EPC about the MME 308 wants to build up. Based on the determination that the UE 302 the connection with a EPC builds, generates and transmits the E-UTRAN access point 304 a S1AP start UE message 338 to the MME 308 , The S1AP initial UE message 338 contains the EPC NAS connection request from the RRC connection setup completion message 336 ,
  • The MME 308 identifies the S1AP start UE message 338 , In response to the identification of the S1AP initial UE message 338 call the MME 308 Subscription information with the UE 302 are associated by one HSS from (such as the HSS 202 ( 2 )). The MME 308 determines that the UE 302 a subscription to EPC based on the subscription information. Therefore, the decides MME 308 to grant the registration request. The MME 308 generates and transmits a S1AP downlink NAS transport message 340 to the E-UTRAN access point 304 , The S1AP downlink NAS transport message 340 Contains an EPC NAS connection accept.
  • The E-UTRAN access point 304 identifies the S1AP downlink NAS transport message 340 by the MME 308 was received. The E-UTRAN access point 304 directs the EPC NAS connection acceptance in a RRC downlink information transmission message 342 to the UE 302 further. In some embodiments, the E-UTRAN access point determines 304 that the registration request by the EPC by routing the EPC NAS connection request to the MME 308 and identifying the EPC NAS Port Acceptance in the S1AP Downlink NAS Transport Message 340 Is accepted.
  • 4 illustrates a message flow of an exemplary registration request process 400 according to various embodiments. In particular, illustrated 4 the signal flow under a UE 402 (like the UEs 104 ( 1 ) and / or the UEs 230 ( 2 )), an E-UTRAN access point 404 (such as the second E-UTRAN access point 112b ( 1 ) and / or the E-UTRAN access point 224 ( 2 )), one AMF 406 (like the AMF 226 ( 2 )) and one MME 408 (like the MME 222 ( 2 )). The E-UTRAN access point 404 For example, in the illustrated embodiment, connections to the AMF 406 and the MME 408 provide. The exemplary registration request process 400 illustrates a successful registration with a 5GC ,
  • The UE 402 initially camps on an E-UTRAN cell and listens to the system information broadcast from the E-UTRAN access point 404 , In particular, the E-UTRAN access point generates and radiates 404 a system information signal 410 out through the UE 402 Will be received. The system information signal 410 indicates that the E-UTRAN access point 404 a connection with 5GC and EPC offering. In particular, the system information signal 410 "N1 / 5GC supported "to indicate that the E-UTRAN access point 404 a connection with 5GC offers, and " S1 / EPC supports "to indicate that the E-UTRAN access point 404 a connection with the EPC offering. In other embodiments, the display of EPC be given implicitly, such as by the UE 402 assumes that EPC supported, and the E-UTRAN access point 404 only expressly indicates if EPC not supported.
  • The UE 402 builds an RRC connection with the E-UTRAN access point 404 on. In particular, it generates and transmits the UE 402 an RRC connection request message 412 to the E-UTRAN access point 404 and the E-UTRAN access point 404 responds with an RRC connection setup message 414 , The UE 402 generates and transmits an RRC connection setup completion message 416 to the E-UTRAN access point 404 in response to the identification of the RRC connection setup message 414 , The RRC connection setup completion message 416 contains an ad that the UE 402 the N1 Interface, such as displaying "N1 capability" in the RRC connection setup completion message 416 , It also contains the RRC connection setup completion message 416 the 5GC -NAS message "Registration request."
  • The E-UTRAN access point 404 identifies the RRC connection setup completion message 416 with the 5GC -NAS message "Registration request." The E-UTRAN access point 404 determined from the indication that the UE 402 the N1 Interface in the RRC connection setup completion message 416 is included that the UE 402 a connection with a 5GC wants to build up (such as the 5GC 110 ( 1 )). The E-UTRAN access point 404 choose the AMF 406 and generates and transmits an N2AP start UE message 418 to the AMF 406 , The N2AP initial UE message 418 contains the 5GC NAS "Registration request."
  • The AMF 406 gets the subscription information that comes with the UE 302 are associated, from a combined UDM and HSS (like the combined UDM and HSS 106 ( 1 ) and / or the combined UDM and HSS 210 ( 2 )). The AMF 406 determines that the UE 402 a subscription to NO based on the subscription information. Therefore, the decides AMF 406 to accept the registration request. The AMF 406 generates and transmits an N2AP downlink NAS transport message 420 to the E-UTRAN access point 404 , The N2AP Downlink NAS Transport Message 420 contains one 5GC NAS registration acceptance.
  • The E-UTRAN access point 404 identifies the N2AP downlink NAS transport message 420 by the AMF 406 Will be received. The E-UTRAN access point 404 directs the 5GC NAS registration acceptance to the UE 402 in a RRC downlink information transfer message 422 further. In some embodiments, the E-UTRAN access point determines 404 by routing the 5GC NAS Registration Request to the MME 408 and identification of 5GC - NAS registration acceptance in the N2AP downlink NAS transport message 420 that the registration request on the 5GC is accepted.
  • 5 illustrates an exemplary connection method 500 according to various embodiments. The connection method 500 is executed by a UE (such as the UEs 104 ( 1 ), the UEs 230 ( 2 ), the UE 302 ( 3 ), and / or the UE 402 ( 4 )).
  • In stage 502 determines the UE whether to try to connect to the NO manufacture. The UE For example, you can determine if the N1 Radio has been disabled. Furthermore, the UE determine if one PLMN ID or tracking area ID corresponding to an access point with which the UE For NO would join in a stored list of PLMN IDs located in which N1 is not allowed, or in a saved list of tracking area IDs in which N1 not allowed. In some embodiments, the UE determine if the attempt to deal with the NO to connect is not optimal. For example, the UE determine that the connection with the NO the transfer of one SGSN (like that SGSN 218 ( 2 )) to an AMF (such as the AMF 226 ( 2 )), which would not allow transmission of UE context, may result in an assignment of a new IP address, and / or may result in service interruptions at an inappropriate time (such as during a telephone call). Furthermore, the UE Determine whether a registration denial message that resulted from subscription information for the UE not in a combined UDM and HSS stored (such as the combined UDM and HSS 210 ( 2 )) have previously been received in some embodiments.
  • In stage 504 configures or reconfigures the UE the network prioritization. In particular, the configured UE the prioritization to prioritize the connection with EPC about the connection with NO if the UE determines that the connection with NO is not optimal. In embodiments in which the UE does not determine if the connection with NR is not optimal, can be level 504 be left out.
  • The procedure 500 goes with step 506 or level 512 Depending on whether the UE determines that it should try to cooperate with the NO connect to. If the UE finds that it should try to contact NO to connect, the procedure continues 500 with level 506 continued. In stage 506 try the UE , with NO connect to. The UE For example, the method performed by the UE is executed after message 312 ( 3 ) to message 316 ( 3 ) or message 412 ( 4 ) to message 416 ( 4 ) by.
  • In stage 508 determines the UE whether the connection with NO successfully built up. In particular, determines the UE , if she 5GC NAS registration acceptance or the SGC NAS registration denial in a RRC downlink information transmission message (such as the RRC downlink information transmission message) 322 ( 3 ) and the RRC downlink information transmission message 422 ( 4 )) was received. If the 5GC NAS registration acceptance is received, the process ends 500 at level 508 , If the 5GC NAS registration rejection is received UE a RRC Connection release after the RRC connection release message 326 To run. Furthermore, the UE , if the 5GC -NAS registry deny, identify an MM root that is included in the RRC downlink information transfer message. If the MM cause is in the N1 Mode is not allowed, does the procedure 500 with level 510 further.
  • In stage 510 deactivates the UE the N1 -Ability. In particular, the leads UE the deactivation procedure 330 ( 3 ) through to the N1 Ability to disable.
  • If the UE in stage 502 determines that she is not with NO should connect, does the procedure 500 from level 502 or level 504 with level 512 further. Further, the procedure does 500 from level 510 with level 512 further. In stage 512 try the UE to deal with that EPC connect to. In stage 512 leads the UE For example, the method used by the UE is executed after message 332 ( 3 ) to message 336 ( 3 ) by.
  • In stage 514 determines the UE, whether the connection with the EPC successfully built up. In particular, determines the UE whether an EPC NAS Port Acceptance or an EPC NAS Port Decline in a RRC Downlink Information Transfer Message (such as the RRC Downlink Information Transfer Message 342 ( 3 ) was received.
  • 6 illustrates another exemplary connection method 600 according to various embodiments. The connection method 600 is through an access point (such as the access points 112 ( 1 ), the GERAN / UTRAN access point 220 ( 2 ), the E-UTRAN access point 224 ( 2 ), the NR access point 228 ( 2 ), the E-UTRAN access point 304 ( 3 ), and / or the E-UTRAN access point 404 ( 4 )). In some embodiments, the connection method becomes 600 possibly only through an access point providing a connection to both EPC and NR.
  • In stage 602 the access point executes an RRC setup. In particular, the access point performs a procedure that passes through an access point after notification 310 ( 3 ) to message 316 ( 3 ) to be executed.
  • In stage 604 determines the access point, with which network a UE (like the UEs 104 ( 1 ), the UEs 230 ( 2 ), the UE 302 ( 3 ), and / or the UE 402 ( 4 )) tries to establish a connection. In particular, the access point determines whether an RRC connection setup completion message (such as the RRC connection setup completion message 316 , the RRC connection setup completion message 336 ( 3 ), and / or the RRC connection setup completion message 416 ( 4 )) of the UE was received, an indication of N1 Capability, includes an SGC NAS Registration Request and / or an EPC NAS Port Request. The access point determines that the UE is attempting to establish a connection with NR if the RRC connection setup completion message is an indication of the N1 Capability and / or SGC NAS registration request. The procedure 600 do with level 606 continue if the access point determines that the UE trying to connect to NR. The access point determines that the UE Attempts to connect to EPC if the RRC connection setup completion message contains an EPC NAS Port Request. The procedure 600 do with level 610 continue if the access point determines that the UE trying to connect with EPC build.
  • In stage 606 the access point tries to connect to NO for the UE build. In particular, the access point performs the procedure performed by the access point upon notification 318 ( 3 ) and message 320 ( 3 ), or message 418 ( 4 ) and 420 ( 4 ), is performed.
  • In stage 608 the access point determines if a successful connection to NR has been established. In particular, the access point determines whether an N2AP downlink NAS transport message (such as the N2AP downlink NAS transport message 320 ( 3 ) and / or the N2AP downlink NAS transport message 420 ( 4 )) an SGC NAS registration denial or a 5GC NAS Registration Receipt Contains. If the access point determines that an N2AP downlink NAS transport message is a 5GC NAS registration denial, the access point generates and transmits an RRC downlink information transmission message (such as the RRC downlink information transmission message) 322 ( 3 ) to the UE, the RRC downlink information transmission message relaying the message 5GC NAS Registry Denial and MM Causes Viewer. If the access point determines that an N2AP downlink NAS transport message is a 5GC -NAS registration acceptance, the access point generates and transmits an RRC downlink information transmission message (such as the RRC downlink information transmission message) 422 ( 4 )) to the UE wherein the RRC downlink information transmission message forwarded the one 5GC NAS Registration Receipt Contains.
  • In stage 610 the access point tries to connect to EPC for the UE build. In particular, the access point performs a procedure that passes through the access point upon notification 338 ( 3 ) and message 340 ( 3 ) to be executed.
  • In stage 612 The access point determines if a successful connection with EPC has been established. In particular, the access point determines whether a S1AP downlink NAS transport message (such as the S1AP downlink NAS transport message 340 ( 3 )) contains an EPC NAS port denial or an EPC NAS accept. If the access point determines that an S1AP downlink NAS transport message contains an EPC NAS port denial, the access point generates and transmits an RRC downlink information transfer message (such as the RRC downlink information transfer message 342 ( 3 ) to the UE, the RRC downlink information transmission message including the forwarded EPC NAS port denial and MM cause indication. If the access point determines that an S1AP downlink NAS transport message contains an EPC NAS Port Acceptance, the access point generates and transmits an RRC Downlink Information Transfer message to the UE wherein the RRC downlink information transmission message includes the forwarded EPC NAS connection assumption.
  • 7 illustrates an architecture of a system XS00 a network according to some embodiments. The system XS00 is considered a user equipment ( UE ) XS01 and a UE XS02 containing shown. The UEs XS01 and XS02 are illustrated as smartphones (eg, portable mobile touchscreen computing devices that can be connected to one or more mobile phone networks), but may also include any mobile or non-mobile computing device, such as personal data assistants (e.g. PDAs ), Pagers, laptop computers, desktop computers, wireless hand sets or any computing device having a wireless communication interface.
  • In some embodiments, all of UEs XS01 and XS02 an Internet of Things (IoT) UE, which may include a network access layer designed for low power IoT applications that use short lived UE connections. An IoT UE can use technologies such as machine-to-machine (M2M) or machine-type communications ( MTC ) for the exchange of data with an MTC server or a device via a public land mobile network (PLMN), a Proximity-Based Service (ProSe) or Device-to-Device (D2D) communications, sensor networks, or IoT networks. Of the M2M or MTC data exchange may be a machine initiated data exchange. An IoT network describes connecting IOT-UEs that can contain uniquely identifiable embedded computing devices with short-lived connections (within the Internet infrastructure). The IoT UEs can run background applications (eg, keep-alive messages, status updates, etc.) to enable the connections of the IoT network.
  • The UEs XS01 and XS02 can be configured to connect to a Radio Access Network (RAN) XS10 to connect, z. B. to couple communicatively - the RAN XS10 For example, an Evolved Universal Mobile Telecommunications System (UMTS) can be Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or any other type of RAN. The UEs XS01 and XS02 use connections XS03 respectively. XS04 each containing a physical communication interface or location (which is explained in more detail below); in this example are the links XS03 and XS04 illustrated as an air interface to facilitate a communicative connection, and may correspond to cellular communication protocols, such as a "Global System for Mobile Communications" - ( GSM ) Protocol, a "Code-Division Multiple Access" (CDMA) network protocol, a "push-to-talk" ( PTT ) Protocol, a " PTT over Cellular "- ( POC ) Protocol, a "Universal Mobile Telecommunications System" ( UMTS ) Protocol, a " 3GPP Long Term Evolution "- ( LTE ) Protocol, a "Fifth Generation" ( 5G ) Protocol, a "New Radio" ( NO ) Protocol and the like.
  • In this embodiment, the UEs XS01 and XS02 Furthermore, communication data directly via a ProSe interface XS05 change. The ProSe interface XS05 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including, but not limited to, a physical sidelink control channel (FIG. PSCCH ), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel ( PSDCH ) and a "Physical Sidelink Broadcast Channel" ( PSBCH ).
  • The UE XS02 than for access to an access point ( AP ) XS06 about the connection XS07 configured. The connection XS07 may include a local wireless connection, such as a connection that one IEEE 802.11 protocol, where the AP XS06 includes a wireless fidelity (WiFi®) router. In this example, the AP XS06 as connected to the Internet without being connected to the core network of the wireless system (described in more detail below).
  • The RAN XS10 may contain one or more access nodes containing the connections XS03 and XS04 enable. These access nodes ( ANs ) can be used as base stations ( BSs ), NodeBs, evolved NodeBs ( eNBs ), Next Generation NodeBs ( GNB , RAN nodes, and so on, and may include ground stations (eg, terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). The RAN XS10 may include one or more RAN nodes for providing macrocells, e.g. For example, macro RAN nodes XS11 , and one or more RAN nodes for providing femtocells or picocells (e.g., cells with smaller coverage areas, smaller user capacity or higher bandwidth compared to macrocells), e.g. B. the low-power ( LP ) RAN node XS12 ,
  • Each of the RAN nodes XS11 and XS12 can complete the air interface protocol and can be the first contact point for the UEs XS01 and XS02 be. In some embodiments, each of the RAN nodes may XS 11 and XS 12 different logical functions for the RAN XS10 including but not limited to radio network controller ( RNC ) Functions, such as radio bearer management, dynamic uplink and downlink radio resource management and data packet planning, as well as mobility management.
  • According to some embodiments, the UEs XS01 and XS02 configured using "Orthogonal Frequency Division Multiplexing" - ( OFDM ) Communication signals with each other or with one of the RAN nodes XS11 and XS12 communicate via a multi-carrier communication channel according to various communication techniques, such as, but not limited to, an "Orthogonal Frequency Division Multiple Access" - ( OFDMA ) Communication technology (eg for downlink communication) or a "single carrier frequency division multiple access" (SC-FDMA) communication technology (eg for uplink and ProSe or Sidelink communication), although the scope the embodiments is not limited in this regard. The OFDM signals may comprise a plurality of orthogonal subcarriers.
  • In some embodiments, a downlink resource lattice may be for downlink transmissions from one of the RAN nodes XS11 and XS12 on the UEs XS01 and XS02 while the uplink transmissions can use similar techniques. The grid may be a time-frequency grid, referred to as the resource lattice or time frequency resource lattice, which represents the physical resource in the downlink in each slot. Such time frequency level representation is a common method for OFDM systems, what makes it intuitive for radio resource allocation. Each column and row of the resource grid corresponds to an OFDM symbol or an OFDM subcarrier. The duration of the resource grid in the time domain corresponds to a slot in a radio frame. The smallest time-frequency unit in a resource grid is referred to as a resource element. Each resource grid includes a number of resource blocks that describe the association of specific physical channels with resource elements. Each resource block comprises a collection of resource elements; in the frequency domain, this can represent the smallest amount of resources that can currently be allocated. There are several different physical downlink channels that are transmitted using such resource blocks.
  • The physical downlink channel ( PDSCH ) can provide user data and higher level signaling to the UEs XS01 and XS02 wear. The physical downlink control channel ( PDCCH ) may, among other things, carry information about the transport format and the resource allocations related to the PDSCH channel. He can also use the UEs XS01 and XS02 about the transport format, the resource allocation and H-ARQ (Hybrid Automatic Repeat Request) Inform information regarding the uplink shared channel. Typically, downlink scheduling (assignment of the control and shared channel resource blocks to the UEs XS01 and or XS02 within a cell) at each of the RAN nodes XS11 and XS12 based on channel quality information obtained from one of the UEs XS01 and XS02 be fed back. The downlink resource allocation information may be on the PDCCH be sent for each of the UEs XS01 and XS02 is used (eg assigned).
  • Of the PDCCH can the control channel elements ( CCEs ) to transmit the control information. Prior to mapping to resource elements, the complex value PDCCH symbols may first be organized into groups of four, which may then be permuted using a sub-block for rate matching. Everyone PDCCH can be done using one or more of the CCEs be transferred, each one CCE nine sets of four physical resource elements that can be used as resource element groups ( REGs ) are known. Four Quadrature Phase Shift Keying ( QPSK ) Symbols can be anybody REG be assigned. Of the PDCCH can be done using one or more CCEs depending on the size of the downlink control information ( DCI ) and the channel state. There may be four or more different PDCCH formats in the LTE with different numbers of CCEs be defined (eg aggregation level, L = 1, 2, 4, or 8).
  • Some embodiments may use resource channel assignment concepts for control channel information that is an extension of the concepts described above. For example, some embodiments may include an improved physical downlink control channel ( ePDCCH ) using PDSCH resources for the transmission of control information. Of the ePDCCH can be performed using one or more improved control channel elements ( ECCes ) be transmitted. As stated above, each one can ECCE nine sets of four physical resource elements that are considered to be improved resource element groups ( EREGs ) are known. One ECCE can in some situations other numbers of EREGs contain.
  • The RAN XS10 is considered communicative with a core network ( CN ) XS20 connected - via a S1 -Interface XS13 , In embodiments, the CN XS20 an evolved packet core ( EPC ) Network, a NextGen Packet Core ( NPC ) Network or another type of CN be. In this embodiment, the S1 -Interface XS13 divided into two parts: the S1 -U interface XS14 that traffic data between the RAN nodes XS11 and XS12 and the server gateway (S-GW) XS22 and the 51 Mobility Management Entity (MME) interface XS15 providing a signaling interface between the RAN nodes XS11 and XS12 and MMEs XS21 is.
  • In this embodiment, the CN XS20 the MMEs XS21 , the S-GW XS22 , the Packet Data Network ( PDN ) Gateway ( P-GW ) XS23 and a Home Subscriber Server ( HSS ) XS24 , The MMEs XS21 can be similar in function to the control level of the old server "General Package Radio Service" - ( GPRS ) Support node ( SGSN ) be. The MMEs XS21 can manage mobility in aspects of access such as gateway selection and tracking list management. Of the HSS XS24 may comprise a database for network users, including subscription-related information for assisting the handling of the network entities with communication sessions. The CN XS20 can have one or more HSSs XS24 include, depending on the number of mobile subscribers, the capacity of the devices, the organization of the network, etc. For example, the HSS XS24 Support for routing / roaming, authentication, authorization, naming / addressing solutions, location dependencies, etc.
  • Of the S-GW XS22 can the S1 -Interface XS13 with the RAN XS10 connect and route data packets between the RAN XS10 and the CN XS20 , Furthermore, that can S-GW XS22 represent a local mobility anchor point for inter-RAN node handoffs and also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, loading and some enforcement of policies.
  • The P-GW XS23 can use a SGi interface with a PDN connect. The P-GW XS23 can data packets between the CN XS20 and external networks like a network, which is the application server XS30 contains (alternatively referred to as application function ( AF )) via an internet protocol ( IP) interface XS25 route. In general, the application server XS30 be an element that offers applications that use IP bearer resources with the core network (eg UMTS Packet Services ( PS ) Domain, LTE PS Data services, etc.). In this embodiment, the P-GW XS23 via an IP communication interface XS25 communicatively with an application server XS30 shown connected. The application server XS30 can also be configured to provide one or more communication services for the UEs XS01 and XS02 over the CN XS20 support (eg Voice over Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.).
  • The P-GW XS23 may also be a node for policy enforcement and the task of collecting the data. The policy and job enforcement feature ( PCRF ) XS26 is the policy and order enforcement element of the CN XS20 , In a non-roaming scenario, a single PCRF in the Home Public Land Mobile Network ( HPLMN ) available with an Internet Protocol Connectivity Access Network (IP CAN ) Meeting of a UEs is associated. In a roaming scenario with local traffic outbreak, two can PCRFs that with the IP-CAN session of a UEs to be present: a home PCRF ( H-PCRF ) in one HPLMN and a Visited PCRF ( V-PCRF ) in a Visited Public Land Mobile Network ( VPLMN ). The PCRF XS26 can be communicative about the P-GW XS23 with the application server XS30 be connected. The application server XS30 can the PCRF XS26 signal a new service flow and the appropriate quality of service ( QoS ) and order parameters. The PCRF XS26 This rule can be used in a policy and job enforcement function ( PCEF ) (not shown) with the appropriate traffic flow template ( TFT ) and the QoS identifier class ( QCI ) represent what the QoS and commissioning according to specifications of the application server XS30 starts.
  • 8th illustrates an architecture of a system XR00 a network according to some embodiments. The system XR00 is a UE XR01 that are the same or similar to the UEs XS01 and XS02 may be that previously discussed; a RAN node XR11 that is the same or similar to the RAN node XS11 and XS12 may be that previously discussed; a user-level function ( UPF ) XR02 ; a data network ( DN ) XR03 which may, for example, be operator services, Internet access or third party services; and a 5G core network ( 5GC or CN ) XR20 containing shown.
  • The CN XR20 can be an authentication server function ( FAIL ) XR22 ; a core access and a mobility management function ( AMF ) XR21 ; a session management function ( SMF ) XR24 ; a network exposure feature ( NEF ) XR23 ; a policy control function ( PCF ) XR26 ; a network function ( NF ) Repository function ( NRF ) XR25 ; a unified data management ( UDM ) XR27 ; and an application function ( AF ) XR28 contain. The CN XR20 may also contain other elements that are not shown, such as a structured data storage network function ( SDSF ), an unstructured data storage network function ( UDSF ) and the same.
  • The UPF XR02 can serve as an anchor point for intra-RAT and inter-RAT mobility, an external protocol data unit ( PDU ) Meeting liaison with DN XR03 , and a branch point to support multi-homed PDU sessions. The UPF XR02 may also perform packet routing and routing, packet control, enforcing the user-level portion of the policy rules, compliant interception packets (UP collection); Traffic usage reports, performing user-level QoS handling (e.g., packet filtering, gating, UL / DL ratification), performing uplink traffic verification (e.g. SDF to QoS scheduling), transport plane packet tagging in uplink and downlink, and downlink packet buffering and downlink data message triggering. UPF XR02 may include an uplink classifier to support traffic flows to a data network. The DN XR03 may represent various network operator services, internet access or third party services. The DN XR03 can the previously discussed application server XS30 represent or be similar to this.
  • The AUSF XR22 can provide data for authentication of UE XR01 save and perform functions associated with authentication. Enables a common authentication framework for different access types.
  • The AMF XR21 can be used for registration management (eg for registering the UE XR01 , etc.), connection management, reachability management, mobility management and lawful interception of AMF-related events, as well as access authentication and authorization. The AMF XR21 can transport for SM messages between UE XR01 and SMF XR24 and serve as a transparent proxy for the routing of SM messages. AMF XR21 can also transport for "Short Message Service" - ( SMS ) Messages between UE XR01 and an SMS function ( SMSF ) (in 8th not shown). AMF XR21 can act as a safety anchor function ( SEA ), what the interaction with the FAIL XR22 and the UE XR01 , and the receipt of an authentication key, due to the authentication method of the UE XR01 was built. If a USIM-based authentication is used, the AMF XR21 the safety material from the FAIL XR22 recall. AMF XR21 can also be a "Security Context Management" - ( SCM ) Contain a key from the function SEA it uses to obtain access network-specific keys. Next, the AMF XR21 A connection point of the RAN-CP interface ( N2 Reference point), a connection point of the NAS ( N1 ) Signaling and performing NAS ciphering and integrity protection.
  • AMF XR21 can also use NAS signaling with a UE XR01 over a N3 Collaborative Function ( IMF ) Support interface. The N3IWF can be used to provide access to untrusted entities. The N3 -IWF can be a connection point for the N2 - and N3 Interfaces for the control level or the user level, and so on N2 Signaling from the SMF and AMF for PDU sessions and QoS handle packages for IPsec and N3 Encapsulate / decapsulate tunneling, N3 - Highlight user-level packets in the uplink and QoS , the N3 -Paketmarkierung corresponds, enforce, where QoS Requirements to be noted in connection with such a mark over N2 was received. N3IWF can also use uplink and downlink control plane NAS ( N1 ) Signaling between the UE XR01 and AMF XR21 forward and uplink and downlink user-level packets between the UE XR01 and the UPF XR02 transfer. The N3IWF also provides mechanisms for IPsec tunneling with the UE XR01 ready.
  • The SMF XR24 can be used for session management (eg, session setup, modification and release, including tunnel maintenance between UPF and AN nodes); UE IP Address Allocation & Management (including optional authorization); Selection and control of the UP function; configures traffic control on UPF to route traffic to the correct destination; Connecting the interfaces to policy control functions; Controlling part of the policy enforcement and QoS; compliant interception (for SM events and interface to the LI system); Completion of SM parts of NAS messages; Downlink data communication; Initiator of AN-specific SM information by AMF above N2 sent to AN; Determine the SSC mode of a session.
  • The SMF XR24 may include the following roaming feature: Local enforcement handling for applying QoS SLAs ( VPLMN ); Fee data collection and fee interface ( VPLMN ); compliant interception (in VPLMN for SM events and interface to the LI system); Support for interaction with external DN for transporting PDU session authorization signaling / external DN authentication.
  • The NEF XR23 may provide resources, the services and capabilities provided by 3GPP network features to third parties, internal disclosure / re-disclosure, application features (e.g., AF XR28 ), Edge computing or fog computing systems etc. In such embodiments, the NEF XR23 the AFs authenticate, authorize and / or throttle. NEF XR23 can also translate information with the AF XR28 exchanged and information exchanged with internal network features. For example, the NEF XR23 between an AF service identifier and an internal one 5GC Translate information. The NEF XR23 can also read information from other network features ( NFs ) based on disclosed capabilities of other network functions. This information can be found in the NEF XR23 stored as structured data or in a data storage NF using standardized interfaces. The stored information can then be redone by the NEF XR23 other NFs and AFs disclosed to and / or used for other purposes such as analysis.
  • The NRF XR25 can support service discovery features, receive NF discovery requests from NF instances, and route the information of detected NF instances to the NF instances. The NRF XR25 also maintains information about available NF instances and their supported services.
  • The PCF XR26 can provide policy rules for control plane function (s) to enforce them, and can also support a consistent policy framework for controlling network behavior. The PCF XR26 can also be a frontend ( FE ) as access to subscription information required for policy decisions in a user data repository ( UDR ) of UDM XR27 are relevant.
  • The UDM XR27 can handle subscription-related information to assist the handling of the communication sessions by the network entities, and can subscribe to the subscription data UE XR01 to save. The UDM XR27 can contain two parts: an application FE and a UDR. The UDM can one UDM-FE responsible for processing access data, location management, subscription management and so on. Several different front ends can serve the same user in different transactions. The UDM-FE accesses subscription information contained in the UDR and performs the authentication access data processing; the user identification handling; the access authorization; the registration / mobility management; and subscription management. The UDR can with the PCF XR26 to interact. The UDM XR27 can also support SMS management, taking one SMS-FE implements a similar application logic as previously discussed.
  • The AF XR28 can provide application influence on traffic routing to the "Network Capability Exposure" ( NCE ) and access the policy control policy frame value. The NCE can be a mechanism that does it 5GC and AF XR28 allowed each other over NEF XR23 Send information that can be used for edge computing transformations. In such implementations, the network operator and third party services may be close to the UE XR01 Access point of the port to achieve efficient service delivery through reduced end-to-end latency and load on the transport network. For edge computing implementations, the 5GC a UPF XR02 near the UE XR01 select and control traffic from the UPF XR02 to the DN XR03 about the N6 Interface. This can be done on the UE subscription data, the UE Location and information provided by the AF XR28 provided. In this way, the AF XR28 the (re) selection of the UPF and affect traffic routing. Based on the operator use, if the AF XR28 is considered a trusted entity, the network operator of the AF XR28 allow, directly with the relevant NFs to interact.
  • As previously discussed, that can CN XR20 a SMSF which is responsible for SMS subscription verification and verification, and SM messages to / from the UE XR01 to other / other entities such as an SMS-GMSC / IWMSC / SMS router. The SMS can also be used for the procedure for notifying that the UE XR01 is available for SMS transmission with AMF XR21 and UDM XR27 interact, (for example, set a UE unreachable flag and UDM XR27 inform when the UE XR01 is available for SMS).
  • The system XR00 may contain the following service-based interfaces: Namf: Service-based interface of AMF ; Nsmf: Service based interface of SMF ; Nnef: Service-based interface of NEF ; Npcf: service based interface of PCF ; Nudm: Service-based interface of UDM ; Naf: Service based interface of AF ; Nnrf: Service-based interface of NRF ; and Nausf: Service-based interface of FAIL ,
  • The system XR00 can contain the following reference points: N1 : Reference point between UE and AMF ; N2 : Reference point between (R) AN and AMF ; N3 : Reference point between (R) AN and UPF ; N4 : Reference point between SMF and UPF ; and N6 : Reference point between UPF and a data network. There may be many more reference points and / or service-based interfaces between the NF services in the NFs give. However, these interfaces and reference points have been omitted for the sake of clarity. For example, a N5 Reference point between PCF and AF lie; one N7 Reference point can be between PCF and SMF are located; an N11 reference point between AMF and SMF ; etc. In some embodiments, the CN XR20 contain an Nx interface that has an inter-CN interface between the MME (eg MME XS21 ) and AMF XR21 is to cooperation between CN XR20 and CN XS20 to enable.
  • If not in 8th is shown, the system can XR00 multiple RAN nodes XR11 contain an Xn interface between two or more RAN nodes XR11 (eg, gNBs and the like) defined with 5GC XR20 connected between a RAN node XR11 (eg gNB), which with 5GC XR20 and an eNB (eg, a RAN node XS11 out 7 ) and / or between two eNBs associated with 5GC XR20 are connected.
  • In some implementations, the Xn interface may include an Xn user-level (Xn-U) interface and an Xn-control plane (Xn-C) interface. The Xn-U can provide non-guaranteed delivery of user-level PDUs and support / provide data forwarding and flow control capabilities. The Xn-C can provide management and error handling functions, functions to manage the Xn-C interface; Mobility support for the UE XR01 in a connected mode (e.g., CM-CONNECTED) including a function for managing the UE mobility for the connected mode between one or more RAN nodes XR11 , The mobility support can be context transfer from an old (source) server RAN node XR11 to a new (destination) server RAN node XR11 ; and user plane tunnel control between the old (source) server RAN node XR11 to the new (destination) server RAN node XR11 contain.
  • A protocol stack of the Xn-U may include a transport network layer that is based on the Internet Protocol (IP) transport layer, and a GTP U layer on a UDP and / or IP layer (s) for supporting the user-level PDUs. The Xn-C protocol stack may include an application layer signaling protocol (referred to as Xn Application Protocol (Xn-AP)) and a transport network layer that is built on an SCTP layer. The SCTP layer may be located on an IP layer. The SCTP layer provides guaranteed delivery of application location messages. In the transport IP layer, a point-to-point transmission is used to deliver the signaling PDUs. In other implementations, the Xn-U protocol stack and / or the Xn-C protocol stack may be the same or more similar as the user level and / or control plane protocol stack illustrated and described herein.
  • 9 illustrates exemplary components of a device XT00 according to some embodiments. In some embodiments, the device may XT00 application circuit XT02 , Baseband circuit XT04 , Radio frequency (radio frequency) RF ) Circuit XT06 , Front-end module ( FEM ) Circuit XT08 , one or more antennas XT10 and power management circuit ( PMC ) XT12 at least as shown coupled together. The components of the illustrated device XT00 may be included in a UE or a RAN node. In some embodiments, the device may XT00 contain fewer elements (for example, a RAN node may not have application circuits XT02 and instead contain a processor / controller for processing IP data received from an EPC). In some embodiments, the device may XT00 include other items such as memory / storage media, display, camera, sensor or input / output (I / O) interface. In other embodiments, the components described below may be included in more than one device (eg, the circuits may be included separately in more than one device for cloud RAN (C-RAN) implementations).
  • The application circuit XT02 can contain one or more application processors. For example, the application circuit XT02 Circuits such as, but not limited to, one or more single-core or multi-core processors. The processor (s) may include any combination of general-purpose processors and special processors (eg, graphics processors, application processors, etc.). The processors may be connected to or contain memory / storage media and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems on the device XT00 to run. In some embodiments, the processors of the application circuits XT02 Process IP data packets received from an EPC.
  • The baseband circuits XT04 may include circuitry such as, but not limited to, one or more single core or multi-core processors. The baseband circuits XT04 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuits XT06 and baseband signals for a transmission signal path of the RF circuits XT06 to create. Baseband processing circuits XT04 can interface with the application circuits XT02 comprise the baseband signals for the control of functions of the RF circuits XT06 to produce and process. For example, in some embodiments, the baseband circuits XT04 a baseband processor XT04A the third generation ( 3G) , a baseband processor XT04B the fourth generation ( 4G) , a baseband processor XT04C the fifth generation ( 5G) or one or more other baseband processor (s) XT04D for other existing generations, generations in development or in the future to develop (eg second generation ( 2G) sixth generation ( 6G) etc.). The baseband circuits XT04 (eg one or more baseband processors XT04A-D ) can handle various radio control functions that require communication with one or more radio networks via the RF circuits XT06 enable. In other embodiments, some or all of the functions of the baseband processors may be XT04A-D contained in modules that are in memory XT04G stored and via a central processing unit ( CPU ) XT04E be executed. The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuits of the baseband circuits XT04 Fast Fourier Transformation ( FFT ), Precoding or constellation mapping / mapping separation functions. In some embodiments, the encoding / decoding circuits of the baseband circuits XT04 Convolution, tail-biting convolution, turbo, viterbi, or low density parity check ( LDPC ) Include coding / decoding functions. Embodiments of modulation / demodulation and encoder / decoder function are not limited to these examples, and may include other suitable functions in other embodiments.
  • In some embodiments, the baseband circuits XT04 one or more audio digital signal processor (s) ( DSP ) XT04F contain. The audio DSP (s) XT04F may include elements for compression / decompression and echo cancellation, and may include other suitable processing elements in other embodiments. Components of the baseband circuits may, in some embodiments, be suitably combined in a single chip or chipset or placed on a same board. In some embodiments, some or all of the constituents that make up the baseband circuits XT04 and the application circuits XT02 be implemented together, such as on a system on a chip ( SOC ).
  • In some embodiments, the baseband circuits XT04 provide communication that is compatible with one or more wireless technologies. For example, in some embodiments, the baseband circuits XT04 Communicate with an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) or other wireless urban area networks ( WMAN ), a wireless local area network ( WIRELESS INTERNET ACCESS ), a wireless personal network ( WPAN ) support. Embodiments in which the baseband circuit XT04 is configured to support radio communications from more than one wireless protocol may be referred to as multimodal baseband circuits.
  • RF circuits XT06 can facilitate communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuits XT06 Switches, filters, amplifiers, etc. included to enable communication with the wireless network. RF circuits XT06 may include a receive signal path that may include circuitry to receive RF signals provided by the FEM circuits XT08 were to be converted, and baseband signals for the baseband circuits XT04 provide. RF circuits XT06 may also include a transmit signal path, which may include circuits for baseband signals transmitted through the baseband circuits XT04 are provided, upconvert and RF output signals to the FEM circuits XT08 to provide for transmission.
  • In some embodiments, the receive signal path of the RF circuits XT06 mixer circuits XT06a , Amplifier circuits XT06b and filter circuits XT06c contain. In some embodiments, the transmit signal path of the RF circuits XT06 filter circuits XT06c and mixer circuits XT06a contain. RF circuits XT06 may also synthesizer circuits XT06d for synthesizing a frequency for use by the mixer circuits XT06a of the received signal path and the transmission signal path. In some embodiments, the mixer circuit XT06a The receive signal path may be configured to receive RF signals from the FEM circuit XT08 based on the synthesized frequency generated by the synthesizer circuit XT06d is provided to convert. The amplifier circuit XT06b may be configured to amplify the downconverted signals and the filter circuit XT06c can a low-pass filter ( LPF ) or band-pass filter ( BPF ) configured to remove unwanted signals from the downconverted signals to produce output baseband signals. Output baseband signals can be used for baseband circuits XT04 be provided for further processing. In some embodiments, the output baseband signals may be zero frequency baseband signals, but this is not a requirement. In some embodiments, the mixer circuit XT06a of the received signal path include passive mixers, although the scope of the embodiments is not limited in this respect.
  • In some embodiments, the mixer circuit XT06a of the transmit signal path, input baseband signals based on the synthesized frequency generated by the synthesizer circuit XT06d is to be upconverted to RF output signals for the FEM circuit XT08 to create. The baseband signals can be through the baseband circuit XT04 be provided and can by filtering circuits XT06c be filtered.
  • In some embodiments, the mixer circuit XT06a the received signal path and the mixer circuit XT06a of the transmit signal path may include two or more mixers and be arranged for quadrature down conversion or upconversion, respectively. In some embodiments, the mixer circuit XT06a the received signal path and the mixer circuit XT06a of the transmit signal path include two or more mixers and be arranged for image rejection (eg, Hartley image rejection). In some embodiments, the mixer circuit XT06a the received signal path and the mixer circuit XT06a of the transmit signal path for direct down-conversion or direct up-conversion may be arranged. In some embodiments, the mixer circuit XT06a the received signal path and the mixer circuit XT06a of the transmit signal path for a superheterodyne function.
  • In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternative embodiments, the RF circuits XT06 analog-to-digital converter ( ADC ) and digital-to-analog converter ( DAC ) Circuits and the baseband circuits XT04 can contain a digital baseband interface to interface with the rf circuits XT06 to communicate.
  • In some dual-mode embodiments, a separate radio IC circuit may be provided to process signals for each spectrum, although the scope of the embodiments is not so limited.
  • In some embodiments, the synthesizer circuit XT06d a fractional-N synthesizer or a fractional one N / N + 1 Synthesizer, although the scope of the embodiments is not limited in this respect, since other types of frequency synthesizers may be suitable. For example, the synthesizer circuit XT06d a delta sigma synthesizer, a frequency multiplier or a synthesizer comprising a phase-locked loop with a frequency divider.
  • The synthesizer circuit XT06d may be configured to have an output frequency for use by the mixer circuit XT06a the RF circuit XT06 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuit XT06d a fractional one N / N + 1 Be synthesizer.
  • In some embodiments, the frequency input may be controlled by a voltage controlled oscillator ( VCO ), but this is not a requirement. The divider control input may be through the baseband circuitry XT04 or the application circuit XT02 be provided, depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel provided by the application circuit XT02 is specified.
  • The synthesizer circuit XT06d the RF circuits XT06 can use a divider, a delay-locked loop ( DLL ), a multiplexer and a phase accumulator. In some embodiments, the divider may comprise a dual modulus divider ( DMD ) and the phase accumulator is a digital phase accumulator ( DPA ) be. In some embodiments, the DMD be configured to input signal through N or N + 1 to divide (eg, based on execution) to provide a fractional divide ratio. In some example embodiments, the DLL a set of cascaded adjustable delay elements, a phase detector, a charge pump, and a type flip-flop D contain. In these embodiments, the delay elements may be configured to divide a VCO period into Nd equal phase packets, where Nd is the number of delay elements in the delay line. This is how the DLL a negative feedback is available to help ensure that the entire delay through the delay line is a VCO cycle.
  • In some embodiments, the synthesizer circuit XT06d be configured to produce a carrier frequency as the output frequency, while in other embodiments the output frequency may be a multiple of the carrier frequency (eg twice the carrier frequency, four times the carrier frequency) and used in conjunction with the quadrature generator and the divider circuit to provide multiple To generate signals with the carrier frequency with several different phases in relation to each other. In some embodiments, the output frequency may be an LO frequency ( LO ) be. In some embodiments, the RF circuits XT06 contain an IQ / polar converter.
  • FEM circuits XT08 may include a receive signal path that may include circuitry configured to operate with RF signals received from one or more antennas XT10 received, the received Amplify signals and the amplified versions of the received signals for the RF circuits XT06 to provide for further processing. FEM circuits XT08 may also include a transmit signal path that may include circuitry configured to amplify signals for transmission transmitted by RF circuitry XT06 for transmission through one or more of the one or more antennas XT10 provided. In various embodiments, the gain through the transmit or receive signal paths may be unique in the RF circuit XT06 , only in the FEM circuit XT08 or in the RF circuit XT06 and the FEM circuit XT08 respectively.
  • In some embodiments, the FEM circuit XT08 a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuit XT08 may include a receive signal path and a transmit signal path. The received signal path of the FEM circuit can be a LNA to amplify received RF signals and provide the amplified RF signals as output (eg, to the RF circuit XT06 ). The transmission signal path of the FEM circuit XT08 can a power amplifier ( PA ) to receive the input RF signals (eg, through the RF circuit XT06 provided) and one or more filters for generating RF signals for subsequent transmission (eg, through one or more of the one or more antennas XT10 ).
  • In some embodiments, the PMC XT12 Manage the performance of the baseband circuits XT04 provided. In particular, the PMC XT12 control power source selection, voltage scaling, battery charging, or GS to GS conversion. Of the PMC XT12 can often be included when the device XT00 is able to be operated by a battery, for example, when the device in a UE is included. Of the PMC XT12 can increase the power conversion efficiency while providing desirable conversion size and heat dissipation characteristics.
  • 9 shows the PMC XT12 only with the baseband circuit XT04 connected. In other embodiments, the PMC XT12 however, still or instead with other components, such as, but not limited to, the application circuitry XT02 , the RF circuit XT06 or the FEM circuit XT08 , be connected and perform similar power management functions for these.
  • In some embodiments, the PMC XT12 various energy saving mechanisms of the device XT00 control or otherwise be part of it. For example, if the device XT00 is in an RRC Connected state where it is still connected to the RAN node, as it expects to receive traffic soon, it may enter a state after a period of inactivity that is an interrupted receive mode ( DRX ) is known. During this state, the device can XT00 Switch off for a short period of time and thus save power.
  • If there is no data traffic activity for an extended period of time, the device may XT00 passed into a state RRC idle, where it disconnects from the network and does not perform functions such as channel quality feedback, handover, etc. The device XT00 switches to a very low power state and paging, waking up periodically to listen to the network and then turn off again. The device XT00 in this state may not receive data to receive data, it must go back to the RRC connected state.
  • Another energy saving mode may allow a device to be unavailable to the network for periods longer than one paging interval (from seconds to several hours). During this time, the device is completely inaccessible to the network and can completely shut down. All data sent during this time has a large delay and it is assumed that this delay is acceptable.
  • Processors of application circuits XT02 and processors of baseband circuits XT04 can be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuits XT04 Used alone or in combination to functions by level 3 , Level 2 or level 1 while processors of the application circuits XT04 Use data (such as packet data) received from these levels and also the function of level 4 (for example, transmission communication protocol (e.g. TCP ) and User Datagram Log ( UDP ) Levels). As mentioned herein, level can be 3 a radio resource control ( RRC ) Level, which is described in more detail below. As mentioned herein, level can be 2 a medium access control ( MAC ) Level, a radio link control ( RLC ) Level and a Packet Data Convergence Protocol ( PDCP ) Level, as described in more detail below. As mentioned herein, level can be 1 a physical ( PHY ) Level of a UE / RAN node, described in more detail below.
  • 10 illustrates exemplary interfaces of baseband circuits according to some embodiments. As explained above, the baseband circuit XT04 out 9 processors XT04A to XT04E and a memory XT04G which the processors use. Each of the processors XT04A to XT04E can each have a memory interface, XU04A to XU04E included to data to / from the memory XT04G to send / receive.
  • The baseband circuits XT04 may further include one or more interfaces to communicate with other circuitry / devices, such as a memory interface XU12 (eg one Interface for sending / receiving data to / from memory outside baseband circuits XT04 ), an application interface XU14 (eg, an interface for sending / receiving data to / from the application circuit XT02 from 9 ), an RF circuit interface XU16 (eg, an interface for sending / receiving data to / from the RF circuit XT06 from 9 ), a wireless hardware connectivity interface XU18 (eg an interface for sending / receiving data to / from Near Field Communication ( NFC ) Components, Bluetooth® components (eg Bluetooth® Low Energy), Wi-Fi® components and other communication components), and a performance management interface XU20 (eg, an interface to send / receive power or control signals to / from the PMC XT12 ).
  • 11 FIG. 10 is an illustration of a control plane protocol stack according to some embodiments. FIG. In this embodiment, a control plane XV00 as a communication protocol stack between the UE XS01 (or alternatively the UE XS02 ), the RAN node XS11 (or alternatively, the RAN node XS12 ), and the MME XS21 shown.
  • The PHY location XV01 can provide information by the MAC location XV02 send or receive over one or more air interfaces. The PHY location XV01 Further, a link adaptation or adaptive modulation and coding ( AMC ), Power control, cell search (eg, for initial synchronization and handover purposes), and other measurements used by higher layers, such as the RRC layer XV05 , The PHY location XV01 can continue error detection on the transport channels, "Forward Error Correction" - ( FEC ) Transport channel coding / decoding, physical channel modulation / demodulation, interleaving, rate matching, assignment to physical channels, and multiple input multiple output ( MIMO ) Execute antenna processing.
  • The MAC location XV02 can an association between the logical channels and transport channels, multiplexing of MAC service data units ( SDUs ) of one or more logical channels on transport blocks ( TB ), which via transport channels PHY demultiplexing of MAC SDUs to one or more logical channels of transport blocks ( TB ) supplied by PHY via transport channels, multiplexing of MAC on TBs , Planning information reporting, error correction by hybrid automatic repeat request ( HARQ ), and perform logical channel prioritization.
  • The RLC location XV03 can run in several operating modes, including: Transparent mode ( TM ), unacknowledged mode ( AROUND ) and confirmed mode ( AT THE ). The RLC location XV03 can be a transmission of protocol data units ( PDUs ) of the upper layer, error correction by automatic repeat request ( ARQ ) for AM data transfers and chaining, segmentation and reassembly of RLC SDUs for AROUND and AM data transfers. The RLC location XV03 can also perform a resegmentation of the RLC data PDUs for AM data transfers, RLC data PDUs for AROUND and reorder AM data transfers, duplicate data for AROUND Detect AM and AM data transfers, discard RLC SDUs for UM and AM data transfers, detect protocol errors for AM data transfers, and perform RLC rebuild.
  • The PDCP location XV04 can perform header compression and decompression of IP data, PDCP sequence numbers ( SNs ), perform in-sequence delivery of upper layer PDUs in lower layer reconstruction, eliminate duplicates of lower layer SDUs in rebuilding the lower layers for radio bearers associated with RLC AM, cipher and decipher control plane data, integrity protection, and integrity verification perform the control plane data, control timebased discard of data, and perform security operations (eg, ciphering, deciphering, integrity protection, integrity verification, etc.).
  • The main services and features of the RRC location XV05 For example, the broadcast of system information (eg, from master information blocks (MIBs) or system information blocks (SIBs) connected to the inaccessible stratum (NAS)), broadcast of system information associated with the access stratum (AS), paging, setup, Receipt and release of a RRC connection between the UE and E-UTRAN (eg RRC connection paging, RRC connection setup, RRC connection change and RRC connection release), setup, configuration, maintenance and release of point-to-point Radio bearers, security features including key management, Inter Radio Access Technology (RAT) mobility and metering configuration for UE metering reports included. The MIBs and SIBs may comprise one or more information elements (IEs), each of which may comprise individual data fields or data structures.
  • The UE XS01 and the RAN node XS11 For example, a Uu interface (eg, an LTE Uu interface) may be used to exchange control plane data over a protocol stack containing the PHY location XV01 , the MAC location XV02 , the RLC location XV03 , the PDCP location XV04 , and the RRC location XV05 includes.
  • The Non-Accessional Stream (NAS) protocols XV06 form the highest stratum of the control plane between the UE XS01 and the MME XS21 , The NAS protocols XV06 support the mobility of UE XS01 and the session management procedures for establishing and maintaining IP connectivity between the UE XS01 and P-GW XS23 ,
  • The S1 Application log ( S1 - AP ) Location XV15 can the functions of S1 Interface and elementary procedures ( EPs ). An EP is a unit of interaction between the RAN node XS11 and CN XS20 , The S1 AP layer services may include two groups: UE-associated services and non-UE-associated services. These services perform functions including but not limited to E-UTRAN Radio Access Bearer (E-RAB) Management, UE Capability Indicator, Mobility, NAS Signaling Transport, RAN Information Management ( RIM ) and configuration transfer.
  • The "Stream Control Transmission Protocol" (SCTP) layer (alternatively referred to as the SCTP / IP layer) XV14 can provide reliable delivery of signaling messages between the RAN node XS11 and the MME XS21 partly based on the IP protocol and supported by the IP location XV13 to ensure. The L2 -Location XV12 and L1 location XV11 may refer to communication links (eg, wired or wireless) used by the RAN node and the MME to exchange information.
  • The RAN node XS11 and the MME XS21 can one S1 -MME interface to exchange control plane data through a protocol stack that specifies the Ll location XV11 , the L2 -Location XV12 , the IP location XV13 , the SCTP location XV14 and the S1 -AP location XV15 includes.
  • 12 FIG. 10 is an illustration of a user-level protocol stack according to some embodiments. FIG. In this embodiment, a user level XW00 as a communication protocol stack between the UE XS01 (or alternatively the UE XS02 ), the RAN node XS11 (or alternatively, the RAN node XS12 ), the S-GW XS22 and the P-GW XS23 shown. The user level XW00 can use at least some of the same protocol layers as the control plane XV00 , For example, the UEs XS01 and the RAN node XS11 use a Uu interface (eg, an LTE Uu interface) to swap user-level data over a protocol stack containing the PHY location XV01 , the MAC location XV02 , the RLC location XV03 , the PDCP location XV04 includes.
  • The "General Packet Radio Service" - ( GPRS ) User level tunneling protocol ( GTP-U ) Location XW04 can be used to carry user data within the GPRS core network and between the radio access network and the core network. The transport user data may be, for example, packets in one of the formats IPv4, IPv6 or PPP. The UDP and IP Security ( UDP / IP ) Location XW03 can provide checksums for data integrity, port numbers for addressing various functions at the source and destination, and encryption and authentication on the selected data flows. The RAN node XS 11 and S-GW XS22 can a S1 Use the U interface to exchange user-level data through a protocol stack that specifies the L1 location XV11 , the L2 -Location XV12 , the UDP / IP location XW03 and the GTP-U location XW04 includes. Of the S-GW XS22 and P-GW XS23 can use an S5 / S8a interface to exchange user-level data through a protocol stack that uses the L1 location XV11 , the L2 -Location XV12 , the UDP / IP location XW03 and the GTP-U location XW04 includes. As above regarding 11 explained, the NAS protocols support the mobility of the UE XS01 and the session management procedures for establishing and maintaining IP connectivity between the UE XS01 and P-GW XS23 ,
  • 13 illustrates components of a core network according to some embodiments. The components of CN XS20 may be implemented in a physical node or in separate physical nodes that include components for reading and executing instructions from a machine-readable or computer-readable medium (eg, a non-transitory machine-readable storage medium). In some embodiments, the "Network Functions Virtualization" ( NFV ) are used to virtualize any or all of the network node functions described above via executable instructions stored in one or more computer readable storage media (described in more detail below). A logical instantiation of the CN XS20 can act as a network disk XX01 be designated. A logical instantiation of a section of the CN XS20 can as a grid washer XX02 be denoted (eg the power sub-disk XX02 is represented as the PGW XS23 and PCRF XS26 containing).
  • NFV architectures and infrastructures can be used to virtualize one or more network functions, alternatively performed by proprietary hardware, on physical resources that contain a combination of industry standard server hardware, storage hardware, or switches. In other words, NFV systems can be used to perform virtual or reconfigurable conversions of one or more EPC components / functions.
  • 14 FIG. 10 is a block diagram illustrating components according to some example embodiments of a system. FIG XY00 in support of NFV illustrated. The system XY00 is considered a virtualized infrastructure manager ( VIM ) XY02 , a network function virtualization infrastructure ( NFVI ) XY04 , a VNF manager ( VNFM ) XY06 , virtualized network functions ( VNFs ) XY08 , one Element manager ( EM ) XY10 , an NFV Orchestrator ( NFVO ) xy12 , and a network manager ( NM ) XY14 containing shown.
  • Of the VIM XY02 manages the resources of NFVI XY04 , The NFVI XY04 can contain physical or virtual resources and applications (including hypervisors) that are used to drive the system XY00 perform. Of the VIM XY02 can use the lifecycle of virtual resources with the NFVI XY04 manage (for example, creating, maintaining, and canceling virtual machines ( VMs , which are associated with one or more physical resources), track VM instances, track performance, errors and security of VM instances and associated physical resources and disclose VM instances and associated physical resources to other management systems.
  • Of the VNFM XY06 can the VNFs XY08 manage. The VNFs XY08 can be used to execute EPC components / functions. Of the VNFM XY06 can the life cycle of VNFs XY08 manage and the performance, errors and security of the virtual aspects of the VNFs XY08 follow. Of the EM XY10 can reduce the performance, errors and safety of the functional aspects of VNFs XY08 follow. The tracking data of VNFM XY06 and EM XY10 For example, power measurement ( PM ) Contain data by the VIM XY02 or the NFVI XY04 be used. Of the VNFM XY06 and the EM XY10 Both can be the amount of VNFs of the system XY00 up or downscale.
  • Of the NFVO xy12 can resources the NFVI XY04 coordinate, authorize, share, and connect to provide the requested service (eg, to perform an EPC function, component, or disk). Of the NM XY14 can provide a package of end user functions with the responsibility for managing a network, including network elements VNFs , non-virtualized network features, or both (management of VNFs can over the EM XY10 respectively).
  • 15 FIGURE 10 is a block diagram illustrating components in accordance with some example embodiments that are capable of reading instructions from a machine-readable or computer-readable medium (eg, a non-transitory machine-readable storage medium) and executing any one or more of the methodologies discussed herein. In particular shows 15 a diagrammatic representation of hardware resources XZ00 including one or more processors (or cores) XZ10 , one or more storage / storage media devices XZ20 , and one or more communication resources XZ30 , each communicatively via a bus XZ40 can be connected. For embodiments in which node virtualization (e.g. NFV ) can be a hypervisor XZ02 to provide an execution environment for one or more network disks / subwindows to the hardware resources XZ00 to use.
  • The processors XZ10 (eg a central processing unit ( CPU ), a reduced instruction set computing ( RISC ) Processor, a Complex Instruction Set Computing ( CISC ) Processor, a graphics processor unit ( GPU ), a digital signal processor ( DSP ) such as a baseband processor, an application specific integrated circuit ( ASIC ), a radio-frequency integrated circuit ( RFIC ), another processor or any suitable combination thereof) may, for example, be a processor XZ12 and a processor XZ14 contain.
  • The storage / storage media devices XZ20 may include main memory, disk storage, or any suitable combination thereof. The storage / storage media devices XZ20 may include any type of volatile or nonvolatile memory, such as dynamic random access memory (DRAM), static random access memory (FIG. SRAM ), erasable programmable memory with read only access ( EPROM ), electrically erasable programmable memory with read only access ( EEPROM ), Flash memory, solid state memory, etc., but are not limited to this.
  • The communication resources XZ30 may include connection or network interface components or other suitable devices for interfacing with one or more peripheral devices XZ04 or one or more databases XZ06 over a network XZ08 to communicate. For example, the communication resources XZ30 wired communication components (for example, for connection via a Universal Serial Bus ( USB )), cellular communication components, NFC components, Bluetooth® components (eg Bluetooth® Low Energy), Wi-Fi® components and other communication components.
  • instructions XZ50 may include software, a program, an application, an applet, an app, or other executable code to at least any one of the processors XZ10 to initiate one or more of any of the methodologies discussed herein. The instructions XZ50 may be completely or partially within at least one of the processors XZ10 (eg within the cache memory of the processor), the memory / storage medium devices XZ20 , or a suitable combination thereof. All can continue Sections of instructions XZ50 on the hardware resources XZ00 be transferred from any combination of peripheral devices XZ04 or the databases XZ06 , Accordingly, the memory of the processors XZ10 , the storage / storage media devices XZ20 , the peripheral devices XZ04 , and the databases XZ06 Examples of computer-readable and machine-readable media.
  • Example 1 is a user equipment ( UE ) for operation in a cellular mobile network, the radio access network ( RAN ) of the cellular mobile network connections with many different types of core networks ( CNs ) that offers UE the RAN a first type CN from the several different types CNs is to indicate to which it wishes to send a registration request, the UE, based on the receipt of a denial of registration with a particular deny reason, determines that it is not allowed to subscribe to the first type CN to register, a second type CN from the several different types CNs selects, and a registration method for the second type CN initiates.
  • Example 2 is the UE of Example 1 or another example herein, where the first type CN is a "5th Generation Core Network" ( 5GC ) and the second type CN is an Evolved Packet Core (EPC).
  • Example 3 is the UE of Example 2 or another example herein, wherein the UE your request to send the registration request to the 5GC by including one N1 Ability indicator in the signaling to the RAN displays.
  • Example 4 is the UE according to Example 1 or another example herein, wherein the RAN is an Evolved Universal Mobile Telecommunication System Terrestrial Radio Access Network (E-UTRAN).
  • Example 5 is the UE according to Example 1 or another example herein, wherein the UE in the system information broadcast of the RAN receives an indication indicating which types CNs the RAN offers a connection.
  • Example 6 is the UE according to Example 1 or another example herein, wherein the protocol that the UE used to be with the first type CN is different from the protocol the UE uses to log in to the second type CN to register.
  • Example 7 is the UE Example 1 or another example herein, wherein in certain cells of the RAN a connection with only one type CN can be offered.
  • Example 8 is the UE of Example 7 or another example herein, where if the only type CN with which the RAN offers a connection, the first type CN is the UE trying to find another cell that is connecting to another type CN offering.
  • Example 9 is a cellular mobile network where the radio access network ( RAN ) of the cellular mobile network connections with many different types of core networks ( CNs ) in order to receive user equipment ( UE ) a registration request via the RAN for a first guy CN of the several different types CNs to receive, to determine that it is the UE is not allowed to join the first guy CN and reject the registration request with a specific reason for refusal, which the UE indicating that they are over that RAN a registration procedure for another type CN of the several different types CNs can initiate.
  • Example 10 is a user equipment ( UE ) for operation in a cellular mobile network, the radio access network ( RAN ) of the cellular mobile network connections with many different types of core networks ( CNs ) that offers UE a registration via a first radio access technology ( ADVICE ) with a first type CN of the several different types CNs should prefer, the UE based on receiving a registration rejection over a second one ADVICE with a specific reason for refusing to change their configuration so that they have the registration over the first one ADVICE with a second type CN of the several different types CNs prefers.
  • Example 11 is the UE Example 10 or another example herein, wherein the first ADVICE a "Third Generation Partnership Project" - ( 3GPP ) "Evolved Universal Mobile Telecommunication System Terrestrial Radio Access Network" (E-UTRAN), the first type CN is a "5th Generation Core Network" ( 5GC ) is the second type ADVICE one 3GPP "New Radio" ( NO ), and the second type CN is an "Evolved Packet Core" ( EPC ).
  • Example 12 is the UE according to example 10 or another example herein, wherein when the UE registers the registration via a first radio access technology ( ADVICE ) with a first type CN of the several different types CNs, the cells selection cells and cell reselection cells that offer a connection with the first type CN preferred over cells that offer only a connection with the second type CN.
  • Example 13 is the UE according to Example 10, wherein, if the registration via a first radio access technology ( ADVICE ) with a second type CN out of the several different types of CNs, the UE should use cell selection and cell reselection cells that are connected to the first type CN offer preference over cells that only connect to the first type CN to offer.
  • Example 14 may include an apparatus comprising means for carrying out one or more elements of a method described or associated with any one of Examples 1 to 13, or another method or process described herein.
  • Example 15 may include one or more non-transitory computer readable media including instructions to cause the electronics device to execute one or more elements of a method as described in any one of Examples 1 to 13 when executing the instructions by one or more processors of an electronic device or any other process or process described herein.
  • Example 16 may include a device that includes logic, modules, or circuitry to perform one or more elements of a method described or associated with any of Examples 1 through 13, or another method or process that which is described herein.
  • Example 17 may include a method, technique or process as described or associated with any of Examples 1 to 13, or portions or portions thereof.
  • Example 18 may include an apparatus comprising: one or more processors and one or more computer readable media including instructions that, when executed by the one or more processors, cause the one or more processors, method, techniques, or method Process as described in or associated with any of Examples 1 to 13, or portions thereof.
  • Example 19 may include a signal as described in or related to any of Examples 1 to 13, or portions or portions thereof.
  • Example 20 may include a signal in a wireless network as shown and described herein.
  • Example 21 may include a method for communicating in a wireless network, as illustrated and described herein.
  • Example 22 may include a system for providing wireless communication, as illustrated and described herein.
  • Example 23 may include an apparatus for providing wireless communication, as illustrated and described herein.
  • Example 24 may include one or more computer readable media upon which instructions are stored, the instructions being responsive to execution by user equipment (e.g. UE ) the UE cause a registration request to be sent to a network to identify a registration denial message received from the network in response to the registration request, the registration denial message including an indication that the N1 Mode is not allowed, and the N1 Disable mode radio capability based on the display.
  • Example 25 may include the computer-readable medium of Example 24 or another example herein, wherein the instructions respond to the execution by the UE UE further induce a Public Land Mobile Network ( PLMN ) Identity ( ID ) associated with the registration denial message, and to trigger the storage of the PLMN ID as in a list of PLMNs in which the N1 Mode is not allowed.
  • Example 26 may include the computer-readable medium of Example 25 or another example herein, which instructions, in response to execution by the UE further cause the PLMN-ID to be removed from the list of PLMNs is deleted when the UE is switched off, or when a time interval expires.
  • Example 27 may include the computer-readable medium of Example 25 or another example herein, the instructions being implemented in response to execution by the UE further cause the UE the initialization of subsequent registration requests to use a N1 Interface of a PLMN which is associated with the PLMN-ID.
  • Example 28 may include the computer-readable medium of any one of Examples 24 to 27 or another example herein, wherein transmission to the network includes transmission to an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access Network (E-UTRAN) access point. and wherein the E-UTRAN access point is equipped with a "Fifth Generation Core Network" ( 5GC ) and an "Evolved Packet Core" ( EPC ) connected is.
  • Example 29 may include the computer-readable medium of Example 28 or another example herein, which instructions, in response to execution by the UE further cause the UE to generate a second registration request for transmission to the E-UTRAN access point after the UE the N1 Mode capability, where the second registration request is an attachment request for an EPC non-access NAS ) for registration with the EPC includes.
  • Example 30 may include the computer-readable medium of any of Examples 24 to 27 or another example herein, wherein the registration request includes an indication that the UE has a N1 Mode capability.
  • Example 31 may include a device for user equipment ( UE ), comprising a circuit for generating a registration request for transmission to a network, identifying a registration denial message received from the network in response to the registration request, the registration denial message including an indication that the N1 Mode is not allowed, and disable the N1 Mode capability based on the display, and memory for storing the registration request.
  • Example 32 may include the device of Example 31 or another example herein, the circuit further comprising a Public Land Mobile Network (FIG. PLMN ) Identity ( ID ), which is associated with the registration denial message, and should cause the PLMN ID in a list of PLMNs is stored in which the N1 Mode is not allowed.
  • Example 33 may include the device of Example 32 or another example herein, the circuit further including the PLMN ID should delete from the list of PLMNs if the UE is switched off or a time interval expires.
  • Example 34 may include the apparatus of Example 32 or another example herein, wherein the circuitry further includes initiating subsequent registration requests for use of a N1 Interface of a PLMN which is associated with the PLMN-ID should avoid.
  • Example 35 may include the apparatus of any of Examples 31-34 or another example herein, wherein transmission to the network includes transmission to an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access Network (E-UTRAN) access point, and the E-UTRAN access point having a "Fifth Generation Core Network" ( 5GC ) and an "Evolved Packet Core" ( EPC ) is coupled.
  • Example 36 may include the apparatus of Example 35 or another example herein, wherein the circuit is further to generate a second registration request for transmission to the E-UTRAN access point after the UE initiates the transmission N1 Mode capability, wherein the second registration request comprises an attachment request for an EPC Disconnect Stream (NAS) for registration with the EPC.
  • Example 37 may include the device of any of Examples 31-34 or another example herein, wherein the registration request includes an indication that the UE has a N1 Mode capability.
  • Example 38 may include one or more computer readable media upon which instructions are stored, which instructions, in response to execution by an access point, cause the access point to identify a registration request made by a user equipment ( UE ), to determine that the registration request is not by a "Fifth Generation Core Network" ( 5GC ) and the transfer of a registration denial to the UE with the registration deny indicating that the N1 Mode is not allowed.
  • Example 39 may include the computer readable medium of example 38 or another example herein, wherein the determination that the registration request is made by the 5GC is not accepted contains the registration request to an access and mobility management function ( AMF ), and those of the AMF to identify received registration rejection.
  • Example 40 may include the computer-readable medium of any of examples 38 or 39 or another example herein, wherein the determination that the registration request is made by the 5GC is not accepted, the provision that the registration request by the 5GC is not accepted, based on subscription information provided with the UE are associated with.
  • Example 41 may include the computer-readable medium of any of examples 38 or 39 or another example herein, wherein the instructions in response to execution by the access point further cause the access point to identify a port request received from the UE, wherein the port request none 5GC requested message and sends the connection request to a mobility management entity (MME).
  • Example 42 may include the computer-readable medium of any of Examples 38 or 39 or another example herein, wherein the access point is an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access Network (E-UTRAN) access point, and wherein the E-UTRAN Access point with a "Fifth Generation Core Network" ( 5GC ) and an "Evolved Packet Core" (EPC).
  • Example 43 may include the computer-readable medium of Example 42 or another example herein, where the E-UTRAN access point is an evolved NodeB (eNB).
  • Example 44 may include an access point device including a circuit for identifying a registration request made by a user equipment ( UE determining that the registration request was made by a "Fifth Generation Core Network" ( 5GC ) is not accepted, and causing the transfer of a registration denial to the UE , where the registration rejection indicates that the N1 Mode is not allowed, and memory for storing the registration request and refusal rejection.
  • Example 45 may include the apparatus of Example 44 or another example herein, wherein the determination that the registration request is by the 5GC is not accepted contains the registration request to an access and mobility management function ( AMF ), and those of the AMF to identify received registration rejection.
  • Example 46 may include the device of any of Examples 44 or 45 or another example herein, wherein the determination that the registration request is made by the 5GC is not accepted, the provision that the registration request by the 5GC is not accepted based on subscription information associated with the UE.
  • Example 47 may include the device of any of Examples 44 or 45 or another example herein, which circuit is further to identify a port request that is being used by the UE was received, the connection request no 5GC requested message, and the connection request to a mobility management entity ( MME ) should send.
  • Example 48 may include the device of any of Examples 44 or 45 or another example herein, wherein the access point is an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access Network (E-UTRAN) access point, and wherein the E-UTRAN is Access point with a "Fifth Generation Core Network" ( 5GC ) and an "Evolved Packet Core" (EPC).
  • Example 49 may include a user equipment (UE) method, comprising causing the UE to generate a registration request for transmission to a network, identifying or causing a registration denial message included by the network in response to the registration request , wherein the registration reject message includes an indication that the N1 Mode is not allowed, and the N1 Disable mode radio capability based on the display.
  • Example 50 may include the method of Example 49 or another example herein, further comprising UE to induce a Public Land Mobile Network ( PLMN ) Identity ( ID ), which is associated with the registration denial message, and cause the PLMN ID to appear as in a list of PLMNs is stored in which the N1 Mode is not allowed.
  • Example 51 may include the method of Example 50 or another example herein, further comprising causing the PLMN ID from the list of PLMNs is deleted when the UE is switched off or a time interval expires.
  • Example 52 may include the method of Example 50 or another example herein, further comprising UE to initiate subsequent registration requests for the use of a N1 Interface of a PLMN to avoid that with the PLMN ID is associated.
  • Example 53 may include the method of any of Examples 49-52 or another example herein, wherein transmission to the network includes transmission to an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access Network (E-UTRAN) access point, and the E-UTRAN access point having a "Fifth Generation Core Network" ( 5GC ) and an "Evolved Packet Core" ( EPC ) connected is.
  • Example 54 may include the method of Example 53 or another example herein, further comprising UE to generate a second registration request for transmission to the E-UTRAN access point after the UE the N1 Mode radio capability, the second registration request being a connection request for a EPC Non-access stratum ( NAS ) for registration with the EPC includes.
  • Example 55 may include the method of any of Examples 49 to 52 or another example herein, wherein the registration request includes an indication that the UE a N1 Mode capability.
  • Example 56 may include a method for user equipment ( UE comprising generating or causing the generation of a registration request for transmission to a network, identifying or causing identification of a registration denial message received from the network in response to the registration request, the registration revocation message including an indication that of the N1 Mode is not allowed, and disabling or causing the deactivation of the N1 Mode capability based on the display, and storing or causing the storing of the registration request.
  • Example 57 may include the method of Example 56 or another example herein, further comprising identifying or causing the identification of a "Public Land Mobile Network" - ( PLMN ) Identity ( ID ) associated with the registration denial message and causing the PLMN ID to be stored in a list of PLMNs in which the N1 Mode is not allowed.
  • Example 58 may include the method of Example 57 or another example herein, further comprising deleting or causing the deletion of the PLMN-ID from the list of PLMNs , if the UE is switched off or a time interval expires.
  • Example 59 may include the method of Example 57 or another example herein, further comprising avoiding or causing avoidance of initiating subsequent registration requests for the use of N1 Interface of a PLMN that with the PLMN ID is associated.
  • Example 60 may include the method of any of Examples 56-59 or another example herein, wherein transmission to the network is transmission to an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access Network ( E-UTRAN ) And the E-UTRAN access point having a "Fifth Generation Core Network" ( 5GC ) and an "Evolved Packet Core" ( EPC ) is coupled.
  • Example 61 may include the method of example 60 or another example herein, further comprising generating or causing the generation of a second registration request for transmission to the E-UTRAN access point after the UE initiates the N1 Mode capability, where the second registration request is an attachment request for an EPC non-access NAS ) for registration with the EPC includes.
  • Example 62 may include the method of any one of Examples 56 to 59 or another example herein, wherein the registration request includes an indication that the UE a N1 Mode capability.
  • Example 63 may include a method for an access point, including identifying or causing the identification of a registration request made by a user equipment ( UE ), determining or causing the determination that the registration request is made by a "Fifth Generation Core Network" ( 5GC ) is not accepted, and causing the transfer of a registration denial to the UE , where the registration rejection indicates that the N1 Mode is not allowed.
  • Example 64 may include the method of Example 63 or another example herein, wherein determining or causing the determination that the registration request is made by the 5GC is not accepted, the forwarding or causing the forwarding of the registration request to an access and mobility management function ( AMF ), and the identification or the cause of the identification of the AMF received registration rejection.
  • Example 65 may include the method of any one of Examples 63 or 64 or another example herein, wherein determining or causing the determination that the registration request is made by the 5GC is not accepted, the determination or making the provision that the registration request by the 5GC is not accepted based on subscription information provided with UE are associated with.
  • Example 66 may include the method of any one of examples 63 or 64 or another example herein, further comprising identifying or causing identification of a connection request made by the UE was received, the connection request no 5GC requested message and sending or causing the connection request to be sent to a mobility management entity ( MME ).
  • Example 67 may include the method of any of Examples 63 or 64 or another example herein, wherein the access point is an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access Network (E). UTRAN) access point, and wherein the E-UTRAN access point is equipped with a "Fifth Generation Core Network" ( 5GC ) and an "Evolved Packet Core" (EPC).
  • Example 68 may include the method of Example 67 or another example herein, wherein the E-UTRAN access point is an evolved NodeB (eNB).
  • Example 69 may include a method for an access point comprising identifying or causing the identification of a registration request received from user equipment (UE), determining or making the determination that the registration request is through a "Fifth Generation Core Network". ( 5GC ), causing the transmission of a registration denial to the UE, the registration denial indicating that the N1 Mode is not allowed, and saving or causing the saving of the registration request and refusal rejection.
  • Example 70 may include the method of Example 69 or another example herein, wherein determining or causing the determination that the registration request has been made by the 5GC is not accepted, the forwarding or causing the forwarding of the registration request to an access and mobility management function (AMF), and the identification or causing the identification of the registration rejection received from the AMF.
  • Example 71 may include the method of any one of Examples 69 or 70 or another example herein, wherein determining or causing the determination that the registration request is made by the 5GC is not accepted, the determination or making the provision that the registration request by the 5GC is not accepted based on subscription information associated with the UE.
  • Example 72 may include the method of any of examples 69 or 70 or another example herein, further comprising identifying or causing the identification of a port request received from the UE, wherein the port request is no 5GC requested message and sending or causing the connection request to be sent to a mobility management entity (MME).
  • Example 73 may include the method of any of Examples 69 or 70 or another example herein, wherein the access point is an Evolved Universal Mobile Telecommunication System Terrestrial Radio Access Network (E-UTRAN) access point, and wherein the E-UTRAN Access point with a "Fifth Generation Core Network" ( 5GC ) and an "Evolved Packet Core" (EPC).
  • Example 74 may include an apparatus to perform the method of any of Examples 49 to 73 or another example herein.
  • Example 75 may include one or more agents to perform the method of any of Examples 49 to 73 or another example herein.
  • Example 76 may include one or more computer readable media upon which instructions are stored, which instructions, in response to execution by a device, cause the device to perform the method of any one of Examples 49 to 73 or another example herein.
  • It will be apparent to those skilled in the art that various modifications and variations can be made in the disclosed embodiments of the disclosed apparatus and associated methods without departing from the spirit or scope of the disclosure. Thus, it is intended that the present disclosure cover the modifications and variations of the above-disclosed embodiments, as long as the modifications and variations fall within the scope of any claims and their equivalents.
  • QUOTES INCLUDE IN THE DESCRIPTION
  • This list of the documents listed by the applicant has been generated automatically and is included solely for the better information of the reader. The list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions.
  • Cited patent literature
    • US 62544281 [0001]

Claims (25)

  1. Computer-readable medium or computer-readable media upon which instructions are stored, the instructions causing the UE in response to execution by user equipment (UE): to generate a registration request for transmission to a network; identify a registration denial message received from the network in response to the registration request, the registration denial message including an indication that the N1 mode is not allowed; and Disable the N1 mode capability based on the display.
  2. Computer readable medium after Claim 1 wherein the instructions in response to the execution by the UE further cause the UE: to identify a public land mobile network (PLMN) identity associated with the registration denial message, and cause the PLMN ID is stored as in a list of PLMNs in which the N1 mode is not allowed.
  3. Computer readable medium after Claim 2 wherein the instructions in response to the execution by the UE further cause the PLMN ID to be deleted from the list of PLMNs when the UE is powered down or when a time interval expires.
  4. Computer readable medium after Claim 2 wherein the instructions in response to the execution by the UE further cause the UE to avoid initializing subsequent registration requests to use an N1 interface of a PLMN associated with the PLMN-ID.
  5. Computer readable medium according to one of Claims 1 to 4 wherein the transmission to the network includes transmission to an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access Network (E-UTRAN) access point, and wherein the E-UTRAN access point is a fifth generation core network (5GC). and an "Evolved Packet Core" (EPC).
  6. Computer readable medium after Claim 5 wherein the instructions in response to the execution by the UE further cause the UE to generate a second registration request for transmission to the E-UTRAN access point after the UE has disabled the N1 mode capability, the second registration request requesting a connection request for an EPC Non-Accessible Root (NAS) for registration with the EPC.
  7. Computer readable medium according to one of Claims 1 to 4 wherein the registration request includes an indication that the UE has N1 mode capability.
  8. User equipment (UE) device comprising: a circuit to: to generate a registration request for transmission to a network; identify a registration denial message received from the network in response to the registration request, the registration denial message including an indication that the N1 mode is not allowed; and Disable N1 mode capability based on the display; and memory to store the registration request.
  9. Device after Claim 8 wherein: the circuit further: identifies a public land mobile network (PLMN) identity associated with the registration denial message and causes the PLMN ID to be stored as in a list of PLMNs in which the N1 mode is not allowed.
  10. Device after Claim 9 wherein the circuit is further to delete the PLMN-ID from the list of PLMNs when the UE is powered off or a time interval expires.
  11. Device after Claim 9 wherein the circuit is further to avoid initiating subsequent registration requests to use an N1 interface of a PLMN associated with the PLMN-ID.
  12. Device according to one of Claims 8 to 11 wherein the transmission to the network includes transmission to an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access Network (E-UTRAN) access point, and wherein the E-UTRAN access point is a fifth generation core network (5GC). and an "Evolved Packet Core" (EPC).
  13. Device after Claim 12 wherein the circuit is further to generate a second registration request for transmission to the E-UTRAN access point after the UE has disabled the N1 mode capability, the second registration request requesting an EPC non-access-point (NAS) attachment request for registration with the EPC includes.
  14. Computer readable medium according to one of Claims 8 to 11 the registration request an indication that the UE has N1 mode capability.
  15. Computer-readable medium or computer-readable media having instructions stored thereon, the instructions causing the access point in response to execution by an access point: identify a registration request received from user equipment (UE); to determine that the registration request is not accepted by a fifth-generation core network (5GC); and to cause a registration deny to be transmitted to the UE, wherein the denial indicates that the N1 mode is not allowed.
  16. Computer readable medium after Claim 15 wherein the determination that the registration request is not accepted by the 5GC includes: directing the registration request to an Access and Mobility Management Function (AMF); and identifying the registration denial received from the AMF.
  17. Computer readable medium according to one of Claims 15 or 16 wherein the determination that the registration request is not accepted by the 5GC includes the determination that the registration request is not accepted by the 5GC based on subscription information associated with the UE.
  18. Computer readable medium according to one of Claims 15 or 16 wherein the instructions in response to execution by the access point further cause the access point: to identify a connection request received from the UE, the connection request not including a display requested by the 5GC; and forwards the connection request to a mobility management entity (MME).
  19. Computer readable medium according to one of Claims 15 or 16 wherein the access point is an Evolved Universal Mobile Telecommunication System Terrestrial Radio Access Network (E-UTRAN) access point, and wherein the E-UTRAN access point has a fifth generation core network (5GC) and an evolved packet core "(EPC) is coupled.
  20. Computer readable medium after Claim 19 , where the E-UTRAN access point is an evolved NodeB (eNB).
  21. An access point device comprising: a circuit to: identify a registration request received from user equipment (UE); to determine that the registration request by a "Fifth Generation Core Network "(5GC) is not accepted; and cause a registration deny to be transmitted to the UE, the denial indicating that the N1 mode is not allowed; and a memory to store the registration request and denial refusal.
  22. Device after Claim 21 wherein the determination that the registration request is not accepted by the 5GC includes: directing the registration request to an Access and Mobility Management Function (AMF); and identifying the registration denial received from the AMF.
  23. Device according to one of Claims 21 or 22 wherein the determination that the registration request is not accepted by the 5GC includes the determination that the registration request is not accepted by the 5GC based on subscription information associated with the UE.
  24. Device according to one of Claims 21 or 22 wherein the circuit further identifies: a port request received from the UE, wherein the port request does not include a screen requested by the 5GC; and forwards the connection request to a mobility management entity (MME).
  25. Device according to one of Claims 21 or 22 wherein the access point is an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access Network (E-UTRAN) access point, and wherein the E-UTRAN access point has a fifth generation core network (5GC) and an evolved packet core "(EPC) is coupled.
DE112018000199.7T 2017-08-11 2018-08-07 Registration management for new radio Pending DE112018000199T5 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US201762544281P true 2017-08-11 2017-08-11
US62/544,281 2017-08-11
PCT/US2018/045534 WO2019032532A1 (en) 2017-08-11 2018-08-07 New radio registration management

Publications (1)

Publication Number Publication Date
DE112018000199T5 true DE112018000199T5 (en) 2019-10-17

Family

ID=63442780

Family Applications (1)

Application Number Title Priority Date Filing Date
DE112018000199.7T Pending DE112018000199T5 (en) 2017-08-11 2018-08-07 Registration management for new radio

Country Status (2)

Country Link
DE (1) DE112018000199T5 (en)
WO (1) WO2019032532A1 (en)

Also Published As

Publication number Publication date
WO2019032532A1 (en) 2019-02-14

Similar Documents

Publication Publication Date Title
JP5864750B2 (en) Method and apparatus for using a non-access layer procedure in a mobile station to access component carrier resources belonging to different radio access technologies
US20130303203A1 (en) Paging and system information broadcast handling in virtualized networks
EP2484171B1 (en) Determining establishment causes for emergency sessions
US20170339609A1 (en) Method and apparatus for determining pdu session identity in wireless communication system
CN103988531A (en) Methods for IP mobility management
CN103299700A (en) Methods and apparatus of integrating device policy and network policy for arbitration of packet data applications
CN104919855A (en) Method and terminal for determining handover for traffic offloaded onto wlan
CN102684755A (en) Mobile radio communication devices and servers
WO2013095000A1 (en) Network-initiated control method and apparatus for providing proximity service
US10271191B2 (en) Procedures to provision and attach a cellular internet of things device to a cloud service provider
WO2012154542A1 (en) Methods and apparatus for using control plane to transmit and receive data
WO2010098146A1 (en) Method for a communication node with a plurality of communication interfaces to notify dynamic path setup and associated apparatus thereof
EP2561707B1 (en) Supporting a multimedia application based on network zone recognition
CN105432117B (en) For assisting the selected Internet protocol traffic at evolved B node to unload the technology supported
US20190191295A1 (en) Cellular iot network architecture
EP3482602A1 (en) Systems, methods and devices for control-user plane separation for 5g radio access networks
US10484848B2 (en) Systems, methods, and devices for V2X services over wireless wide area networks
KR20180124033A (en) Network slicing behavior
US20190028943A1 (en) Mobility Management for Next Generation Mobile Network
CN102685921A (en) Dual-channel communication method and system
JP2018508139A (en) Method for supporting mobility management entity, user equipment and extended discontinuous reception mechanism
US9237589B2 (en) Method and apparatus for performing plural network attachment procedures to support plural connections in a wireless access system
US20190364541A1 (en) Method for selecting resource operation preferred by user in wireless communication system and device for same
DE112016004943T5 (en) Quality of service delivery framework for an SDN-based mobile network architecture
US20180376446A1 (en) De-registration method in wireless communication system and apparatus therefor