WO2019072904A1 - Notification d'informations sur un type de réseau central (cn) - Google Patents

Notification d'informations sur un type de réseau central (cn) Download PDF

Info

Publication number
WO2019072904A1
WO2019072904A1 PCT/EP2018/077578 EP2018077578W WO2019072904A1 WO 2019072904 A1 WO2019072904 A1 WO 2019072904A1 EP 2018077578 W EP2018077578 W EP 2018077578W WO 2019072904 A1 WO2019072904 A1 WO 2019072904A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
enodeb
network node
neighbor cell
epc
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.)
Ceased
Application number
PCT/EP2018/077578
Other languages
English (en)
Inventor
Parisa PAKNIAT
Gunnar Mildh
Icaro L. J. Da Silva
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.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of WO2019072904A1 publication Critical patent/WO2019072904A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/00835—Determination of neighbour cell lists
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H04W36/00692—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink using simultaneous multiple data streams, e.g. cooperative multipoint [CoMP], carrier aggregation [CA] or multiple input multiple output [MIMO]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node
    • H04W36/125—Reselecting a serving backbone network switching or routing node involving different types of service backbones
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/10—Access point devices adapted for operation in multiple networks, e.g. multi-mode access points

Definitions

  • FIG. 1 depicts various ways to deploy 5G network with or without interworking with existing LTE and EPC. Some of the various ways to deploy 5G network are depicted as "options" in FIG. 1.
  • a method of deploying the 5G network is referred to as "option 3" and called EN-
  • DC E-UTRAN-NR Dual Connectivity
  • LTE is a master node
  • NR is a secondary node.
  • the RAN node (gNB) supporting NR may not have a control plane connection to core network (e.g., EPC), and instead rely on the LTE as master node (MeNB).
  • EPC core network
  • MeNB master node
  • This may also called a "Non-stand-alone NR" and there is no 5GCN in this deployment.
  • the functionality of an NR cell may be limited to be used for connected mode UEs as a booster and/or diversity leg, and a UE may not camp on these NR cells in option 3.
  • option 2 may support stand-alone NR deployment where a gNB is connected to 5GCN.
  • LTE may also be connected to 5GCN as shown in option 5.
  • option 2 and option 5 both NR and LTE are seen as part of the NG-RAN which connects to 5GCN.
  • option 4 and option 7 may be other variants of dual connectivity between LTE and NR which will be standardized as part of NG-RAN connected to 5GCN, which are called MR-DC (Multi-Radio Dual Connectivity).
  • MR-DC Multi-Radio Dual Connectivity
  • FIG. 2 illustrates various interfaces used in the network corresponding to the different options described above.
  • the various interfaces depicted in FIG. 2 correspond to Figures 4.3.1.1-1 and Figures 4.3.2.2-1 of 3GPP TS37.340.
  • an X2 interface is used to support EN-DC between an LTE
  • MR-DC for 5GCN is however supported using the Xn protocol between LTE or NR MN node and LTE or NR SN node.
  • the X2 and Xn may also be used to support handovers, where the X2 may be used for intra-LTE handovers for UEs connected to EPC core network (CN), and the Xn may be used for handover within and between LTE and NR for UEs connected to 5GCN.
  • the SI and NG interfaces are used for intra-system handover between EPC and 5GCN.
  • a network node associated with an LTE cell may be connected to both a 5GCN and a EPC.
  • the perspective of UE connection there is only one core network involved where the UE is registered in. That is, either the EPC or the 5GC may be involved where the UE is registered in.
  • LTE-EPC capable e.g., compatibility with eNodeB-
  • LTE-5GC capable (e.g., compatibility with eNodeB-5GC network connection), and (iii) both LTE-5GC and LTE-EPC capable, among others.
  • NR there may be different capabilities for NR such as: (i) NR
  • the types of handovers or inter-DC setup that can be performed from NR towards LTE may depend on the above mentioned UE capabilities but may also depend on the CN that the LTE node is connected to.
  • the supported inter-node / mobility functionality depends on the CN that the UE is connected to, i.e., whether the CN is the same as the neighbor cell intended to be the target cell.
  • a neighbor cell for a given RAT when needs to be measured is known to be connected to a particular CN.
  • an LTE cell detected by the UE may be either connected to EPC or 5GC, it is ambiguous to the serving node receiving measurement reports associated to the LTE cell whether the LTE cell is connected to the EPC or the 5GC. That ambiguity can create problems to the serving node when deciding which action can be done.
  • receiving a measurement report associated to an LTE cell is not sufficient to enable the serving cell to know what actions may be taken based on the measurement reports because the actions may also depend on the CN type the LTE cell is connected to.
  • the network has no means to prioritize LTE neighbor cells connected to the same CN, which may also lead to improve mobility performance.
  • the above mentioned problems are mainly related to actions from the serving node towards the UE.
  • problems in terms of inter-node actions the serving node can take For example, it may not be possible to setup an X2 connectivity with the reported LTE cell which is connected to 5GC. Similarly, it may not be possible to setup an Xn connectivity with an LTE cell associated to an eNodeB connected to EPC.
  • the present disclosure is directed to a UE configured to report to a serving node CN type information indicating a type of CN to which an neighbor LTE cell (e.g., eNB) detected by the UE is connected.
  • the UE may transmit to the serving node a report comprising identification information identifying the detected neighbor LTE cell and further comprising CN type information indicating at least one of: i) that the detected neighbor LTE cell is connected to a CN of a first type (e.g., EPC) and ii) that the detected neighbor LTE cell is connected to a CN of a second type (e.g. 5GC).
  • a serving node CN type information indicating a type of CN to which an neighbor LTE cell (e.g., eNB) detected by the UE is connected.
  • the UE may transmit to the serving node a report comprising identification information identifying the detected neighbor LTE cell and further comprising CN type information indicating at least one of: i) that the detected neighbor
  • the UE may receive the CN type information via a cell broadcast channel, and later report this information to the serving cell.
  • the network node e.g., eNB
  • the network node responsible for the serving cell may then use this information to know if it should trigger a handover or not to the target cell, or setup Xn (or X2) relations to the target node or setup Dual Connectivity.
  • the UE may be configured by the network to receive and report the CN type information.
  • the UE may be configured: (i) by an eNB connected to 5GC; (ii) by a eNB connected to EPC or (iii) by an gNB connected to 5GC, among others.
  • UE related embodiments of the present application are realized by an enhanced CGI reporting functionality in which the UE is provided by the network with an LTE cell identifier (e.g. physical cell identifier (PCI)), and the UE uses the LTE cell identifier to acquire system information associated with that LTE cell identifier (by any system information acquisition method e.g. broadcasted or on demand) and reads the acquired system information to determine whether that LTE cell is connected to 5GC or EPC. Once that is done, the UE includes in a measurement report CN type information indicating either 5GC or EPC and sends to the serving node the measurement report.
  • LTE cell identifier e.g. physical cell identifier (PCI)
  • PCI physical cell identifier
  • the UE uses the LTE cell identifier to acquire system information associated with that LTE cell identifier (by any system information acquisition method e.g. broadcasted or on demand) and reads the acquired system information to determine whether that LTE cell is connected to 5GC or EPC
  • network related embodiments of the present application may be based on the reported information from the UE regarding which CN the reported LTE cell(s) is connected to. Accordingly, the serving network node may decide which type of interface it can setup with the detected neighbor LTE node (e.g. X2, Xn, etc.) and/or which kind of action towards the UE can be taken i.e. handovers, CA/DC setup (SCG addition), release and redirect, etc.
  • the serving network node may decide which type of interface it can setup with the detected neighbor LTE node (e.g. X2, Xn, etc.) and/or which kind of action towards the UE can be taken i.e. handovers, CA/DC setup (SCG addition), release and redirect, etc.
  • the present disclosure introduces new information in existing UE measurements on LTE.
  • the new information may include an indication whether a neighbor LTE cell is connected to 5GC and/or EPC. This new information facilitates mobility / ANR functionality in the network to assist RAN (eNB/gNB) with optimal decision making in different scenarios.
  • Advantages of the proposed solutions in the present disclosure include: (1) improved ANR functionality, (2) improved end user performance, and (3) simplified network management.
  • the improved ANR aims to provide neighbor cell relation information required in the eNB/gNB to assist different RAN decisions and actions, such as coverage triggered mobility, dual connectivity setup/modification, etc. Whether an LTE neighbor cell is connected to 5GC or EPC, is part of the required information for the eNB/gNB to initiate appropriate actions in different scenarios.
  • the current disclosure provides that if multiple LTE cells are reported and some of them are connected the same CN as the serving node, these should be prioritized. Hence, knowing which LTE cell is connected to which CN is beneficial for the serving node, in view of knowing that via wide network configuration can be cumbersome.
  • a method implemented in a wireless device is provided.
  • the method includes acquiring CN type information transmitted by a neighbor network node, wherein the CN type information indicates at least one of: i) that the neighbor network node is connected to a CN of a first type (e.g., an evolved packet core (EPC) network) and ii) that the neighbor network node is connected to a CN of a second type (e.g., a 5G core network (5GC)); and transmitting to a serving network node a report comprising identification information identifying the neighbor network node and core network type information indicating at least one of: i) that the identified neighbor network node is connected to a CN of the first type and ii) that the identified neighbor network node is connected to a CN of the second type.
  • a first type e.g., an evolved packet core (EPC) network
  • a second type e.g., a 5G core network (5GC)
  • a method performed by a serving network node for establishing an interface with a neighbor network node includes receiving a report transmitted by a wireless device, wherein the report comprises identification information identifying the neighbor network node and core network type information indicating at least one of: i) that the identified neighbor network node is connected to a CN of a first type (e.g. an EPC network) and ii) that the identified neighbor network node is connected to a CN of a second type (e.g., a 5GC network).
  • a first type e.g. an EPC network
  • a second type e.g., a 5GC network
  • a method performed by a network node includes transmitting core network type information, wherein the core network type information indicates at least one of: i) that the neighbor network node is connected to a CN of a first type (e.g., an EPC network) and ii) that the neighbor network node is connected to a CN of a second type (e.g., a 5GC network).
  • a first type e.g., an EPC network
  • a second type e.g., a 5GC network
  • a method performed by a wireless device includes acquiring core network (CN) type information associated with a neighbor cell, wherein the CN type information indicates that the neighbor cell is connected to a core network (CN) of a first type and/or a CN of a second type.
  • the method includes transmitting to a serving network node a report comprising identification information associated with the neighbor cell and the CN type information indicating that the neighbor cell is connected to a CN of the first type and/or a CN of the second type.
  • the neighbor cell is an evolved universal terrestrial radio access (E-UTRA) cell.
  • the CN type information comprises a CN indicator indicating a CN type.
  • the CN type information comprises at least one of: a Cell Global Identity (CGI), a Tracking Area Code, a CN identifier, and a Public Land Mobile Network (PLMN) identifier.
  • CGI Cell Global Identity
  • PLMN Public Land Mobile Network
  • the method includes deriving a CN type based on the at least one of: the CGI, the Tracking Area Code, the CN identifier, and the PLMN identifier.
  • the method includes before acquiring the CN type information associated with the neighbor cell, receiving from a network a cell identifier for identifying the neighbor cell; and using the cell identifier to acquire the CN type information associated with the neighbor cell.
  • the step of acquiring the CN type information comprises: receiving system information broadcast associated with the cell identifier, wherein the system information broadcast comprises the CN type information; and acquiring the CN type information from the received system information.
  • the step of acquiring the CN type information comprises: transmitting a request to a neighbor network node providing the neighbor cell for system information; receiving the requested system information from the neighbor network node, wherein the system information comprises the CN type information; and acquiring the CN type information from the received system information.
  • the method includes after acquiring the CN type information, determining, based on the acquired CN type information, whether the neighbor cell is connected to a EPC network and/or a 5GC network.
  • the identification information comprises a flag indicating whether the neighbor cell is connected to a 5GC network.
  • a method performed by a serving network node for establishing an interface with a neighbor network node providing a neighbor cell includes receiving a report transmitted by a wireless device, wherein the report comprises identification information associated with the neighbor cell and core network type information indicating that the neighbor cell is connected to a CN of a first type and/or a CN of a second type.
  • the method includes determining, based on the report, a type of interface to establish between the serving network node and the neighbor network node. In some embodiments, the method includes storing the identification information associated with the neighbor cell and the core network type information. In some embodiments, the method includes determining the core network type connected to the neighbor cell based on the report, wherein the neighbor network node is a eNodeB.
  • the serving network node is a eNodeB connected to a EPC network.
  • the method includes based on a determination that the neighbor cell is connected to the EPC network, determining i) to configure carrier aggregation, ii) to configure dual connectivity with the neighbor cell, and/or iii) to initiate an intra-Radio Access Technology (RAT) handover.
  • RAT Radio Access Technology
  • the serving network node is a eNodeB connected to a EPC network.
  • the method includes based on a determination that the neighbor cell is connected to both the EPC network and a 5GC network, determining whether the wireless device supports an eNodeB - EPC network connection and an eNodeB - 5GC network connection; and based on a determination that the wireless device supports the eNodeB - EPC network connection and the eNodeB - 5GC network connection, determining i) to configure carrier aggregation, ii) to configure dual connectivity with the neighbor cell, iii) to initiate an intra-Radio Access Technology (RAT) handover, iv) to initiate an inter-CN-based handover to the 5GC network, and/or v) to initiate a release and redirect of the wireless device to the neighbor cell.
  • RAT intra-Radio Access Technology
  • the serving network node is a eNodeB connected to a EPC network.
  • the method includes based on a determination that the neighbor cell is connected to a 5GC network, determining whether the wireless device supports an eNodeB - EPC network connection and an eNodeB - 5GC network connection; and based on a determination that the wireless device supports the eNodeB - EPC network connection and the eNodeB - 5GC network connection, initiating i) an inter-CN-based handover to the 5GC network and/or ii) a release and redirect of the wireless device to the neighbor cell.
  • the serving network node is a eNodeB connected to a 5GC network.
  • the method includes based on a determination that the neighbor cell is connected to the 5GC network, determining i) to configure carrier aggregation, ii) to configure dual connectivity with the neighbor cell, and/or iii) to initiate an intra-Radio Access Technology (RAT) handover.
  • RAT Radio Access Technology
  • the serving network node is a eNodeB connected to a 5GC network.
  • the method includes based on a determination that the neighbor cell is connected to both the EPC network and the 5GC network, determining whether the wireless device supports an eNodeB - EPC network connection and an eNodeB - 5GC network connection; and based on a determination that the wireless device supports the eNodeB - EPC network connection and the eNodeB - 5GC network connection, determining i) to configure carrier aggregation, ii) to configure dual connectivity with the neighbor cell, iii) to initiate an intra-Radio Access Technology (RAT) handover, iv) to initiate an inter-CN-based handover to the EPC network, and/or v) to initiate a release and redirect of the wireless device to the neighbor cell.
  • RAT intra-Radio Access Technology
  • the serving network node is an eNodeB connected to a
  • the method includes based on a determination that the neighbor cell is connected to a EPC network, determining whether the wireless device supports an eNodeB - EPC network connection and an eNodeB - 5GC network connection, and based on a determination that the wireless device supports the eNodeB - EPC network connection and the eNodeB - 5GC network connection, initiating i) an inter-CN-based handover to the EPC network and/or ii) a release and redirect of the wireless device to the neighbor cell.
  • the serving network node is a gNodeB connected to a 5GC network.
  • the method includes based on a determination that the neighbor cell is connected to the 5GC network, determining whether the wireless device supports a eNodeB-5GC network connection; and based on a determination that the wireless device supports the eNodeB-5GC network connection, determining i) to configure carrier aggregation, ii) to configure dual connectivity with the neighbor cell, and/or iii) to initiate an intra-Radio Access Technology (RAT) handover.
  • RAT Intra Radio Access Technology
  • the serving network node is a gNodeB connected to a 5GC network.
  • the method includes based on a determination that the neighbor cell is connected to both a EPC network and the 5GC network, determining whether the wireless device supports an eNodeB - EPC network connection and an eNodeB - 5GC network connection; and based on a determination that the wireless device supports the eNodeB - EPC network connection and the eNodeB - 5GC network connection, determining i) to configure carrier aggregation, ii) to configure dual connectivity with the neighbor cell, iii) to initiate an intra-Radio Access Technology (RAT) handover, iv) to initiate an inter-RAT and inter-CN based handover to the EPC network, and/or v) to initiate a release and redirect of the wireless device to the neighbor cell.
  • RAT Radio Access Technology
  • the serving network node is a gNodeB connected to a 5GC network.
  • the method includes based on a determination that the neighbor cell is connected a EPC network, determining whether the wireless device supports an eNodeB - EPC network connection; and based on a determination that the wireless device supports the eNodeB - EPC network connection, initiating i) an inter-RAT and inter-CN based handover to the EPC network and/or ii) a release and redirect of the wireless device to the neighbor cell.
  • the method includes determining that the neighbor cell is connected to a 5GC network.
  • the serving node is at least one of a eNodeB and a gNodeB, the serving node connected to the 5GC network and the determined type of interface to establish between the serving network node and the neighbor network node is a Xn connection interface.
  • the method includes determining that the neighbor cell is connected to both a EPC network and a 5GC network.
  • the serving node is at least one of a eNodeB and a gNodeB, the serving node connected to the 5GC network, and the determined type of interface to establish between the serving network node and the neighbor network node is a Xn connection interface.
  • the serving node is a eNodeB to the EPC network
  • the determined type of interface to establish between the serving network node and the neighbor network node is a X2 connection interface.
  • the method includes determining that the neighbor cell is connected to a EPC network.
  • the serving node is a eNodeB to the EPC network, and the determined type of interface to establish between the serving network node and the neighbor network node is a X2 connection interface.
  • the method includes transmitting core network type information associated with a neighbor cell, wherein the core network type information indicates that the neighbor network node is connected to a CN of a first type and/or a CN of a second type.
  • the core network type information comprises a core network indicator indicating the core network type.
  • the core network type information comprises at least one of: Cell Global Identity (CGT), Tracking Area Codes, Core Network (CN) identifiers, and Public Land Mobile Network (PLMN) identifiers.
  • CCT Cell Global Identity
  • CN Core Network
  • PLMN Public Land Mobile Network
  • the step of transmitting the core network type information comprises broadcasting the core network type information to the wireless device.
  • FIG. 1 illustrates various ways to deploy a network.
  • FIG. 2 illustrates various interfaces used in a network.
  • FIG. 3 illustrates a message flow diagram according to one embodiment.
  • FIG. 4A illustrates a portion of an information element according to one embodiment.
  • FIG. 4B illustrates a portion of an information element according to one embodiment.
  • FIG. 5 illustrates a summary of different actions according to some embodiments.
  • FIG. 6 which shows a wireless network in accordance with some embodiments.
  • FIG. 7 illustrates one embodiment of a UE in accordance with various aspects.
  • FIG. 8 is a schematic block diagram illustrating a virtualization environment according to some embodiments.
  • FIG. 9 schematically illustrates a telecommunication network connected via an intermediate network to a host computer.
  • FIG. 10 is a generalized block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection.
  • FIG. 11 is a flowchart illustrating a method implemented in a communication system including a host computer, a base station and a user equipment.
  • FIG. 12 is a flowchart illustrating a method implemented in a communication system including a host computer, a base station and a user equipment.
  • FIG. 13 is a flowchart illustrating a method implemented in a communication system including a host computer, a base station and a user equipment.
  • FIG. 14 is a flowchart illustrating a method implemented in a communication system including a host computer, a base station and a user equipment.
  • FIG. 15 is a flowchart illustrating a method implemented in a communication system including a host computer, a base station and a user equipment.
  • FIG. 16 is a flowchart illustrating a method implemented in a communication system including a host computer, a base station and a user equipment.
  • FIG. 17 is a flowchart illustrating a method implemented in a communication system including a host computer, a base station and a user equipment.
  • FIG. 18 illustrates a schematic block diagram of an apparatus in a wireless network.
  • FIG. 19 illustrates a schematic block diagram of an apparatus in a wireless network.
  • FIG. 20 illustrates a schematic block diagram of an apparatus in a wireless network.
  • FIG. 3 illustrates a message flow diagram illustrating signalling for CGI (Cell
  • Global Identity measurement according to some embodiments.
  • CGI reporting is part of ANR functionality, where the UE is requested to read neighbor cells system information (including global cell identity) to assist eNB/gNB build neighbor relation information.
  • CGI measurement is normally requested when the UE has reported an unknown PCI (i.e. an unknown neighbor cell).
  • PCI Physical Cell Identity
  • PCI Physical Cell Identity
  • the eNB/gNB has required information about a neighbor cell, this information is stored, it is used to setup X2/Xn connection between the nodes, which later on is used for several different procedures, such as handover, dual connectivity setup, etc.
  • the message flow diagram illustrating CGI acquisition signalling may be valid for the following several different embodiments described below.
  • the UE may be configured with an LTE measurement (this is an IRAT measurement if UE is connected to gNB, otherwise it is an intra-LTE measurement if the UE is connected to eNB).
  • LTE measurement this is an IRAT measurement if UE is connected to gNB, otherwise it is an intra-LTE measurement if the UE is connected to eNB.
  • the CGI measurement report may indicate whether the neighbor LTE is connected to EPC or 5GC.
  • the LTE cell broadcasts an indicator about which CN it is connected to (in some SIB) explicitly.
  • this CN indicator may be an indicator about EPC or 5GC.
  • single CN identifiers / PLMN identifiers broadcasted in system information may encode an information indicating the CN type, i.e., whether that is EPC or 5GC.
  • ASN.1 changes to support this additional functionality of indicating whether the neighbor LTE is connected to EPC or 5GC.
  • IE Information Element
  • MeasResults IE may include CGI information to support ANR functionality. With change marks, potential changes to the MeasResults IE may be applied as highlighted below for the implementation of the proposed solutions provided in the current disclosure in the case LTE configures the UE to report LTE CN related information.
  • IE MeasResults As proposed for 3GPP TS.36.331 is shown.
  • the IE MeasResults covers measured results for intra-frequency, inter- frequency and inter- RAT mobility.
  • measResultPCell-v1250 RSRQ-Range-v1250 OPTIONAL measResultCSI-RS-List-r12 MeasResultCSI-RS-List-r12 OPTIONAL [[ measResultForRSSI-r13 easResultForRSSI-r13 OPTIONAL, measResultServFreqListExt-r13 MeasResultServFreqListExt-r13 OPTIONAL,
  • measResultSSTD-r13 MeasResultSSTD-r13 OPTIONAL
  • measResultPCell-v1310 SEQUENCE ⁇
  • MeasResultListEUTRA SEQUENCE (SIZE (LmaxCellReport)) OF MeasResultEUTRA
  • MeasResultEUTRA SEQUENCE ⁇
  • freqBandlndicator-r13 FreqBandlndicator-r1 1 OPTIONAL, multiBandlnfoList-r13 MultiBandlnfoList-r1 1 OPTIONAL, freqBandlndicatorPriority-r13 ENUMERATED ⁇ true ⁇ OPTIONAL
  • MeasResultServFreqList-r10 SEQUENCE (SIZE (1..maxServCell-r10)) OF MeasResultServFreq-r10
  • MeasResultServFreqListExt-r13 SEQUENCE (SIZE (1..maxServCell-r13)) OF MeasResultServFreq-r13
  • MeasResultServFreq-r13 :: SEQUENCE ⁇
  • MeasResultCSI-RS-List-r12 SEQUENCE (SIZE (1..maxCellReport)) OF MeasResultCSI-RS-r12
  • easResultListUTRA SEQUENCE (SIZE (L.maxCellReport)) OF MeasResultUTRA
  • MeasResultGERAN SEQUENCE ⁇
  • MeasResultListCDMA2000 :: SEQUENCE (SIZE (LmaxCellReport)) OF MeasResultCDMA2000
  • MeasResultCDMA2000 :: SEQUENCE ⁇
  • MeasResultListCBR-r14 SEQUENCE (SIZE (1..maxCBR-Report-r14)) OF MeasResultCBR-r14
  • MeasResultForECID-r9 SEQUENCE ⁇
  • PLMN-ldentityList2 SEQUENCE (SIZE (1..5)) OF PLMN-ldentity
  • UL-PDCP-DelayResultList-r13 SEQUENCE (SIZE (1..maxQCI-r13)) OF UL-PDCP-DelayResult-r13
  • CGI information may comprise a NGC (e.g., 5GC) flag which indicates whether the reported LTE cell is an NGC or not, according to some embodiments.
  • the NGC flag is a Boolean flag.
  • the CGI information may comprise a sequence (e.g., coreType indication) indicating whether the reported LTE cell supports: (i) NGC, (ii) EPC or (iii) both NGC and EPC, as shown in FIG. 4B.
  • a sequence e.g., coreType indication
  • the eNB/gNB may store the supported CN type in neighboring NR cells.
  • different actions maybe expected depending on the serving node (eNB/gNB), the CN that serving node is connected to, the neighbor LTE cell connection to EPC and/or 5GC, and UE capability.
  • the UE may be connected to eNB-EPC, i.e., a eNodeB connected to EPC, and configured with intra-LTE measurement.
  • eNB-EPC i.e., a eNodeB connected to EPC
  • intra-LTE measurement i.e., a eNodeB connected to EPC
  • the UE reports a suitable LTE cell:
  • the eNB may decide to configure carrier aggregation, dual connectivity or initiate an intra-RAT handover (e.g. X2, SI or intra- node HO).
  • an intra-RAT handover e.g. X2, SI or intra- node HO.
  • the eNB may decide to initiate inter-CN-based handover or release-and-redirect.
  • the eNB may decide to initiate inter-CN-based handover or release-and- redirect.
  • the UE may be connected to eNB-5GC, i.e., a eNodeB connected to 5GC, and configured with intra-LTE measurement.
  • eNB-5GC i.e., a eNodeB connected to 5GC
  • intra-LTE measurement When the UE reports a suitable LTE cell: [0099] (1) If neighbor LTE cell is connected to 5GC, the eNB may decide to configure carrier aggregation, dual connectivity or initiate an intra-RAT handover (e.g. Xn, NG or intra- node HO).
  • intra-RAT handover e.g. Xn, NG or intra- node HO
  • the eNB may decide to initiate inter-CN-based handover or release-and-redirect.
  • the eNB may decide to initiate inter-CN-based handover or release-and- redirect.
  • the UE may be connected to gNB (NR) with 5GC, i.e. a gNodeB connected to 5GC, and configured with IRAT LTE measurement.
  • gNB NR
  • 5GC i.e. a gNodeB connected to 5GC
  • IRAT LTE measurement IRAT LTE measurement.
  • the gNB may decide to configure carrier aggregation, dual connectivity or initiate an inter-RAT (intra-CN) handover (e.g. Xn, NG or intra-node HO).
  • intra-CN inter-RAT
  • the gNB may decide to initiate inter-RAT inter-CN-based handover or release-and-redirect.
  • Tf neighbor LTE cell is connected to EPC only, and the UE is LTE-EPC capable, the gNB may decide to initiate inter-RAT inter-CN-based handover or release-and- redirect.
  • FIG. 6 illustrates a non-limiting summary of some different actions depending on the the serving node (eNB/gNB), the CN that serving node is connected to, the neighbor LTE cell connection to EPC and/or 5GC, and UE capability, including some of the actions described above.
  • an LTE cell connected to 5GC may be referred to as cLTE
  • a cNB is a node supporting LTE
  • a gNB is a node supporting NR
  • Another embodiment could be that the UE includes the indication of EPC/5GC supports by different kinds of configuration.
  • the network may configure the UE with a field in the LTE measurement object indicating that detected LTE cells in that particular measurement object, when reported, should include the EPC/5GC indication.
  • the EPC/5GC indication may be implicitly derived by the UE based on any other indication, implicit or explicit, that is associated to the LTE neighbor cell. In some embodiments, this information may be broadcasted explicitly as part of system information. In some embodiments, the EPC/5GC indication may be implicitly derived by the UE and/or by the network based on bits of other network identifiers such as CGI, Tracking area codes, PLMN identifiers, PCI, etc.
  • one possible solution could be that EPC/5GC support information could be exchanged via Xn or X2. This is however may not be possible in all cases since if the eNB only supports EPC, it is only required to support X2. Likewise, if the eNB only supports 5GC, it is only required to support Xn. Only in case the eNB is connected to both EPC and 5GC it is expected to support both X2 and Xn. Therefore, only in the cases where the nodes support the same interface(s) this option would be possible. It would require also to add new information elements to this interface(s) protocol specification (e.g. X2AP/XnAP) to signal support for EPC/5GC connections.
  • X2AP/XnAP new information elements to this interface(s) protocol specification
  • Another possible solution would be to rely on handover statistics, i.e. to ignore specific targets from handover after no success rate over time. This solution impacts both network and UE performance negatively.
  • manual configuration may not be a practical and preferred option in real field either
  • HO restriction list may be configured by core network, which is an existing solution. Assigning different tracking areas for NSA and SA, however, may not provide a practical option in reality. For example, assigning different tracking areas for NSA and SA cells requires update of the tracking area planning at every RAN upgrade. [00116] In some embodiments, the serving node may perform one of the following actions and/or a combination based on the reporting of EPC/5GC information per LTE/eLTE cell:
  • serving node is an eNB or gNB connected to 5GC, it can setup Xn connection (if same CN node), and (ii) if serving node is an eNB connected only to EPC, no interface towards target eNB can be setup.
  • the network may backlist some LTE/eLTE cells for a given UE depending on UE capabilities. For example, if the reported LTE cell is only connected to 5GC, and the UE is only LTE-EPC capable, these cells for that particular UE may be blacklisted.
  • the network may whitelist some LTE cell with EPC and/or
  • 5GC connection for a given UE depending on UE capabilities and/or a specific interest the network (DC, IRAT, etc.).
  • a wireless network such as the example wireless network illustrated in Figure 6.
  • the wireless network of Figure 6 only depicts network 606, network nodes 660 and 660b, and WDs 610, 610b, and 610c.
  • a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device.
  • network node 660 and wireless device (WD) 610 are depicted with additional detail.
  • the wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices' access to and/or use of the services provided by, or via, the wireless network.
  • the wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system.
  • the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures.
  • embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards;
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • WLAN wireless local area network
  • WiMax Worldwide Interoperability for Microwave Access
  • Network 606 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks
  • PSTNs public switched telephone networks
  • WANs wide-area networks
  • LANs local area networks
  • wireless local area networks wireless local area networks
  • WLANs wireless networks
  • wireless networks wireless networks
  • metropolitan area networks metropolitan area networks
  • Network node 660 and WD 610 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network.
  • the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network.
  • network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (cNBs) and N NodcBs (gNBs)).
  • APs access points
  • BSs base stations
  • cNBs evolved Node Bs
  • gNBs NodcBs
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
  • DAS distributed antenna system
  • network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (R Cs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.
  • MSR multi-standard radio
  • R Cs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • transmission points transmission nodes
  • MCEs multi-cell/multicast coordination entities
  • core network nodes e.g., MSCs, MMEs
  • O&M nodes e.g., OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.
  • network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.
  • network node 660 includes processing circuitry 670, device readable medium 680, interface 690, auxiliary equipment 684, power source 686, power circuitry 687, and antenna 662.
  • network node 660 illustrated in the example wireless network of Figure 6 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein.
  • network node 660 may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 680 may comprise multiple separate hard drives as well as multiple RAM modules).
  • network node 660 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • network node 660 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeB's.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • network node 660 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • Network node 660 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 660, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 660.
  • Processing circuitry 670 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 670 may include processing information obtained by processing circuitry 670 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing information obtained by processing circuitry 670 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • Processing circuitry 670 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 660 components, such as device readable medium 680, network node 660 functionality.
  • processing circuitry 670 may execute instructions stored in device readable medium 680 or in memory within processing circuitry 670. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein.
  • processing circuitry 670 may include a system on a chip (SOC).
  • SOC system on a chip
  • processing circuitry 670 may include one or more of radio frequency (RF) transceiver circuitry 672 and baseband processing circuitry 674.
  • radio frequency (RF) transceiver circuitry 672 and baseband processing circuitry 674 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units.
  • part or all of RF transceiver circuitry 672 and baseband processing circuitry 674 may be on the same chip or set of chips, boards, or units
  • processing circuitry 670 executing instructions stored on device readable medium 680 or memory within processing circuitry 670.
  • some or all of the functionality may be provided by processing circuitry 670 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner.
  • processing circuitry 670 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 670 alone or to other components of network node 660, but are enjoyed by network node 660 as a whole, and/or by end users and the wireless network generally.
  • Device readable medium 680 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 670.
  • volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or
  • Device readable medium 680 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 670 and, utilized by network node 660.
  • Device readable medium 680 may be used to store any calculations made by processing circuitry 670 and/or any data received via interface 690.
  • processing circuitry 670 and device readable medium 680 may be considered to be integrated.
  • Interface 690 is used in the wired or wireless communication of signalling and/or data between network node 660, network 606, and/or WDs 610. As illustrated, interface 690 comprises port(s)/terminal(s) 694 to send and receive data, for example to and from network 606 over a wired connection. Interface 690 also includes radio front end circuitry 692 that may be coupled to, or in certain embodiments a part of, antenna 662. Radio front end circuitry 692 comprises filters 698 and amplifiers 696. Radio front end circuitry 692 may be connected to antenna 662 and processing circuitry 670. Radio front end circuitry may be configured to condition signals communicated between antenna 662 and processing circuitry 670.
  • Radio front end circuitry 692 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 692 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 698 and/or amplifiers 696. The radio signal may then be transmitted via antenna 662. Similarly, when receiving data, antenna 662 may collect radio signals which are then converted into digital data by radio front end circuitry 692. The digital data may be passed to processing circuitry 670. In other embodiments, the interface may comprise different components and/or different combinations of components.
  • network node 660 may not include separate radio front end circuitry 692, instead, processing circuitry 670 may comprise radio front end circuitry and may be connected to antenna 662 without separate radio front end circuitry 692.
  • processing circuitry 670 may comprise radio front end circuitry and may be connected to antenna 662 without separate radio front end circuitry 692.
  • all or some of RF transceiver circuitry 672 may be considered a part of interface 690.
  • interface 690 may include one or more ports or terminals 694, radio front end circuitry 692, and RF transceiver circuitry 672, as part of a radio unit (not shown), and interface 690 may communicate with baseband processing circuitry 674, which is part of a digital unit (not shown).
  • Antenna 662 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 662 may be coupled to radio front end circuitry 690 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 662 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna 662 may be separate from network node 660 and may be connectable to network node 660 through an interface or port.
  • Antenna 662, interface 690, and/or processing circuitry 670 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 662, interface 690, and/or processing circuitry 670 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.
  • Power circuitry 687 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 660 with power for performing the functionality described herein. Power circuitry 687 may receive power from power source 686. Power source 686 and/or power circuitry 687 may be configured to provide power to the various components of network node 660 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 686 may either be included in, or external to, power circuitry 687 and/or network node 660.
  • network node 660 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 687.
  • power source 686 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 687. The battery may provide backup power should the external power source fail.
  • Other types of power sources, such as photovoltaic devices, may also be used.
  • Alternative embodiments of network node 660 may include additional components beyond those shown in Figure 6 that may be responsible for providing certain aspects of the network node's functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein.
  • network node 660 may include user interface equipment to allow input of information into network node 660 and to allow output of information from network node 660. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 660.
  • wireless device refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices.
  • the term WD may be used interchangeably herein with user equipment (UE).
  • Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air.
  • a WD may be configured to transmit and/or receive information without direct human interaction.
  • a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network.
  • Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE), a vehicle-mounted wireless terminal device, etc.
  • VoIP voice over IP
  • PDA personal digital assistant
  • LOE laptop-embedded equipment
  • LME laptop-mounted equipment
  • CPE wireless customer-premise equipment
  • a WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to -vehicle (V2V), vehicle- to-infrastructure (V2I), vehicle-to -everything (V2X) and may in this case be referred to as a D2D communication device.
  • D2D device-to-device
  • V2V vehicle-to -vehicle
  • V2I vehicle- to-infrastructure
  • V2X vehicle-to -everything
  • a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node.
  • the WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device.
  • M2M machine-to-machine
  • the WD may be a UE implementing the 3 GPP narrow band internet of things ( B-IoT) standard.
  • B-IoT narrow band internet of things
  • machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.).
  • a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • a WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.
  • wireless device 610 includes antenna 611, interface 614, processing circuitry 620, device readable medium 630, user interface equipment 632, auxiliary equipment 634, power source 636 and power circuitry 637.
  • WD 610 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 610, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD 610.
  • Antenna 611 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 614.
  • antenna 611 may be separate from WD 610 and be connectable to WD 610 through an interface or port.
  • Antenna 611, interface 614, and/or processing circuitry 620 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD.
  • radio front end circuitry and/or antenna 611 may be considered an interface.
  • interface 614 comprises radio front end circuitry 612 and antenna
  • Radio front end circuitry 612 comprise one or more filters 618 and amplifiers 616.
  • Radio front end circuitry 614 is connected to antenna 611 and processing circuitry 620, and is configured to condition signals communicated between antenna 611 and processing circuitry 620.
  • Radio front end circuitry 612 may be coupled to or a part of antenna 611.
  • WD 610 may not include separate radio front end circuitry 612; rather, processing circuitry 620 may comprise radio front end circuitry and may be connected to antenna 611.
  • some or all of RF transceiver circuitry 622 may be considered a part of interface 614.
  • Radio front end circuitry 612 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection.
  • Radio front end circuitry 612 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 618 and/or amplifiers 616. The radio signal may then be transmitted via antenna 611. Similarly, when receiving data, antenna 611 may collect radio signals which are then converted into digital data by radio front end circuitry 612. The digital data may be passed to processing circuitry 620. In other embodiments, the interface may comprise different components and/or different combinations of components.
  • Processing circuitry 620 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD 610 components, such as device readable medium 630, WD 610 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 620 may execute instructions stored in device readable medium 630 or in memory within processing circuitry 620 to provide the functionality disclosed herein.
  • processing circuitry 620 includes one or more of RF transceiver circuitry 622, baseband processing circuitry 624, and application processing circuitry 626.
  • the processing circuitry may comprise different components and/or different combinations of components.
  • processing circuitry 620 of WD 610 may comprise a SOC.
  • RF transceiver circuitry 622, baseband processing circuitry 624, and application processing circuitry 626 may be on separate chips or sets of chips.
  • part or all of baseband processing circuitry 624 and application processing circuitry 626 may be combined into one chip or set of chips, and RF transceiver circuitry 622 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry 622 and baseband processing circuitry 624 may be on the same chip or set of chips, and application processing circuitry 626 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry 622, baseband processing circuitry 624, and application processing circuitry 626 may be combined in the same chip or set of chips.
  • RF transceiver circuitry 622 may be a part of interface 614.
  • RF transceiver circuitry 622 may condition RF signals for processing circuitry 620.
  • processing circuitry 620 executing instructions stored on device readable medium 630, which in certain embodiments may be a computer-readable storage medium.
  • processing circuitry 620 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In any of those particular
  • processing circuitry 620 can be configured to perform the described functionality.
  • the benefits provided by such functionality are not limited to processing circuitry 620 alone or to other components of WD 610, but are enjoyed by WD 610 as a whole, and/or by end users and the wireless network generally.
  • Processing circuitry 620 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 620, may include processing information obtained by processing circuitry 620 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 610, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing information obtained by processing circuitry 620 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 610, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • Device readable medium 630 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 620.
  • Device readable medium 630 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 620.
  • processing circuitry 620 and device readable medium 630 may be considered to be integrated.
  • User interface equipment 632 may provide components that allow for a human user to interact with WD 610. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 632 may be operable to produce output to the user and to allow the user to provide input to WD 610. The type of interaction may vary depending on the type of user interface equipment 632 installed in WD 610. For example, if WD 610 is a smart phone, the interaction may be via a touch screen; if WD 610 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected).
  • usage e.g., the number of gallons used
  • a speaker that provides an audible alert
  • User interface equipment 632 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 632 is configured to allow input of information into WD 610, and is connected to processing circuitry 620 to allow processing circuitry 620 to process the input information. User interface equipment 632 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 632 is also configured to allow output of information from WD 610, and to allow processing circuitry 620 to output information from WD 610. User interface equipment 632 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 632, WD 610 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.
  • Auxiliary equipment 634 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 634 may vary depending on the embodiment and/or scenario.
  • Power source 636 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used.
  • WD 610 may further comprise power circuitry 637 for delivering power from power source 636 to the various parts of WD 610 which need power from power source 636 to carry out any functionality described or indicated herein.
  • Power circuitry 637 may in certain embodiments comprise power management circuitry.
  • Power circuitry 637 may additionally or alternatively be operable to receive power from an external power source; in which case WD 610 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable.
  • Power circuitry 637 may also in certain embodiments be operable to deliver power from an external power source to power source 636. This may be, for example, for the charging of power source 636. Power circuitry 637 may perform any formatting, converting, or other modification to the power from power source 636 to make the power suitable for the respective components of WD 610 to which power is supplied.
  • FIG. 7 illustrates one embodiment of a UE in accordance with various aspects described herein.
  • a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).
  • a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
  • UE 7200 may be any UE identified by the 3rd Generation
  • UE 700 is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3rd Generation Partnership Project (3 GPP), such as 3GPP's GSM, UMTS, LTE, and/or 5G standards.
  • 3 GPP 3rd Generation Partnership Project
  • the term WD and UE may be used interchangeable. Accordingly, although Figure 7 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.
  • UE 700 includes processing circuitry 701 that is opcrativcly coupled to input/output interface 705, radio frequency (RF) interface 709, network connection interface 711, memory 715 including random access memory (RAM) 717, read-only memory (ROM) 719, and storage medium 721 or the like, communication subsystem 731, power source 733, and/or any other component, or any combination thereof.
  • Storage medium 721 includes operating system 723, application program 725, and data 727. In other embodiments, storage medium 721 may include other similar types of information.
  • Certain UEs may utilize all of the components shown in Figure 7, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • processing circuitry 701 may be configured to process computer instructions and data.
  • Processing circuitry 701 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above.
  • the processing circuitry 701 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.
  • input/output interface 705 may be configured to provide a communication interface to an input device, output device, or input and output device.
  • UE 700 may be configured to use an output device via input/output interface 705.
  • An output device may use the same type of interface port as an input device.
  • a USB port may be used to provide input to and output from UE 700.
  • the output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • UE 700 may be configured to use an input device via input/output interface 705 to allow a user to capture information into UE 700.
  • the input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like.
  • the presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof.
  • the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.
  • RF interface 709 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna.
  • Network connection interface 711 may be configured to provide a communication interface to network 743a.
  • Network 743a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • network 743a may comprise a Wi-Fi network.
  • Network connection interface 711 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like.
  • Network connection interface 711 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.
  • RAM 717 may be configured to interface via bus 702 to processing circuitry 701 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers.
  • ROM 719 may be configured to provide computer instructions or data to processing circuitry 701.
  • ROM 719 may be configured to store invariant low- level system code or data for basic system functions such as basic input and output (T/O), startup, or reception of keystrokes from a keyboard that arc stored in a non- volatile memory.
  • Storage medium 721 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives.
  • storage medium 721 may be configured to include operating system 723, application program 725 such as a web browser application, a widget or gadget engine or another application, and data file 727.
  • Storage medium 721 may store, for use by UE 700, any of a variety of various operating systems or combinations of operating systems.
  • Storage medium 721 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro- DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof.
  • RAID redundant array of independent disks
  • HD-DVD high-density digital versatile disc
  • HDDS holographic digital data storage
  • DIMM synchronous dynamic random access memory
  • SIM/RUIM removable user identity
  • Storage medium 721 may allow UE 700 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium 721, which may comprise a device readable medium.
  • processing circuitry 701 may be configured to communicate with network 743b using communication subsystem 731.
  • Network 743 a and network 743b may be the same network or networks or different network or networks.
  • Communication subsystem 731 may be configured to include one or more transceivers used to communicate with network 743b.
  • communication subsystem 731 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.7, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like.
  • RAN radio access network
  • Each transceiver may include transmitter 733 and/or receiver 735 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 733 and receiver 735 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.
  • the communication functions of communication subsystem 731 may include data communication, voice communication, multimedia
  • communication subsystem 731 may include cellular communication, Wi-Fi
  • Network 743b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • network 743b may be a cellular network, a Wi-Fi network, and/or a near- field network.
  • Power source 713 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 700.
  • communication subsystem 731 may be configured to include any of the components described herein.
  • processing circuitry 701 may be configured to communicate with any of such components over bus 702.
  • any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 701 perform the corresponding functions described herein.
  • the functionality of any of such components may be partitioned between processing circuitry 701 and communication subsystem 731.
  • the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.
  • Figure 8 is a schematic block diagram illustrating a virtualization environment
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).
  • some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 800 hosted by one or more of hardware nodes 830. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.
  • the functions may be implemented by one or more applications 820 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Applications 820 are run in virtualization environment 800 which provides hardware 830 comprising processing circuitry 860 and memory 890.
  • Memory 890 contains instructions 895 executable by processing circuitry 860 whereby application 820 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.
  • Virtualization environment 800 comprises general-purpose or special-purpose network hardware devices 830 comprising a set of one or more processors or processing circuitry 860, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors.
  • processors or processing circuitry 860 which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors.
  • Each hardware device may comprise memory 890-1 which may be non-persistent memory for temporarily storing instructions 895 or software executed by processing circuitry 860.
  • Each hardware device may comprise one or more network interface controllers (NICs) 870, also known as network interface cards, which include physical network interface 880.
  • NICs network interface controllers
  • Each hardware device may also include non-transitory, persistent, machine-readable storage media 890-2 having stored therein software 895 and/or instructions executable by processing circuitry 860.
  • Software 895 may include any type of software including software for instantiating one or more virtualization layers 850 (also referred to as hypervisors), software to execute virtual machines 840 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.
  • Virtual machines 840 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 850 or hypervisor. Different embodiments of the instance of virtual appliance 820 may be implemented on one or more of virtual machines 840, and the implementations may be made in different ways.
  • processing circuitry 860 executes software 895 to instantiate the hypervisor or virtualization layer 850, which may sometimes be referred to as a virtual machine monitor (VMM).
  • VMM virtual machine monitor
  • Virtualization layer 850 may present a virtual operating platform that appears like networking hardware to virtual machine 840.
  • hardware 830 may be a standalone network node with generic or specific components. Hardware 830 may comprise antenna 8225 and may implement some functions via virtualization. Alternatively, hardware 830 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) 8100, which, among others, oversees lifecycle management of applications 820.
  • CPE customer premise equipment
  • MANO management and orchestration
  • NFV network function virtualization
  • NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
  • virtual machine 840 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each of virtual machines 840, and that part of hardware 830 that executes that virtual machine be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 840, forms a separate virtual network elements (VNE).
  • VNE virtual network elements
  • VNF Virtual Network Function
  • one or more radio units 8200 that each include one or more transmitters 8220 and one or more receivers 8210 may be coupled to one or more antennas 8225.
  • Radio units 8200 may communicate directly with hardware nodes 830 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
  • control system 8230 which may alternatively be used for communication between the hardware nodes 830 and radio units 8200.
  • the illustrated communication system includes telecommunication network 910, such as a 3GPP-type cellular network, which comprises access network 911, such as a radio access network, and core network 914.
  • Access network 911 comprises a plurality of base stations 912a, 912b, 912c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 913a, 913b, 913c.
  • Each base station 912a, 912b, 912c is connectable to core network 914 over a wired or wireless connection 915.
  • a first UE 991 located in coverage area 913c is configured to wirelessly connect to, or be paged by, the corresponding base station 912c.
  • a second UE 992 in coverage area 913a is wirelessly connectable to the corresponding base station 912a. While a plurality of UEs 991, 992 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 912.
  • Telecommunication network 910 is itself connected to host computer 930, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm.
  • Host computer 930 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections 921 and 922 between
  • telecommunication network 910 and host computer 930 may extend directly from core network 914 to host computer 930 or may go via an optional intermediate network 920.
  • Intermediate network 920 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 920, if any, may be a backbone network or the Internet; in particular, intermediate network 920 may comprise two or more sub-networks (not shown).
  • the communication system of Figure 9 as a whole enables connectivity between the connected UEs 991, 992 and host computer 930.
  • the connectivity may be described as an over-the-top (OTT) connection 950.
  • OTT over-the-top
  • Host computer 930 and the connected UEs 991, 992 are configured to communicate data and/or signaling via OTT connection 950, using access network 911, core network 914, any intermediate network 920 and possible further infrastructure (not shown) as intermediaries.
  • OTT connection 950 may be transparent in the sense that the participating communication devices through which OTT connection 950 passes are unaware of routing of uplink and downlink communications.
  • base station 912 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 930 to be forwarded (e.g., handed over) to a connected UE 991.
  • base station 912 need not be aware of the future routing of an outgoing uplink communication originating from the UE 991 towards the host computer 930.
  • host computer 1010 comprises hardware 1015 including communication interface 1016 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 1000.
  • Host computer 1010 further comprises processing circuitry 1018, which may have storage and/or processing capabilities.
  • processing circuitry 1018 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Host computer 1010 further comprises software 1011, which is stored in or accessible by host computer 1010 and executable by processing circuitry 1018.
  • Software 1011 includes host application 1012.
  • Host application 1012 may be operable to provide a service to a remote user, such as UE 1030 connecting via OTT connection 1050 terminating at UE 1030 and host computer 1010. In providing the service to the remote user, host application 1012 may provide user data which is transmitted using OTT connection 1050.
  • Communication system 1000 further includes base station 1020 provided in a telecommunication system and comprising hardware 1025 enabling it to communicate with host computer 1010 and with UE 1030.
  • Hardware 1025 may include communication interface 1026 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 1000, as well as radio interface 1027 for setting up and maintaining at least wireless connection 1070 with UE 1030 located in a coverage area (not shown in Figure 10) served by base station 1020.
  • Communication interface 1026 may be configured to facilitate connection 1060 to host computer 1010. Connection 1060 may be direct or it may pass through a core network (not shown in Figure 10) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.
  • hardware 1025 of base station 1020 further includes processing circuitry 1028, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Base station 1020 further has software 1021 stored internally or accessible via an external connection.
  • Communication system 1000 further includes UE 1030 already referred to. Its hardware 1035 may include radio interface 1037 configured to set up and maintain wireless connection 1070 with a base station serving a coverage area in which UE 1030 is currently located. Hardware 1035 of UE 1030 further includes processing circuitry 1038, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • UE 1030 further comprises software 1031, which is stored in or accessible by UE 1030 and executable by processing circuitry 1038.
  • Software 1031 includes client application 1032. Client application 1032 may be operable to provide a service to a human or non-human user via UE 1030, with the support of host computer 1010.
  • an executing host application 1012 may communicate with the executing client application 1032 via OTT connection 1050 terminating at UE 1030 and host computer 1010.
  • client application 1032 may receive request data from host application 1012 and provide user data in response to the request data.
  • OTT connection 1050 may transfer both the request data and the user data.
  • Client application 1032 may interact with the user to generate the user data that it provides.
  • host computer 1010, base station 1020 and UE 1030 illustrated in Figure 10 may be similar or identical to host computer 930, one of base stations 912a, 912b, 912c and one of UEs 991, 992 of Figure 9, respectively.
  • the inner workings of these entities may be as shown in Figure 10 and independently, the surrounding network topology may be that of Figure 9.
  • OTT connection 1050 has been drawn abstractly to illustrate the communication between host computer 1010 and UE 1030 via base station 1020, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from UE 1030 or from the service provider operating host computer 1010, or both. While OTT connection 1050 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • Wireless connection 1070 between UE 1030 and base station 1020 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to UE
  • the teachings of these embodiments may improve network performance by introducing new information in existing UE measurements on LTE, the new information identifying whether the a neighbor LTE cell is connected 5GC and/or EPC, and the new information being used by RANs (eNB/gNB) to make optimal decisions in different network scenarios, and thereby provide benefits such as improved ANR functionality, improved end user performance, and simplified network management.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring OTT connection 1050 may be implemented in software 1011 and hardware 101 of host computer 1010 or in software
  • sensors may be deployed in or in association with communication devices through which OTT connection 1050 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 1011, 1031 may compute or estimate the monitored quantities.
  • reconfiguring of OTT connection 1050 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 1020, and it may be unknown or imperceptible to base station 1020. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling facilitating host computer 1010's measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software 1011 and 1031 causes messages to be transmitted, in particular empty or 'dummy' messages, using OTT connection 1050 while it monitors propagation times, errors etc.
  • FIG. 11 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 9 and 10. For simplicity of the present disclosure, only drawing references to Figure 11 will be included in this section.
  • the host computer provides user data.
  • substep 1111 (which may be optional) of step 1110, the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE.
  • step 1130 the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 1140 the UE executes a client application associated with the host application executed by the host computer.
  • FIG. 12 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 9 and 10. For simplicity of the present disclosure, only drawing references to Figure 12 will be included in this section.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 1230 (which may be optional), the UE receives the user data carried in the transmission.
  • FIG. 13 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 9 and 10. For simplicity of the present disclosure, only drawing references to Figure 13 will be included in this section.
  • step 1310 the UE receives input data provided by the host computer. Additionally or alternatively, in step 1320, the UE provides user data.
  • substep 1321 (which may be optional) of step 1320, the UE provides the user data by executing a client application.
  • substep 1311 (which may be optional) of step 1310, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer.
  • the executed client application may further consider user input received from the user.
  • the UE initiates, in substep 1330 (which may be optional), transmission of the user data to the host computer.
  • step 1340 of the method the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.
  • FIG 14 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 9 and 10. For simplicity of the present disclosure, only drawing references to Figure 14 will be included in this section.
  • the base station receives user data from the UE.
  • the base station initiates transmission of the received user data to the host computer.
  • step 1430 (which may be optional)
  • the host computer receives the user data carried in the transmission initiated by the base station.
  • any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses.
  • Each virtual apparatus may comprise a number of these functional units.
  • These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein.
  • the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more
  • FIG. 15 depicts a method 1500, in accordance with particular embodiments, that is performed by a wireless device.
  • Method 1500 may begin at step 1502 in which the wireless device acquires CN type information transmitted by a neighbor network node, wherein the CN type information indicates at least one of: i) that the neighbor network node is connected to a CN of a first type (e.g., an evolved packet core (EPC) network) and ii) that the neighbor network node is connected to a CN of a second type (e.g., a 5G core network (5GC)).
  • the neighbor network node is a eNodeB.
  • the core network type information comprises a core network indicator indicating the core network type.
  • the core network type information comprises at least one of: a Cell Global Identity (CGI), a Tracking Area Code, a CN identifier, and a Public Land Mobile Network (PLMN) identifier.
  • CGI Cell Global Identity
  • PLMN Public Land Mobile Network
  • the wireless device derives a core network type connected to the neighbor network node based on the at least one of: the CGI, the Tracking Area Code, the CN identifier, and the PLMN identifier.
  • the wireless device transmits to a serving network node a report comprising identification information identifying the neighbor network node and core network type information indicating at least one of: i) that the identified neighbor network node is connected to a CN of the first type and ii) that the identified neighbor network node is connected to a CN of the second type.
  • the method 1500 further includes the wireless device: receiving from a network a cell identifier (e.g., PCI) for identifying the neighbor network node before acquiring core network type information transmitted by the neighbor network node; and using the cell identifier to acquire the core network type information transmitted by the neighbor network.
  • the identification information comprises a flag indicating whether the neighbor network node is connected to a 5GC network.
  • acquiring the core network type information transmitted by the neighbor network node comprises: receiving system information broadcast associated with the cell identifier, wherein the system information broadcast comprises the core network type information; and acquiring the core network type information from the received system information.
  • the acquiring the core network type information transmitted by the neighbor network node comprises: transmitting a request to the neighbor network node for system information; receiving the requested system information from the neighbor network node, wherein the system information comprises the core network type information; and acquiring the core network type information from the received system information.
  • the method 1500 further includes the wireless device: after acquiring the core network type information transmitted by the neighbor network node, determining, based on the acquired core network type information, whether the neighbor network node is connected to at least one of: i) a EPC network and ii) a 5GC network.
  • FIG. 16 depicts a method 1600, in accordance with particular embodiments, that is performed by a serving network node for establishing an interface with a neighbor network node.
  • Method 1600 may begin at step 1602 in which the serving network node (e.g., base station) receiving a report transmitted by a wireless device, wherein the report comprises identification information identifying the neighbor network node and core network type information indicating at least one of: i) that the identified neighbor network node is connected to a CN of a first type (e.g. an EPC network) and ii) that the identified neighbor network node is connected to a CN of a second type (e.g., a 5GC network).
  • a first type e.g. an EPC network
  • a second type e.g., a 5GC network
  • method 1600 further includes the serving network node: determining, based on the report, a type of interface to establish between the serving network node and the neighbor network node. In some embodiments, method 1600 further includes the serving network node: storing the identification information identifying the neighbor network node and core network type information. [00195] In some embodiments, method 1600 further includes the serving network node: determining the core network type connected to the identified neighbor network node based on the report, wherein the identified neighbor network node is a eNodeB.
  • the method 1600 further includes the serving network node: based on a determination that the identified neighbor network node is connected to the EPC network, determining at least one of: i) to configure carrier aggregation, ii) to configure dual connectivity with the identified neighbor network node, and iii) to initiate an intra-Radio Access Technology (RAT) handover (e.g. X2, SI or intra-node handover).
  • RAT Radio Access Technology
  • the method 1600 further includes the serving network node: based on a determination that the identified neighbor network node is connected to both the EPC network and a 5GC network, determining whether the wireless device is compatible with an eNodeB - EPC network connection and an eNodeB - 5GC network connection; and based on a determination that the wireless device is compatible with the eNodeB - EPC network connection and the eNodeB - 5GC network connection, determining at least one of: i) to configure carrier aggregation, ii) to configure dual connectivity with the identified neighbor network node, iii) to initiate an intra-Radio Access Technology (RAT) handover, iv) to initiate an inter-CN-based handover to the 5GC network, and v) to initiate a release and redirect of the wireless device to the identified neighbor network node.
  • RAT Radio Access Technology
  • the method 1600 further includes the serving network node: based on a determination that the identified neighbor network node is connected to a 5GC network, determining whether the wireless device is compatible with an eNodeB - EPC network connection and an eNodeB - 5GC network connection; and based on a determination that the wireless device is compatible with the eNodeB - EPC network connection and the eNodeB - 5GC network connection, initiating at least one of: i) an inter-CN-based handover to the 5GC network and ii) a release and redirect of the wireless device to the identified neighbor network node.
  • the method 1600 further includes the serving network node: based on a determination that the identified neighbor network node is connected to the 5GC network, determining at least one of: i) to configure carrier aggregation, ii) to configure dual connectivity with the identified neighbor network node, and iii) to initiate an intra-Radio Access Technology (RAT) handover (e.g., Xn, NG or intra-node handover).
  • RAT Radio Access Technology
  • the method 1600 further includes the serving network node: based on a determination that the identified neighbor network node is connected to both the EPC network and the 5GC network, determining whether the wireless device is compatible with an eNodeB - EPC network connection and an eNodeB - 5GC network connection; and based on a determination that the wireless device is compatible with the eNodeB - EPC network connection and the eNodeB - 5GC network connection, determining at least one of: i) to configure carrier aggregation, ii) to configure dual connectivity with the identified neighbor network node, iii) to initiate an intra-Radio Access Technology (RAT) handover (e.g., Xn, NG or intra-node handover), iv) to initiate an inter-CN-based handover to the EPC network, and v) to initiate a release and redirect of the wireless device to the
  • RAT Radio Access Technology
  • the method 1600 further includes the serving network node: based on a determination that the identified neighbor network node is connected to a EPC network, determining whether the wireless device is compatible with an eNodeB - EPC network connection and an eNodeB - 5GC network connection, and based on a determination that the wireless device is compatible with the eNodeB - EPC network connection and the eNodeB - 5GC network connection, initiating at least one of: i) an inter-CN-based handover to the 5GC network and ii) a release and redirect of the wireless device to the identified neighbor network node.
  • the method 1600 further includes the serving network node: based on a determination that the identified neighbor network node is connected to the 5GC network, determining at least one of: i) to configure carrier aggregation, ii) to configure dual connectivity with the identified neighbor network node, and iii) to initiate an intra- adio Access Technology (RAT) handover (e.g., Xn, NG or intra-node handover)
  • RAT intra- adio Access Technology
  • the method 1600 further includes the serving network node: based on a determination that the identified neighbor network node is connected to both the EPC network and the 5GC network, determining whether the wireless device is compatible with an eNodeB - EPC network connection and an eNodeB - 5GC network connection; and based on a
  • the wireless device is compatible with the eNodeB - EPC network connection and the eNodeB - 5GC network connection, determining at least one of: i) to configure carrier aggregation, ii) to configure dual connectivity with the identified neighbor network node, iii) to initiate an intra-Radio Access Technology (RAT) handover (e.g., Xn, NG or intra-node handover), iv) to initiate an inter-CN-based handover to the EPC network, and v) to initiate a release and redirect of the wireless device to the identified neighbor network node.
  • RAT Radio Access Technology
  • the method 1600 further includes the serving network node: based on a determination that the identified neighbor network node is connected to a EPC network, determining whether the wireless device is compatible with an eNodeB - EPC network connection and an eNodeB - 5GC network connection, and based on a determination that the wireless device is compatible with the eNodeB - EPC network connection and the eNodeB - 5GC network connection, initiating at least one of: i) an inter-CN-based handover to the EPC network and ii) a release and redirect of the wireless device to the identified neighbor network node.
  • the method 1600 further includes the serving network node: based on a determination that the identified neighbor network node is connected to the 5GC network, determining whether the wireless device is compatible with a eNodeB-5GC network connection; and based on a determination that the wireless device is compatible with the eNodeB-5GC network connection, determining at least one of: i) to configure carrier aggregation, ii) to configure dual connectivity with the identified neighbor network node, and iii) to initiate an intra-Radio Access Technology (RAT) handover (e.g., Xn, NG or intra-node handover).
  • RAT Intra Radio Access Technology
  • the method 1600 further includes the serving network node: based on a determination that the identified neighbor network node is connected to both a EPC network and the 5GC network, determining whether the wireless device is compatible with an eNodeB - EPC network connection and an eNodeB - 5GC network connection; and based on a determination that the wireless device is compatible with the eNodeB - EPC network connection and the eNodeB - 5GC network connection, determining at least one of: i) to configure carrier aggregation, ii) to configure dual connectivity with the identified neighbor network node, iii) to initiate an intra- adio Access Technology (RAT) handover (e.g., Xn, NG or intra-node handover), iv) to initiate an inter-RAT and inter-CN based handover to the EPC network, and v) to initiate a
  • RAT intra- adio Access Technology
  • the method 1600 further includes the serving network node: based on a determination that the identified neighbor network node is connected a EPC network, determining whether the wireless device is compatible with an eNodeB - EPC network connection; and based on a determination that the wireless device is compatible with the eNodeB - EPC network connection, initiating at least one of: i) an inter-RAT and inter-CN based handover to the EPC network and ii) a release and redirect of the wireless device to the identified neighbor network node.
  • the method 1600 further includes the serving network node: determining that the identified neighbor network node is connected to a 5GC network, wherein the serving node is at least one of a eNodeB and a gNodeB, the serving node connected to the 5GC network, and wherein the determined type of interface to establish between the serving network node and the neighbor network node is a Xn connection interface.
  • the method 1600 further includes the serving network node: determining that the identified neighbor network node is connected to both a EPC network and a 5GC network, wherein the serving node is at least one of a eNodeB and a gNodeB, the serving node connected to the 5GC network, and wherein the determined type of interface to establish between the serving network node and the neighbor network node is a Xn connection interface.
  • the method 1600 further includes the serving network node: determining that the identified neighbor network node is connected to both a EPC network and a 5GC network, wherein the serving node is a eNodeB to the EPC network, and wherein the determined type of interface to establish between the serving network node and the neighbor network node is a X2 connection interface.
  • the method 1600 further includes the serving network node: determining that the identified neighbor network node is connected to a EPC network, wherein the serving node is a eNodeB to the EPC network, and wherein the determined type of interface to establish between the serving network node and the neighbor network node is a X2 connection interface.
  • FIG. 17 depicts a method 1700, in accordance with particular embodiments, that is performed by a network node.
  • Method 1700 may begin at step 1702 in which the network node transmitting core network type information, wherein the core network type information indicates at least one of: i) that the neighbor network node is connected to a CN of a first type (e.g., an EPC network) and ii) that the neighbor network node is connected to a CN of a second type (e.g., a 5GC network).
  • the core network type information comprises a core network indicator indicating the core network type.
  • the core network type information comprises at least one of: Cell Global Identity (CGI), Tracking Area Codes, Core Network (CN) identifiers, and Public Land Mobile Network (PLMN) identifiers.
  • the network node may broadcast the core network type information to the wireless device as part of the transmitting the core network type information step.
  • Figure 18 illustrates a schematic block diagram of an apparatus 1800 in a wireless network (for example, the wireless network shown in Figure 6).
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device 610 or network node 660 shown in Figure 6).
  • Apparatus 1800 is operable to carry out the example method described with reference to Figure 15 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of Figure 15 is not necessarily carried out solely by apparatus 1800. At least some operations of the method can be performed by one or more other entities.
  • Virtual Apparatus 1800 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.
  • the processing circuitry may be used to cause acquiring unit 1802 to acquire core network type information transmitted by a neighbor network node, wherein the core network type information indicates at least one of: i) that the neighbor network node is connected to a core network (CN) of a first type (e.g., an evolved packet core (EPC) network) and ii) that the neighbor network node is connected to a CN of a second type (e.g., a 5G core network (5GC)), transmitter unit 1804 to transmit to a serving network node a report comprising identification information identifying the neighbor network node and core network type information indicating at least one of: i) that the identified neighbor network node is connected to a CN of the first type and ii) that the identified neighbor network node is connected to a CN of the second type, and any other suitable units of apparatus 1800 to perform corresponding functions according one or more embodiments of the present disclosure.
  • CN core network
  • a first type e.g., an evolved packet core (EPC
  • Figure 19 illustrates a schematic block diagram of an apparatus 1900 in a wireless network (for example, the wireless network shown in Figure 6).
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device 610 or network node 660 shown in Figure 6).
  • Apparatus 1900 is operable to carry out the example method described with reference to Figure 16 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of Figure 16 is not necessarily carried out solely by apparatus 1900. At least some operations of the method can be performed by one or more other entities.
  • Virtual Apparatus 1900 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.
  • the processing circuitry may be used to cause receiver unit 1902 to receive a report transmitted by a wireless device, wherein the report comprises identification information identifying the neighbor network node and core network type information indicating at least one of: i) that the identified neighbor network node is connected to a CN of a first type (e.g. an EPC network) and ii) that the identified neighbor network node is connected to a CN of a second type (e.g., a 5GC network), and any other suitable units of apparatus 1900 to perform corresponding functions according one or more embodiments of the present disclosure.
  • a first type e.g. an EPC network
  • a second type e.g., a 5GC network
  • Figure 20 illustrates a schematic block diagram of an apparatus 2000 in a wireless network (for example, the wireless network shown in Figure 6).
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device 610 or network node 660 shown in Figure 6).
  • Apparatus 2000 is operable to carry out the example method described with reference to Figure 17 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of Figure 17 is not necessarily carried out solely by apparatus 2000. At least some operations of the method can be performed by one or more other entities.
  • Virtual Apparatus 2000 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.
  • the processing circuitry may be used to cause transmitter unit 2002 to transmit transmitting core network type information, wherein the core network type information indicates at least one of: i) that the neighbor network node is connected to a CN of a first type (e.g., an EPC network) and ii) that the neighbor network node is connected to a CN of a second type (e.g., a 5GC network), and any other suitable units of apparatus 2000 to perform corresponding functions according one or more embodiments of the present disclosure.
  • a first type e.g., an EPC network
  • a second type e.g., a 5GC network
  • the term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • a method implemented in a wireless device comprising: acquiring core network (CN) type information transmitted by a neighbor network node, wherein the CN type information indicates at least one of: i) that the neighbor network node is connected to a core network (CN) of a first type (e.g., an evolved packet core (EPC) network) and ii) that the neighbor network node is connected to a CN of a second type (e.g., a 5G core network (5GC)); and
  • CN core network
  • CN core network
  • a first type e.g., an evolved packet core (EPC) network
  • EPC evolved packet core
  • a second type e.g., a 5G core network (5GC)
  • a serving network node transmitting to a serving network node a report comprising identification information identifying the neighbor network node and CN type information indicating at least one of: i) that the identified neighbor network node is connected to a CN of the first type and ii) that the identified neighbor network node is connected to a CN of the second type.
  • A2 The method of A2, wherein the neighbor network node is a eNodeB.
  • the CN type information comprises a CN indicator indicating a CN type.
  • the CN type information comprises at least one of: a Cell Global Identity (CGI), a Tracking Area Code, a CN identifier, and a Public Land Mobile Network (PLMN) identifier.
  • CGI Cell Global Identity
  • PLMN Public Land Mobile Network
  • A5. The method of A4, further comprising:
  • a CN type based on the at least one of: the CGI, the Tracking Area Code, the CN identifier, and the PLMN identifier.
  • a cell identifier e.g., PCI
  • system information broadcast associated with the cell identifier, wherein the system information broadcast comprises the CN type information
  • A8 The method of A6, wherein the acquiring the CN type information transmitted by the neighbor network node comprises:
  • system information comprises the CN type information
  • A9 The method of any one of A1-A8, further comprising:
  • the neighbor network node after acquiring the CN type information transmitted by the neighbor network node, determining, based on the acquired CN type information, whether the neighbor network node is connected to at least one of: i) a EPC network and ii) a 5GC network.
  • A10 The method of any one of A1-A9, wherein the identification information comprises a flag indicating whether the neighbor network node is connected to a 5GC network.
  • a method performed by a serving network node for establishing an interface with a neighbor network node comprising: receiving a report transmitted by a wireless device, wherein the report comprises identification information identifying the neighbor network node and core network type information indicating at least one of: i) that the identified neighbor network node is connected to a CN of a first type (e.g. an EPC network) and ii) that the identified neighbor network node is connected to a CN of a second type (e.g., a 5GC network).
  • a first type e.g. an EPC network
  • a second type e.g., a 5GC network
  • the identified neighbor network node is a eNodeB.
  • B4 The method of B3, wherein the serving network node is a eNodeB connected to a EPC network, the method further comprising:
  • RAT Radio Access Technology
  • B5. The method of B3, wherein the serving network node is a eNodeB connected to a EPC network, the method further comprising:
  • RAT Radio Access Technology
  • B6 The method of B3, wherein the serving network node is a eNodeB connected to a EPC network, the method further comprising:
  • the wireless device based on a determination that the identified neighbor network node is connected to a 5GC network, determining whether the wireless device is compatible with an eNodeB - EPC network connection and an eNodeB - 5GC network connection;
  • the wireless device based on a determination that the wireless device is compatible with the eNodeB - EPC network connection and the eNodeB - 5GC network connection, initiating at least one of: i) an inter-CN-based handover to the 5GC network and ii) a release and redirect of the wireless device to the identified neighbor network node.
  • B7 The method of B3, wherein the serving network node is a eNodeB connected to a 5GC network, the method further comprising:
  • RAT Radio Access Technology
  • B8 The method of B3, wherein the serving network node is a eNodeB connected to a 5GC network, the method further comprising:
  • RAT Radio Access Technology
  • B9 The method of B3, wherein the serving network node is an eNodeB connected to a 5GC network, the method further comprising:
  • the wireless device based on a determination that the identified neighbor network node is connected to a EPC network, determining whether the wireless device is compatible with an eNodeB - EPC network connection and an eNodeB - 5GC network connection, and
  • the wireless device based on a determination that the wireless device is compatible with the eNodeB - EPC network connection and the eNodeB - 5GC network connection, initiating at least one of: i) an inter-CN-based handover to the EPC network and ii) a release and redirect of the wireless device to the identified neighbor network node.
  • RAT Radio Access Technology
  • Bl 1 The method of B3, wherein the serving network node is a gNodeB connected to a 5GC network, the method further comprising: based on a determination that the identified neighbor network node is connected to both a EPC network and the 5GC network, determining whether the wireless device is compatible with an eNodeB - EPC network connection and an eNodeB - 5GC network connection; and
  • RAT Radio Access Technology
  • B12 The method of B3, wherein the serving network node is a gNodeB connected to a 5GC network, the method further comprising:
  • the wireless device based on a determination that the wireless device is compatible with the eNodeB - EPC network connection, initiating at least one of: i) an inter-RAT and inter-CN based handover to the EPC network and ii) a release and redirect of the wireless device to the identified neighbor network node.
  • B14 The method of B13, wherein the serving node is at least one of a eNodeB and a gNodeB, the serving node connected to the 5GC network, and
  • the determined type of interface to establish between the serving network node and the neighbor network node is a Xn connection interface.
  • B 15 The method of B3 , further comprising : determining that the identified neighbor network node is connected to both a EPC network and a 5GC network.
  • B16 The method of B15, wherein the serving node is at least one of a eNodeB and a gNodeB, the serving node connected to the 5GC network, and
  • the determined type of interface to establish between the serving network node and the neighbor network node is a Xn connection interface.
  • B17 The method of B15, wherein the serving node is a eNodeB to the EPC network, and wherein the determined type of interface to establish between the serving network node and the neighbor network node is a X2 connection interface.
  • B19 The method of B19, wherein the serving node is a eNodeB to the EPC network, and wherein the determined type of interface to establish between the serving network node and the neighbor network node is a X2 connection interface.
  • a method performed by a network node comprising:
  • the core network type information indicates at least one of: i) that the neighbor network node is connected to a CN of a first type (e.g., an EPC network) and ii) that the neighbor network node is connected to a CN of a second type (e.g., a 5GC network).
  • a first type e.g., an EPC network
  • a second type e.g., a 5GC network
  • the core network type information comprises a core network indicator indicating the core network type.
  • the core network type information comprises at least one of: Cell Global Identity (CGI), Tracking Area Codes, Core Network (CN) identifiers, and Public Land Mobile Network (PLMN) identifiers.
  • CGI Cell Global Identity
  • CN Core Network
  • PLMN Public Land Mobile Network
  • a wireless device comprising:
  • processing circuitry configured to perform any of the steps of any of the Group A embodiments.
  • a base station comprising:
  • processing circuitry configured to perform any of the steps of any of the Group B embodiments
  • power supply circuitry configured to supply power to the wireless device.
  • a user equipment comprising:
  • an antenna configured to send and receive wireless signals
  • radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry;
  • an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry
  • a battery connected to the processing circuitry and configured to supply power to the UE.
  • a communication system including a host computer comprising:
  • processing circuitry configured to provide user data
  • a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE),
  • UE user equipment
  • the cellular network comprises a base station having a radio interface and processing circuitry, the base station's processing circuitry configured to perform any of the steps of any of the Group B embodiments.
  • the communication system of the pervious embodiment further including the base station.
  • the communication system of the previous 2 embodiments further including the UE, wherein the UE is configured to communicate with the base station.
  • the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data
  • the UE comprises processing circuitry configured to execute a client application associated with the host application.
  • the host computer providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments.
  • a user equipment configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to performs the of the previous 3 embodiments.
  • a communication system including a host computer comprising:
  • processing circuitry configured to provide user data
  • a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE),
  • UE user equipment
  • the UE comprises a radio interface and processing circuitry, the UE's components configured to perform any of the steps of any of the Group A embodiments.
  • CI 3 The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.
  • the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data
  • the host computer initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A embodiments.
  • a communication system including a host computer comprising:
  • UE user equipment
  • the UE comprises a radio interface and processing circuitry, the UE's processing circuitry configured to perform any of the steps of any of the Group A embodiments.
  • the communication system of the previous 2 embodiments further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.
  • the processing circuitry of the host computer is configured to execute a host application
  • the UE's processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.
  • the UE's processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.
  • the host computer receiving user data transmitted to the base station from the UE, wherem the UE performs any of the steps of any of the Group A embodiments.
  • the user data to be transmitted is provided by the client application in response to the input data.
  • a communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station's processing circuitry configured to perform any of the steps of any of the Group B embodiments.
  • UE user equipment
  • the communication system of the previous embodiment further including the base station.
  • the communication system of the previous 2 embodiments further including the UE, wherein the UE is configured to communicate with the base station.
  • the processing circuitry of the host computer is configured to execute a host application; the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.
  • the host computer receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.
  • eNB RAN node supporting LTE radio access technology
  • E-CID Enhanced Cell-ID positioning method
  • E-SMLC Evolved- Serving Mobile Location Centre

Landscapes

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

Abstract

La présente invention concerne un dispositif sans fil configuré pour acquérir des informations sur un type de réseau central (CN) associées à une cellule voisine, les informations sur le type de CN indiquant que la cellule voisine est connectée à un réseau central (CN) d'un premier type et/ou à un CN d'un second type ; et pour transmettre à un nœud de réseau de desserte un rapport comprenant des informations d'identification associées à la cellule voisine ainsi que les informations sur le type de CN indiquant que la cellule voisine est connectée à un CN du premier type et/ou à un CN du second type. L'invention concerne également un nœud de réseau de desserte configuré pour recevoir le rapport transmis par le dispositif sans fil, le rapport comprenant les informations d'identification associées à la cellule voisine et les informations sur le type de réseau central indiquant que la cellule voisine est connectée à un CN du premier type et/ou à un CN du second type.
PCT/EP2018/077578 2017-10-10 2018-10-10 Notification d'informations sur un type de réseau central (cn) Ceased WO2019072904A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201762570388P 2017-10-10 2017-10-10
US62/570388 2017-10-10

Publications (1)

Publication Number Publication Date
WO2019072904A1 true WO2019072904A1 (fr) 2019-04-18

Family

ID=63857906

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2018/077578 Ceased WO2019072904A1 (fr) 2017-10-10 2018-10-10 Notification d'informations sur un type de réseau central (cn)

Country Status (1)

Country Link
WO (1) WO2019072904A1 (fr)

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110536341A (zh) * 2019-04-29 2019-12-03 中兴通讯股份有限公司 网络信息上报方法、装置、用户终端、服务节点和介质
CN111095987A (zh) * 2017-11-09 2020-05-01 Oppo广东移动通信有限公司 获取核心网类型的方法、接入网设备和核心网设备
CN112105037A (zh) * 2019-06-18 2020-12-18 中国电信股份有限公司 异系统测量信息传输方法和系统、计算机可读存储介质
US10911993B2 (en) 2017-10-10 2021-02-02 Telefonaktiebolaget Lm Ericsson (Publ) Report NSA/SA NR indicator
CN112449374A (zh) * 2019-09-04 2021-03-05 大唐移动通信设备有限公司 确定目标主基站以及关联目标辅基站的方法及装置
WO2021160103A1 (fr) * 2020-02-14 2021-08-19 华为技术有限公司 Procédé et dispositif de traitement d'identité globale de cellule (cgi)
CN114097274A (zh) * 2019-06-18 2022-02-25 三星电子株式会社 无线通信系统中处理切换的方法和ue
WO2022164712A1 (fr) 2021-01-28 2022-08-04 Sprint Spectrum L.P. Sélection commandée par ue entre un transfert inter-rat et une connectivité double inter-rat
US11800584B2 (en) * 2019-07-12 2023-10-24 Parallel Wireless, Inc. 5G mobile network with intelligent 5G non-standalone (NSA) radio access network (RAN)
US11974219B2 (en) 2018-04-05 2024-04-30 Nokia Technologies Oy Cell access procedure
WO2024108502A1 (fr) * 2022-11-24 2024-05-30 Oppo广东移动通信有限公司 Procédé de communication et appareil de communication

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
OPPO: "Discussion on ANR Functionality for eLTE", vol. RAN WG2, no. Prague, Czech Republic; 20171009 - 20171013, 28 September 2017 (2017-09-28), XP051354191, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_99bis/Docs/> [retrieved on 20170928] *
OPPO: "Discussion on EPC and 5GC Selection during Intra-LTE Handover with CN Type Change", vol. RAN WG2, no. Athens, Greece; 20180226 - 20180302, 13 February 2018 (2018-02-13), XP051398945, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fran/WG2%5FRL2/TSGR2%5F101/Docs/> [retrieved on 20180213] *
ZTE: "Discussion on gNB-eNB interface setup", vol. RAN WG3, no. Qingdao, China; 20170627 - 20170629, 26 June 2017 (2017-06-26), XP051302316, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN3/Docs/> [retrieved on 20170626] *

Cited By (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11838810B2 (en) 2017-10-10 2023-12-05 Telefonaktiebolaget Lm Ericsson (Publ) Report NSA/SA NR indicator
US12267737B2 (en) 2017-10-10 2025-04-01 Telefonaktiebolaget Lm Ericsson (Publ) Report NSA/SA NR indicator
US11641603B2 (en) 2017-10-10 2023-05-02 Telefonaktiebolaget Lm Ericsson (Publ) Report NSA/SA NR indicator
US10911993B2 (en) 2017-10-10 2021-02-02 Telefonaktiebolaget Lm Ericsson (Publ) Report NSA/SA NR indicator
CN111095987B (zh) * 2017-11-09 2021-12-03 Oppo广东移动通信有限公司 获取核心网类型的方法、接入网设备和核心网设备
CN111095987A (zh) * 2017-11-09 2020-05-01 Oppo广东移动通信有限公司 获取核心网类型的方法、接入网设备和核心网设备
US11974219B2 (en) 2018-04-05 2024-04-30 Nokia Technologies Oy Cell access procedure
CN110536341A (zh) * 2019-04-29 2019-12-03 中兴通讯股份有限公司 网络信息上报方法、装置、用户终端、服务节点和介质
US12284557B2 (en) 2019-06-18 2025-04-22 Samsung Electronics Co., Ltd. Method and UE for handling handover in wireless communication system
US12245079B2 (en) 2019-06-18 2025-03-04 China Telecom Corporation Limited Inter-system measurement information transmission method and system, and computer readable storage medium
CN112105037B (zh) * 2019-06-18 2021-12-14 中国电信股份有限公司 异系统测量信息传输方法和系统、计算机可读存储介质
CN114097274A (zh) * 2019-06-18 2022-02-25 三星电子株式会社 无线通信系统中处理切换的方法和ue
CN112105037A (zh) * 2019-06-18 2020-12-18 中国电信股份有限公司 异系统测量信息传输方法和系统、计算机可读存储介质
US11800584B2 (en) * 2019-07-12 2023-10-24 Parallel Wireless, Inc. 5G mobile network with intelligent 5G non-standalone (NSA) radio access network (RAN)
US20240205994A1 (en) * 2019-07-12 2024-06-20 Parallel Wireless, Inc. 5G Mobile Network With Intelligent 5G Non-Standalone (NSA) Radio Access Network (RAN)
CN112449374B (zh) * 2019-09-04 2022-05-03 大唐移动通信设备有限公司 确定目标主基站以及关联目标辅基站的方法及装置
CN112449374A (zh) * 2019-09-04 2021-03-05 大唐移动通信设备有限公司 确定目标主基站以及关联目标辅基站的方法及装置
US12445875B2 (en) 2020-02-14 2025-10-14 Huawei Technologies Co., Ltd. Cell global identity CGI processing method and device
WO2021160103A1 (fr) * 2020-02-14 2021-08-19 华为技术有限公司 Procédé et dispositif de traitement d'identité globale de cellule (cgi)
WO2022164712A1 (fr) 2021-01-28 2022-08-04 Sprint Spectrum L.P. Sélection commandée par ue entre un transfert inter-rat et une connectivité double inter-rat
EP4285644A4 (fr) * 2021-01-28 2024-11-27 Sprint Spectrum LLC Sélection commandée par ue entre un transfert inter-rat et une connectivité double inter-rat
US12452941B2 (en) 2021-01-28 2025-10-21 T-Mobile Usa, Inc. UE-controlled selection between inter-RAT handover and inter-RAT dual connectivity
WO2024108502A1 (fr) * 2022-11-24 2024-05-30 Oppo广东移动通信有限公司 Procédé de communication et appareil de communication

Similar Documents

Publication Publication Date Title
US12267737B2 (en) Report NSA/SA NR indicator
US12192832B2 (en) Determining security keys
EP4042748B1 (fr) Rapport de mesure pour des candidats de transfert conditionnel
CN112956230B (zh) 用于nr-dc中的测量配置的方法和装置
US11265746B2 (en) Configuring measurement reporting for new radio
US12538140B2 (en) Management of frequency bands selection and measurement configurations
WO2019072904A1 (fr) Notification d&#39;informations sur un type de réseau central (cn)
US12184563B2 (en) Measurement gap configuration in NE-DC and NR-NR DC
EP4104587B1 (fr) Coordination de capacité d&#39;équipement utilisateur pour ne-dc
US20250203437A1 (en) Handling of mismatch between ue and network early measurment handling capabilities during early measurement reporting
WO2021044375A1 (fr) Signalisation de capacité à connectivité multiple pour nœuds multiservices
WO2019226111A1 (fr) Procédés d&#39;indication de technologie d&#39;accès radio
US11882457B2 (en) Baseband processing capability handling in split deployment

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18786270

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18786270

Country of ref document: EP

Kind code of ref document: A1