WO2022243941A1 - Indication de capacité d'informations d'historique de mobilité - Google Patents

Indication de capacité d'informations d'historique de mobilité Download PDF

Info

Publication number
WO2022243941A1
WO2022243941A1 PCT/IB2022/054706 IB2022054706W WO2022243941A1 WO 2022243941 A1 WO2022243941 A1 WO 2022243941A1 IB 2022054706 W IB2022054706 W IB 2022054706W WO 2022243941 A1 WO2022243941 A1 WO 2022243941A1
Authority
WO
WIPO (PCT)
Prior art keywords
mhi
network node
indication
network
receiving
Prior art date
Application number
PCT/IB2022/054706
Other languages
English (en)
Inventor
Pradeepa Ramachandra
Angelo Centonza
Ioanna Pappa
Kristina Zetterberg
Ali PARICHEHREHTEROUJENI
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2022243941A1 publication Critical patent/WO2022243941A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • 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/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H04W36/0044—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information of quality context information
    • 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/0058—Transmission of hand-off measurement information, e.g. measurement reports

Definitions

  • the MHI measurements are accumulated by the UE (user equipment) independent of its RRC (Radio Resource Control) state (Idle/Inactive/Connected).
  • the UE stores the cell identifier which is the current serving cell for this UE and also stores the information related to how long the UE has stayed in this cell.
  • the UE further keeps such a history for up to past 16 serving cells.
  • the UE also includes information related to how long it has been out of the coverage scenario as well.
  • the procedural text related to the UE’s accumulation of the MHI information in LTE is in section 5.6.11 of TS 36.331 specification and the corresponding ASN.1 (Abstract Syntax Notation One) can be found in the IE (Information Element) VisitedCellInfoList in section 6.3.6 of TS 36.331.
  • This MHI herby referred to LTE-MHI is covering visited LTE cells.
  • the procedural text related to the UE’s accumulation of the MHI information in NR is in section 5.7.9 of TS 38.331 specification and the corresponding ASN.1 can be found in the IE VisitedCellInfoList in section 6.3.4 of TS 38.331.
  • This MHI herby referred to NR-LTE-MHI is covering both visited LTE cells and visited NR cells.
  • the UE can indicate the availability of this mobility history via the field mobilityHistoryAvail in either RRCSetupComplete or RRCResumeComplete messages. It is the RAT (Radio Access Technology) of the fetching cell that implicitly decides whether the UE will report the LTE-MHI or the NR-LTE MHI. Based on the MHI reported by the UE, the network can estimate the UE mobility characteristics like UE speed.
  • the specification TS 38.423 covers propagation of NR-LTE-MHI, but also propagation of NR-MHI is being discussed in standardization, see for example R3-211697.
  • One embodiment under the present disclosure comprises a method performed by a user equipment (UE) for indicating mobility history information (MHI) capability.
  • the method comprises transmitting a first indication to a first network node indicating that MHI associated with the UE is available; and receiving a handover command from the first network node, the handover command indicating that the UE is to be handed over to a second network node. It can further include transmitting, based on receiving the handover command, a second indication to the second network node indicating that the MHI associated with the UE is available.
  • Another embodiment can comprise a method performed by a network node for indicating MHI capability of a UE.
  • the method comprises receiving an indication indicating that MHI associated with the UE is available; and transmitting, based on receiving the indication and prior to receiving the MHI from the UE, a handover request based on determining that the UE is to be handed over to a second network node, the handover request including information to indicate that the UE is capable of providing the MHI.
  • a further embodiment comprises a method performed by a second network node for receiving an indication of MHI capability of a UE. The method comprises receiving a handover request for a UE; and receiving an indication that the UE is MHI capable.
  • Fig.1 shows a flow-chart of a method embodiment of the present disclosure
  • Fig.2 shows a flow-chart of a method embodiment of the present disclosure
  • Fig.3 shows a flow-chart of a method embodiment of the present disclosure
  • Fig.4 shows a flow-chart of a method embodiment of the present disclosure
  • Fig.5 shows a schematic of a process flow embodiment under the present disclosure
  • Fig.6 shows a schematic of a process flow embodiment under the present disclosure
  • Fig.7 shows a schematic of a process flow embodiment under the present disclosure
  • Fig. 12 shows a schematic of a user equipment embodiment under the present disclosure
  • Fig.13 shows a schematic of a network node embodiment under the present disclosure
  • Fig. 14 shows a schematic of a host embodiment under the present disclosure
  • Fig. 15 shows a schematic of a virtualization environment embodiment under the present disclosure
  • Fig. 16 shows a schematic representation of an embodiment of communication amongst nodes, hosts, and user equipment under the present disclosure.
  • DETAILED DESCRIPTION [00027]
  • the present disclosure is applicable to any multi- connectivity scenarios e.g., dual connectivity scenarios such as LTEDC (LTE Dual Connectivity), EN-DC (EUTRA-NR Dual Connectivity), NR-DU (NR Distributed Unit), NE-DC (NR-E-UTRA Dual Connectivity), etc.
  • network node and RAN node are used interchangeably.
  • a non-limiting example of a network node or a RAN node can be an eNB (Evolved NodeB (LTE base station)), gNB (base station in NR), gNB-CU (gNB Central Unit), gNB-CU-CP (gNB Central Unit Control Plane), gNB-DU (gNB Distributed Unit).
  • the term wireless terminal and UE are interchangeable and can refer to any device using the network node.
  • This information cannot be forwarded to the target node. Since the UE is already connected to the network, no new indication of MHI availability will be sent from the UE to the new node. The target node will then not be aware of that the UE has MHI capability, nor that the UE has an MHI available that has not yet been reported, and will not be able to perform MHI based optimizations.
  • Certain aspects of the disclosure and its embodiments may provide solutions to these or other challenges.
  • the UE can indicate the availability of MHI to the network in the RRCSetupComplete or RRCResumeComplete messages sent when a connection is established or resumed after being suspended.
  • the network node can then request for the UE to send the MHI in the UEInformationRequest message, and retrieve the MHI in the UEInformationResponse message.
  • the MHI can be propagated to the target node. This can serve the purpose of both transferring the MHI, and indicating that the UE is capable of collecting MHI.
  • the present disclosure includes methods using which the target node of a handover for a UE gets to know that the UE supports storage and reporting of MHI when the target node does not receive the previously reported MHI from the source node of the handover.
  • the target node gets this information from the source node and in some other embodiments of the present disclosure, the target node gets this information from the UE. This helps e.g., in cases where the UE has indicated MHI availability to the source node, but the source node did not fetch this information before handover and it helps in letting the target RAN (Radio Access Network) understand what type of MHI reporting the UE supports.
  • Radio Access Network Radio Access Network
  • an indication of MHI capability can be sent in a message from the source node to the target node upon handover. For example, this can be sent in the UE history information from the UE message, in case the UE has indicated MHI availability to the source node, but the source node did not fetch this information.
  • a capability indication or the MHI is included in the UE history information from the UE message.
  • the UE history information from the UE can contain separate capability indications to indicate availability of LTE-MHI, and/or availability of NR- LTE-MHI.
  • the indication may serve as an indicator that the UE is cable of collecting the MHI for LTE and/or for NR and as an indication that the MHI for LTE and/or LTE-NR is available at the UE.
  • the UE history information from the UE can contain an indication that the LTE-MHI and/or the NR-LTE-MHI is available at the UE and it has not been retrieved by the RAN.
  • the source RAN may transfer to the target RAN, via handover signaling messages, an outdated MHI, e.g., an MHI that was received from the UE while the UE was served by a different cell, or an MHI that was received from a different source RAN node, or it may not transfer to the target RAN any MHI (for LTE and/or for LTE-NR), and at the same time the source RAN may signal to the target RAN that a new MHI (the LTE-MHI and/or the NR-LTE- MHI) is available for retrieval at the UE.
  • an indication that the UE has NR- LTE-MHI capability can also serve as an indication that the UE has LTE-MHI capability.
  • an indication of MHI capability can be sent in a message from a source node to a target node upon handover, for example in the UE history information from the UE message, in case the source node may have received an indication of MHI capability upon a previous handover, but the source node did not fetch the MHI from the UE.
  • the term “indication of MHI capability” can refer to an indication that the UE is capable of collecting and reporting a specific version of the MHI, and/or that the UE has a specific version of the MHI available for retrieval. If only one of the foregoing capabilities is intended at a certain point in this description, then that will be set forth regarding the specific embodiment.
  • One embodiment can include a method performed by a UE (e.g., in RRC CONNECTED mode) that is connected to a first network node for indicating MHI capability to a second network node.
  • a UE e.g., in RRC CONNECTED mode
  • Step 110 is transmitting a first indication to a first network node indicating that MHI associated with the UE is available.
  • Step 120 is receiving a handover command from the first network node, the handover command indicating that the UE is to be handed over to a second network node.
  • Step 130 is transmitting, based on receiving the handover command, a second indication to the second network node indicating that the MHI associated with the UE is available.
  • the first and second network nodes belong to the same radio access technology. Sometimes the nodes may belong to different radio access technologies.
  • the handover command in step 120 may indicate, that the two nodes belong to the same radio access technology and/or that the first node has not fetched the MHI. Additional steps in method 100 can include receiving a request from the second network node to send the MHI, and then sending the MHI to the second network node.
  • the handover command in step 120 may indicate that the two nodes belong to different radio access technologies, and/or that the first node has not fetched the MHI.
  • the UE may want to perform an additional step in method 100 of storing information indicating that the first network node of a first radio access technology has not fetched the MHI. Additional possible steps in method 100 can include, upon connecting to a third network node belonging to the first radio access technology again, and if the stored third information indicates that the MHI was not fetched by the network node belonging to the first radio access technology, sending an indication to the third network node about the first indication, indication indicating the availability of the stored MHI.
  • Method 200 is a method performed by a network node for enabling the fetching of MHI from a UE by a second network node.
  • Step 210 is receiving an indication indicating that MHI associated with the UE is available. The indication in step 210 can be from a UE or a third network node.
  • Step 220 is transmitting, based on receiving the indication and prior to receiving the MHI from the UE, a handover request based on determining that the UE is to be handed over to a second network node, the handover request including information to indicate that the UE is capable of providing the MHI.
  • the information in step 220 may indicate that the UE has the capability to report the MHI towards a network node belonging to the first radio access technology.
  • the first and second network nodes may function on the same or different radio access technologies.
  • the handover request could be sent to the second network node, but in some situations may be sent to an MME/AMF, or to other network components.
  • the first network node may function on a first radio access technology and the second network node may function on a second radio access technology.
  • An additional optional step is receiving an acknowledgment from the second network node to handover the UE.
  • Another step can be sending a second indication to the UE, the said second indication indicating the UE to perform the mobility procedure to the second network node.
  • Method 300 is a method performed by a second network node belonging to a first radio access technology, to enable the fetching of the MHI from a UE by the second network node.
  • Step 310 is receiving a handover request from e.g., a first network node, MME, AMF, or other component, to handover the UE wherein the request includes a first indication that the UE has the capability to report the MHI towards a network node belonging to the first radio access technology.
  • Step 320 is sending an acknowledgment to e.g., the first network node, an MME or AMF, or other component, to handover the UE.
  • Step 330 is, upon the completion of the handover procedure by the UE, sending a request to transmit the MHI.
  • Step 340 is receiving the MHI from the UE.
  • Method 400 is a method performed by a second network node for fetching and/or receiving MHI from a UE.
  • Step 410 is receiving a handover request for a UE.
  • Step 420 is receiving an indication that the UE is MHI capable.
  • Optional steps include transmitting a request to the UE for the MHI, and receiving the MHI from the UE.
  • a target node will be made aware of whether the UE has MHI capabilities even if the MHI has not been fetched by the source node. The target node can then fetch the MHI and perform optimizations based on the MHI. Additional Embodiments [00044] As described above, the present disclosure includes methods using which the target node of a handover for a UE gets to know that the UE supports storage and reporting of MHI (e.g., has MHI capabilities). This can include when the target node does not receive the previously reported MHI from the source node of the handover and/or when the MHI has not been fetched by the source node.
  • MHI capabilities can include whether the UE is capable of collecting the MHI for LTE and/or for LTE-NR and whether the UE has an MHI available for retrieval. Such an information can be provided to the target cell of the handover either via the source cell or from the UE directly.
  • Scenario A – UE comes to RRC_Connected in NR Cell-A [00045] Scenario A and several of its variations are shown in Figures 5-10.
  • an MHI capability indication is included in a Handover Request (e.g., over X2/Xn interfaces) or Handover Required (e.g., over S1/NG interfaces) message.
  • the UE when the MHI has not been fetched by RAN node serving Cell-A, the UE includes the availability of the MHI information in an RRCReconfigurationComplete message sent to a RAN node serving target cell.
  • RRCReconfigurationComplete message sent to a RAN node serving target cell.
  • a UE comes to RRC_Connected in NR Cell-A and it indicates MHI availability, e.g., via RRCSetupComplete or RRCResumeComplete.
  • the need for handover from source NR Cell-A to target NR Cell-B is identified.
  • an MHI capability indication is included in the UE history information from the UE IE in the Handover Request (over X2/Xn interfaces (Interface between two eNBs in LTE/Interface between two gNBs in NR)) or Handover Required (over S1/NG interfaces (Single Interface between LTE RAN and evolved packet core/interface between NG-RAN and 5GC)) message.
  • the RAN node serving Cell-B can be aware of the existence of the MHI and it may correspondingly fetch it.
  • An example signal flow graph is shown in Figure 5. This example is associated to X2/Xn based procedure.
  • the source cell, NR Cell- A includes an indication in the HO (handover) Request message wherein the indication indicates that the UE supports the collection and reporting of MHI to an NR cell.
  • This information is used by the target cell, NR CellB to fetch the MHI from the UE.
  • the RAN node serving Cell-B also does not fetch the MHI from the UE, and if the RAN node serving Cell-B hands over this UE to another NR/LTE cell, then the RAN node serving Cell-B includes an indication in the Handover Request (over X2/Xn interfaces) or Handover Required (over S1/NG interfaces) message that the UE supports the feature of NR MHI information collection and reporting.
  • An example signal flow graph is shown in Figure 6. This example is associated to X2/Xn based procedure.
  • the source cell, NR cell-A includes an indication in the HO Request message wherein the indication indicates that the UE supports the collection and reporting of MHI to an NR cell.
  • This information is forwarded by the NR CellB to NR CellC which in turn uses this information to fetch the MHI from the UE.
  • the information related to the UE support for MHI reporting is still kept from the network point of view.
  • An example signal flow graph is shown in Figure 7. This example is associated to X2/Xn based procedure.
  • the source cell, NR cell-A includes an indication in the HO Request message wherein the indication indicates that the UE supports the collection and reporting of MHI to an NR cell.
  • This information is forwarded by the LTE CellB to NR CellC which in turn uses this information to fetch the MHI from the UE.
  • RRCReconfigurationComplete messages are used.
  • An example signal flow graph is shown in Figure 8. As a result, RAN node serving Cell-B is aware of the existence of the MHI at the UE and it may correspondingly fetch it.
  • the UE upon receiving the HO command before the source node serving NR CellA has fetched the MHI, the UE realizes that this information should be included in the RRCReconfigurationCompelte message to be sent to the NR CellB. This information is used by the NR CellB to fetch the MHI from the UE.
  • One important aspect of the embodiment of Figure 8 is the step at the UE wherein the UE recognizes that the source cell of the handover NRCellA has not fetched the MHI (e.g., the MHI is unavailable to NRCellA) from it despite sending a MHI availability indication to the NRCellA.
  • the same principle can be applied by the UE if the NR CellB also does not fetch the MHI report (e.g., the MHI is unavailable to NRCellB) from the UE and hands over this UE to another NR cell.
  • the MHI report e.g., the MHI is unavailable to NRCellB
  • FIGS 9-10 a couple examples are shown in Figures 9-10.
  • the NR CellB hands over the UE to another NR cell, NR CellC, before fetching the MHI from the UE.
  • the UE includes the MHI availability indication to the NR CellC.
  • the UE Upon inter-RAT handover, the UE does not have to use this indication as the MHI to be reported to an NR cell is different from an LTE cell.
  • the UE can retain the information that it has not reported the MHI associated to the RAT.
  • the UE is handed over from an NR cell, NR CellA, to an LTE Cell, LTE CellB, before the node serving NR CellA has fetched the MHI from the UE (e.g., the MHI is unavailable to NRCellA).
  • the UE can be then further handed over to NR Cell, NR CellC and then the UE indicates to the NR CellC that it has NR MHI available for reporting.
  • Scenario B – UE comes to connected in LTE Cell-A [00052]
  • the UE comes to connected in LTE Cell-A and it indicates MHI availability, e.g., via RRCConnectionSetupComplete or RRCConnectionResumeComplete. Then the need for handover from the source LTE Cell-A to the target NR Cell-B is identified.
  • MHI capability can be indicated in Handover Request or Handover Required messages, or in RRCConnectionReconfigurationComplete messaging: ⁇
  • an LTE-MHI capability indication is included in the UE history information from the UE IE in the Handover Request (over X2/Xn interfaces) or Handover Required (over S1/NG interfaces) message.
  • the UE since the MHI has not been fetched by the cell in which it performed state transition from RRC Inactive/Idle to RRC connected (i.e., LTE Cell-A), the UE includes the availability of the MHI information in the RRCConnectionReconfigurationComplete message sent to the LTE cell in the future upon performing a handover (from the NR cell).
  • the source RAN node serving LTE Cell-A had already fetched the MHI, then the source can include the MHI in the UE history information from the UE IE.
  • Scenario C – UE comes to connected in NR Cell-A, Cell-B deduces
  • the UE comes to connected in NR Cell-A and it indicates MHI availability, e.g., via RRCSetupComplete or RRCResumeComplete.
  • the RAN node serving Cell-A fetches MHI.
  • the need for handover from the source NR Cell-A to the target LTE Cell-B is then identified.
  • the RAN node serving Cell-B deduces, from presence of the MHI in the handover signalling from the RAN node serving Cell-A, that the UE is capable of producing an MHI for LTE and/or for LTE-NR (depending on the MHI that was forwarded from source RAN to target RAN). Hence, the RAN node serving Cell-B also fetches the MHI because it became aware of the capability by the UE of producing the MHI for LTE and/or LTE-NR. Next, the RAN node serving LTE Cell-B performs handover to another NR cell. Correspondingly the RAN node serving source Cell-B includes the MHI in the UE history information from the UE IE.
  • the need for handover from the source NR Cell-A to the target LTE Cell-B is then identified.
  • the RAN node serving Cell-B fetches the MHI.
  • the RAN node serving LTE Cell-B performs handover to another NR cell.
  • the source Cell-B includes the MHI in the UE history information from the UE IE.
  • Example Implementations [00056] The following provides an example implementation of the method wherein the UE includes an indication in the RRCReconfigurationComplete message about the availability of the MHI and also the corresponding procedural text.
  • the UE includes an indication in the RRCReconfigurationComplete message about the availability of the MHI and also the corresponding procedural text.
  • the UE performs the described actions upon reception of the RRCReconfiguration, or upon execution of the conditional reconfiguration (CHO or CPC): /*some part of the procedural text is skipped*/ 1> set the content of the RRCReconfigurationComplete message as follows: 2> if the RRCReconfiguration includes the masterCellGroup containing the reportUplinkTxDirectCurrent: 3> include the uplinkTxDirectCurrentList for each MCG serving cell with UL; 3> include uplinkDirectCurrentBWP-SUL for each MCG serving cell configured with SUL carrier, if any, within the uplinkTxDirectCurrentList; 2> if the RRCReconfiguration includes the masterCellGroup containing the reportUplinkTxDirectCurrentTwoCarrier: 3> include in the uplinkTxDirectCurrentTwoCarrierList the list of uplink Tx DC locations for the configured intra-band uplink carrier aggregation in the MCG; 2> if the RRCRe
  • the RRCReconfiguration message includes the mrdc- SecondaryCellGroupConfig with mrdc-SecondaryCellGroup set to eutra- SCG: 3> include in the eutra-SCG-Response the E-UTRA RRCConnectionReconfigurationComplete message in accordance with TS 36.331 [10] clause 5.3.5.3; 2> if the RRCReconfiguration message includes the mrdc- SecondaryCellGroupConfig with mrdc-SecondaryCellGroup set to nr- SCG: 3> include in the nr-SCG-Response the RRCReconfigurationComplete message; 2> if the UE has logged measurements available for NR and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport: 3> include the logMeasAvailable in the RRCReconfigurationComplete message; 3> if Bluetooth measurement results are included
  • An IE can contain information about mobility history report for a UE, such as given in Table 1: Table 1 [00059] In the above embodiments, it is evident that either the actual MHI can be forwarded from the source node to the target node or an indication of the UE’s ability to store and report the MHI, enabling the target node to itself proceed with fetching MHI, or both. [00060] Looking into TS 38.423 we see that currently the following is defined for the UE history information from the UE IE in Table 2.
  • This IE contains information about mobility history report for a UE: Table 2 [00061] Looking into TS 38.331 there is information about the UEInformationResponse message.
  • the UEInformationResponse message is used by the UE to transfer information requested by the network and can have the following characteristics: ⁇ Signalling radio bearer: SRB1 or SRB2 (when logged measurement information is included) ⁇ RLC-SAP: AM ⁇ Logical channel: DCCH ⁇ Direction: UE to network [00062]
  • a sample UEInformationResponse can be given as follows: ⁇ [00063] Another IE can be the VisitedCellInfoList.
  • the IE VisitedCellInfoList includes the mobility history information of a maximum of 16 most recently visited cells or time spent in any cell selection state and/or camped on any cell state in NR or E-UTRA.
  • the most recently visited cell is stored first in the list.
  • the list can include cells visited in RRC_IDLE, RRC_INACTIVE and RRC_CONNECTED states for NR and RRC_IDLE and RRC_CONNECTED for E-UTRA.
  • a sample VisitedCellInfoList information element follows: [00065] The VisitedCellInforList field description is given in Table 3. Table 3 [00066]
  • the VisitedCellInfoList-r16 in TS 38.331 can contain both NR and LTE entries.
  • the UE history information from the UE IE as defined in TS 38.423 should be enhanced in order to incorporate the possibility to include MHI based on TS 36.331, namely what has been previously referred to as the LTE MHI, which is an MHI containing E-UTRA cells.
  • the UE history information from the UE IE as defined in TS 38.423 should be enhanced in order to include this indication.
  • Table 4 [00069] In this example the NR Mobility History Supported and the LTE Mobility History Supported can be interpreted by the receiving node as notifying that the UE supports the reporting of the NRandLTEMobility History Report and/or LTE Mobility History Report. Additionally, the new IEs may indicate to the receiving nodes that the NRandLTEMobility History Report and/or LTE Mobility History Report are available at the UE for retrieval.
  • Figure 11 shows an example of a communication system 1100 in accordance with some embodiments.
  • the communication system 1100 includes a telecommunication network 1102 that includes an access network 1104, such as a radio access network (RAN), and a core network 1106, which includes one or more core network nodes 1108.
  • the access network 1104 includes one or more access network nodes, such as network nodes 1110a and 1110b (one or more of which may be generally referred to as network nodes 1110), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point.
  • 3GPP 3rd Generation Partnership Project
  • the network nodes 1110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1112a, 1112b, 1112c, and 1112d (one or more of which may be generally referred to as UEs 1112) to the core network 1106 over one or more wireless connections.
  • UE user equipment
  • Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors.
  • the communication system 1100 may include any number of wired or wireless networks, network nodes, UEs, 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.
  • the communication system 1100 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 1112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 1110 and other communication devices.
  • the network nodes 1110 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 1112 and/or with other network nodes or equipment in the telecommunication network 1102 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 1102.
  • the core network 1106 connects the network nodes 1110 to one or more hosts, such as host 1116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts.
  • the core network 1106 includes one more core network nodes (e.g., core network node 1108) that are structured with hardware and software components.
  • Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).
  • MSC Mobile Switching Center
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • SIDF Subscription Identifier De-concealing function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • the host 1116 may be under the ownership or control of a service provider other than an operator or provider of the access network 1104 and/or the telecommunication network 1102, and may be operated by the service provider or on behalf of the service provider.
  • the host 1116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
  • the communication system 1100 of Figure 11 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z- Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • 6G wireless local area network
  • WiFi wireless local area network
  • WiMax Worldwide Interoperability for Microwave Access
  • the telecommunication network 1102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1102. For example, the telecommunications network 1102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive IoT services to yet further UEs.
  • the UEs 1112 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 1104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1104.
  • a UE may be configured for operating in single- or multi-RAT or multi-standard mode.
  • a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio – Dual Connectivity (EN-DC).
  • MR-DC multi-radio dual connectivity
  • the hub 1114 communicates with the access network 1104 to facilitate indirect communication between one or more UEs (e.g., UE 1112c and/or 1112d) and network nodes (e.g., network node 1110b).
  • the hub 1114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 1114 may be a broadband router enabling access to the core network 1106 for the UEs.
  • the hub 1114 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • Commands or instructions may be received from the UEs, network nodes 1110, or by executable code, script, process, or other instructions in the hub 1114.
  • the hub 1114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data.
  • the hub 1114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1114 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 1114 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy IoT devices.
  • the hub 1114 may have a constant/persistent or intermittent connection to the network node 1110b.
  • the hub 1114 may also allow for a different communication scheme and/or schedule between the hub 1114 and UEs (e.g., UE 1112c and/or 1112d), and between the hub 1114 and the core network 1106.
  • the hub 1114 is connected to the core network 1106 and/or one or more UEs via a wired connection.
  • the hub 1114 may be configured to connect to an M2M service provider over the access network 1104 and/or to another UE over a direct connection.
  • UEs may establish a wireless connection with the network nodes 1110 while still connected via the hub 1114 via a wired or wireless connection.
  • the hub 1114 may be a dedicated hub – that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 1110b.
  • the hub 1114 may be a non-dedicated hub – that is, a device which is capable of operating to route communications between the UEs and network node 1110b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • Figure 12 shows a UE 1200 in accordance with some embodiments.
  • a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs.
  • Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc.
  • Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • 3GPP 3rd Generation Partnership Project
  • NB-IoT narrow band internet of things
  • MTC machine type communication
  • eMTC enhanced MTC
  • a UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to- everything (V2X).
  • D2D device-to-device
  • DSRC Dedicated Short-Range Communication
  • V2V vehicle-to-vehicle
  • V2I vehicle-to-infrastructure
  • V2X vehicle-to- everything
  • a 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).
  • the UE 1200 includes processing circuitry 1202 that is operatively coupled via a bus 1204 to an input/output interface 1206, a power source 1208, a memory 1210, a communication interface 1212, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 12. The level of integration between the components may vary from one UE to another UE.
  • the processing circuitry 1202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1210.
  • the processing circuitry 1202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above.
  • FPGAs field-programmable gate arrays
  • ASICs application specific integrated circuits
  • DSP digital signal processor
  • the processing circuitry 1202 may include multiple central processing units (CPUs).
  • the input/output interface 1206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices.
  • Examples of an output device include 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.
  • An input device may allow a user to capture information into the UE 1200.
  • Examples of an input device 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, a biometric sensor, etc., or any combination thereof.
  • An output device may use the same type of interface port as an input device.
  • a Universal Serial Bus (USB) port may be used to provide an input device and an output device.
  • the power source 1208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used.
  • the power source 1208 may further include power circuitry for delivering power from the power source 1208 itself, and/or an external power source, to the various parts of the UE 1200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1208.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1208 to make the power suitable for the respective components of the UE 1200 to which power is supplied.
  • the memory 1210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth.
  • the memory 1210 includes one or more application programs 1214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1216.
  • the memory 1210 may store, for use by the UE 1200, any of a variety of various operating systems or combinations of operating systems.
  • the memory 1210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), 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 tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof.
  • RAID redundant array of independent disks
  • HD- DVD high-density digital versatile disc
  • HD- DVD high-density digital versatile disc
  • the UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’
  • the memory 1210 may allow the UE 1200 to access instructions, application programs and 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 as or in the memory 1210, which may be or comprise a device-readable storage medium.
  • the processing circuitry 1202 may be configured to communicate with an access network or other network using the communication interface 1212.
  • the communication interface 1212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1222.
  • the communication interface 1212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network).
  • Each transceiver may include a transmitter 1218 and/or a receiver 1220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 1218 and receiver 1220 may be coupled to one or more antennas (e.g., antenna 1222) and may share circuit components, software or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 1212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof.
  • GPS global positioning system
  • Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/internet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
  • a UE may provide an output of data captured by its sensors, through its communication interface 1212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE.
  • a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change.
  • the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.
  • a UE when in the form of an Internet of Things (IoT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare.
  • Non-limiting examples of such an IoT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot.
  • UAV Un
  • a UE in the form of an IoT device comprises circuitry and/or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE 1200 shown in Figure 12.
  • a UE 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 UE and/or a network node.
  • the UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device.
  • the UE may implement the 3GPP NB-IoT standard.
  • a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone.
  • the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed.
  • the first and/or the second UE can also include more than one of the functionalities described above.
  • a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
  • Figure 13 shows a network node 1300 in accordance with some embodiments.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication 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 (eNBs) and NR NodeBs (gNBs)).
  • APs access points
  • BSs base stations
  • Node Bs evolved Node Bs
  • gNBs NR NodeBs
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may 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 (RRUs), 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 multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • OFDM Operation and Maintenance
  • OSS Operations Support System
  • SON Self-Organizing Network
  • positioning nodes e.g., Evolved Serving Mobile Location Centers (E-SMLCs)
  • the network node 1300 includes a processing circuitry 1302, a memory 1304, a communication interface 1306, and a power source 1308.
  • the network node 1300 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.
  • the network node 1300 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 NodeBs.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • the network node 1300 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • some components may be duplicated (e.g., separate memory 1304 for different RATs) and some components may be reused (e.g., a same antenna 1310 may be shared by different RATs).
  • the network node 1300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) 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 1300.
  • RFID Radio Frequency Identification
  • the processing circuitry 1302 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 1300 components, such as the memory 1304, to provide network node 1300 functionality.
  • the processing circuitry 1302 includes a system on a chip (SOC).
  • the processing circuitry 1302 includes one or more of radio frequency (RF) transceiver circuitry 1312 and baseband processing circuitry 1314.
  • RF radio frequency
  • the radio frequency (RF) transceiver circuitry 1312 and the baseband processing circuitry 1314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1312 and baseband processing circuitry 1314 may be on the same chip or set of chips, boards, or units.
  • the memory 1304 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 the processing circuitry 1302.
  • 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-
  • the memory 1304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 1302 and utilized by the network node 1300.
  • the memory 1304 may be used to store any calculations made by the processing circuitry 1302 and/or any data received via the communication interface 1306.
  • the processing circuitry 1302 and memory 1304 is integrated.
  • the communication interface 1306 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE.
  • the communication interface 1306 comprises port(s)/terminal(s) 1316 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 1306 also includes radio front-end circuitry 1318 that may be coupled to, or in certain embodiments a part of, the antenna 1310.
  • Radio front-end circuitry 1318 comprises filters 1320 and amplifiers 1322.
  • the radio front-end circuitry 1318 may be connected to an antenna 1310 and processing circuitry 1302.
  • the radio front-end circuitry may be configured to condition signals communicated between antenna 1310 and processing circuitry 1302.
  • the radio front-end circuitry 1318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection.
  • the radio front-end circuitry 1318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1320 and/or amplifiers 1322. The radio signal may then be transmitted via the antenna 1310. Similarly, when receiving data, the antenna 1310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1318. The digital data may be passed to the processing circuitry 1302. In other embodiments, the communication interface may comprise different components and/or different combinations of components. [000103] In certain alternative embodiments, the network node 1300 does not include separate radio front-end circuitry 1318, instead, the processing circuitry 1302 includes radio front- end circuitry and is connected to the antenna 1310.
  • the RF transceiver circuitry 1312 is part of the communication interface 1306.
  • the communication interface 1306 includes one or more ports or terminals 1316, the radio front-end circuitry 1318, and the RF transceiver circuitry 1312, as part of a radio unit (not shown), and the communication interface 1306 communicates with the baseband processing circuitry 1314, which is part of a digital unit (not shown).
  • the antenna 1310 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 1310 may be coupled to the radio front-end circuitry 1318 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 1310 is separate from the network node 1300 and connectable to the network node 1300 through an interface or port.
  • the antenna 1310, communication interface 1306, and/or the processing circuitry 1302 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna 1310, the communication interface 1306, and/or the processing circuitry 1302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.
  • the power source 1308 provides power to the various components of network node 1300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 1308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1300 with power for performing the functionality described herein.
  • the network node 1300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1308.
  • the power source 1308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry.
  • Embodiments of the network node 1300 may include additional components beyond those shown in Figure 13 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.
  • the network node 1300 may include user interface equipment to allow input of information into the network node 1300 and to allow output of information from the network node 1300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1300.
  • Figure 14 is a block diagram of a host 1400, which may be an embodiment of the host 1116 of Figure 11, in accordance with various aspects described herein.
  • the host 1400 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm.
  • the host 1400 may provide one or more services to one or more UEs.
  • the host 1400 includes processing circuitry 1402 that is operatively coupled via a bus 1404 to an input/output interface 1406, a network interface 1408, a power source 1410, and a memory 1412.
  • Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 12 and 13, such that the descriptions thereof are generally applicable to the corresponding components of host 1400.
  • the memory 1412 may include one or more computer programs including one or more host application programs 1414 and data 1416, which may include user data, e.g., data generated by a UE for the host 1400 or data generated by the host 1400 for a UE.
  • Embodiments of the host 1400 may utilize only a subset or all of the components shown.
  • the host application programs 1414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems).
  • the host application programs 1414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network.
  • the host 1400 may select and/or indicate a different host for over-the-top services for a UE.
  • the host application programs 1414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.
  • HLS HTTP Live Streaming
  • RTMP Real-Time Messaging Protocol
  • RTSP Real-Time Streaming Protocol
  • MPEG-DASH Dynamic Adaptive Streaming over HTTP
  • Figure 15 is a block diagram illustrating a virtualization environment 1500 in which functions implemented by some embodiments may be virtualized.
  • 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 any device described herein, 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.
  • Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host.
  • VMs virtual machines
  • hardware nodes such as a hardware computing device that operates as a network node, UE, core network node, or host.
  • the virtual node does not require radio connectivity (e.g., a core network node or host)
  • the node may be entirely virtualized.
  • Hardware 1504 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth.
  • Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1508a and 1508b (one or more of which may be generally referred to as VMs 1508), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 1506 may present a virtual operating platform that appears like networking hardware to the VMs 1508.
  • the VMs 1508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1506.
  • a virtual appliance 1502 may be implemented on one or more of VMs 1508, and the implementations may be made in different ways.
  • Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV).
  • 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.
  • a VM 1508 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 the VMs 1508, and that part of hardware 1504 that executes that VM forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 1508 on top of the hardware 1504 and corresponds to the application 1502.
  • Hardware 1504 may be implemented in a standalone network node with generic or specific components. Hardware 1504 may implement some functions via virtualization. Alternatively, hardware 1504 may be part of a larger cluster of hardware (e.g.
  • hardware 1504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes 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. In some embodiments, some signaling can be provided with the use of a control system 1512 which may alternatively be used for communication between hardware nodes and radio units.
  • Figure 16 shows a communication diagram of a host 1602 communicating via a network node 1604 with a UE 1606 over a partially wireless connection in accordance with some embodiments.
  • UE such as a UE 1112a of Figure 11 and/or UE 1200 of Figure 12
  • network node such as network node 1110a of Figure 11 and/or network node 1300 of Figure 13
  • host such as host 1116 of Figure 11 and/or host 1400 of Figure 14
  • embodiments of host 1602 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host 1602 also includes software, which is stored in or accessible by the host 1602 and executable by the processing circuitry.
  • the software includes a host application that may be operable to provide a service to a remote user, such as the UE 1606 connecting via an over-the-top (OTT) connection 1650 extending between the UE 1606 and host 1602.
  • OTT over-the-top
  • a host application may provide user data which is transmitted using the OTT connection 1650.
  • the network node 1604 includes hardware enabling it to communicate with the host 1602 and UE 1606.
  • the connection 1660 may be direct or pass through a core network (like core network 1106 of Figure 11) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • an intermediate network may be a backbone network or the Internet.
  • the UE 1606 includes hardware and software, which is stored in or accessible by UE 1606 and executable by the UE’s processing circuitry.
  • the software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1606 with the support of the host 1602.
  • a client application such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1606 with the support of the host 1602.
  • an executing host application may communicate with the executing client application via the OTT connection 1650 terminating at the UE 1606 and host 1602.
  • the UE's client application may receive request data from the host's host application and provide user data in response to the request data.
  • the OTT connection 1650 may transfer both the request data and the user data.
  • the UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 1650.
  • the OTT connection 1650 may extend via a connection 1660 between the host 1602 and the network node 1604 and via a wireless connection 1670 between the network node 1604 and the UE 1606 to provide the connection between the host 1602 and the UE 1606.
  • the connection 1660 and wireless connection 1670, over which the OTT connection 1650 may be provided, have been drawn abstractly to illustrate the communication between the host 1602 and the UE 1606 via the network node 1604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host 1602 provides user data, which may be performed by executing a host application.
  • the user data is associated with a particular human user interacting with the UE 1606.
  • the user data is associated with a UE 1606 that shares data with the host 1602 without explicit human interaction.
  • the host 1602 initiates a transmission carrying the user data towards the UE 1606.
  • the host 1602 may initiate the transmission responsive to a request transmitted by the UE 1606.
  • the request may be caused by human interaction with the UE 1606 or by operation of the client application executing on the UE 1606.
  • the transmission may pass via the network node 1604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1612, the network node 1604 transmits to the UE 1606 the user data that was carried in the transmission that the host 1602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the UE 1606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1606 associated with the host application executed by the host 1602. [000123] In some examples, the UE 1606 executes a client application which provides user data to the host 1602. The user data may be provided in reaction or response to the data received from the host 1602.
  • the UE 1606 may provide user data, which may be performed by executing the client application.
  • the client application may further consider user input received from the user via an input/output interface of the UE 1606.
  • the UE 1606 initiates, in step 1618, transmission of the user data towards the host 1602 via the network node 1604.
  • the network node 1604 receives user data from the UE 1606 and initiates transmission of the received user data towards the host 1602.
  • the host 1602 receives the user data carried in the transmission initiated by the UE 1606.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 1606 using the OTT connection 1650, in which the wireless connection 1670 forms the last segment. More precisely, the teachings of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, improved content resolution, better responsiveness, and/or extended battery lifetime.
  • factory status information may be collected and analyzed by the host 1602.
  • the host 1602 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host 1602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • the host 1602 may store surveillance video uploaded by a UE.
  • the host 1602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs.
  • the host 1602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.
  • 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 the OTT connection may be implemented in software and hardware of the host 1602 and/or UE 1606.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1650 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 may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 1650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1604.
  • measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 1602.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1650 while monitoring propagation times, errors, etc.
  • the computing devices described herein e.g., UEs, network nodes, hosts
  • other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein.
  • Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information 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 may process information 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.
  • computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components.
  • a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface.
  • non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
  • some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium.
  • some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner.
  • the processing circuitry can be configured to perform the described functionality.
  • the term “computer system” or “computing system,” as used herein is intended to include personal computers, desktop computers, laptop computers, tablets, hand-held devices (e.g., mobile telephones, PDAs, pagers), microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, multi-processor systems, network PCs, distributed computing systems, datacenters, message processors, routers, switches, and even devices that conventionally have not been considered a computing system, such as wearables (e.g., glasses).
  • the memory may take any form and may depend on the nature and form of the computing system.
  • the memory can be physical system memory, which includes volatile memory, non-volatile memory, or some combination of the two.
  • the term “memory” may also be used herein to refer to non-volatile mass storage such as physical storage media.
  • the computing system also has thereon multiple structures often referred to as an “executable component.”
  • the memory of a computing system can include an executable component.
  • executable component is the name for a structure that is well understood to one of ordinary skill in the art in the field of computing as being a structure that can be software, hardware, or a combination thereof.
  • an executable component may include software objects, routines, methods, and so forth, that may be executed by one or more processors on the computing system, whether such an executable component exists in the heap of a computing system, or whether the executable component exists on computer-readable storage media.
  • the structure of the executable component exists on a computer-readable medium in such a form that it is operable, when executed by one or more processors of the computing system, to cause the computing system to perform one or more functions, such as the functions and methods described herein.
  • Such a structure may be computer-readable directly by a processor—as is the case if the executable component were binary.
  • the structure may be structured to be interpretable and/or compiled—whether in a single stage or in multiple stages—so as to generate such binary that is directly interpretable by a processor.
  • executable component is also well understood by one of ordinary skill as including structures that are implemented exclusively or near-exclusively in hardware logic components, such as within a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), Program-specific Standard Products (ASSPs), System-on-a-chip systems (SOCs), Complex Programmable Logic Devices (CPLDs), or any other specialized circuit.
  • FPGA field programmable gate array
  • ASIC application specific integrated circuit
  • ASSPs Program-specific Standard Products
  • SOCs System-on-a-chip systems
  • CPLDs Complex Programmable Logic Devices
  • executable component is a term for a structure that is well understood by those of ordinary skill in the art of computing, whether implemented in software, hardware, or a combination thereof.
  • the terms “component,” “service,” “engine,” “module,” “control,” “generator,” or the like may also be used in this description. As used in this description and in this case, these terms—whether expressed with or without a modifying clause—are also intended to be synonymous with the term “executable component” and thus also have a structure that is well understood by those of ordinary skill in the art of computing.
  • the communication system may include a complex of computing devices executing any of the method of the embodiments as described above and data storage devices which could be server parks and data centers.
  • a computer is generally understood to comprise one or more processors or one or more controllers, and the terms computer, processor, and controller may be employed interchangeably.
  • the functions may be provided by a single dedicated computer or processor or controller, by a single shared computer or processor or controller, or by a plurality of individual computers or processors or controllers, some of which may be shared or distributed.
  • processor or “controller” also refers to other hardware capable of performing such functions and/or executing software, such as the example hardware recited above.
  • the various exemplary embodiments may be implemented in hardware or special purpose chips, circuits, software, logic, or any combination thereof.
  • some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor, or other computing device, although the disclosure is not limited thereto.
  • a computing system includes a user interface for use in communicating information from/to a user.
  • the user interface may include output mechanisms as well as input mechanisms. The principles described herein are not limited to the precise output mechanisms or input mechanisms as such will depend on the nature of the device.
  • output mechanisms might include, for instance, speakers, displays, tactile output, projections, holograms, and so forth.
  • input mechanisms might include, for instance, microphones, touchscreens, projections, holograms, cameras, keyboards, stylus, mouse, or other pointer input, sensors of any type, and so forth.
  • embodiments described herein may comprise or utilize a special purpose or general-purpose computing system.
  • Embodiments described herein also include physical and other computer-readable media for carrying or storing computer-executable instructions and/or data structures. Such computer-readable media can be any available media that can be accessed by a general purpose or special purpose computing system.
  • Computer-readable media that store computer-executable instructions are physical storage media.
  • Computer-readable media that carry computer-executable instructions are transmission media.
  • Computer-readable storage media include RAM, ROM, EEPROM, solid state drives (“SSDs”), flash memory, phase-change memory (“PCM”), CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other physical and tangible storage medium that can be used to store desired program code in the form of computer- executable instructions or data structures and that can be accessed and executed by a general purpose or special purpose computing system to implement the disclosed functionality or functionalities.
  • Computer-executable instructions may be embodied on one or more computer-readable storage media to form a computer program product.
  • Transmission media can include a network and/or data links that can be used to carry desired program code in the form of computer-executable instructions or data structures and that can be accessed and executed by a general purpose or special purpose computing system. Combinations of the above should also be included within the scope of computer-readable media.
  • program code in the form of computer-executable instructions or data structures can be transferred automatically from transmission media to storage media (or vice versa).
  • NIC network interface module
  • storage media can be included in computing system components that also—or even primarily—utilize transmission media.
  • a computing system may also contain communication channels that allow the computing system to communicate with other computing systems over, for example, a network. Accordingly, the methods described herein may be practiced in network computing environments with many types of computing systems and computing system configurations.
  • the disclosed methods may also be practiced in distributed system environments where local and/or remote computing systems, which are linked through a network (either by wired data links, wireless data links, or by a combination of wired and wireless data links), both perform tasks.
  • a distributed system environment the processing, memory, and/or storage capability may be distributed as well.
  • the disclosed methods may be practiced in a cloud computing environment. Cloud computing environments may be distributed, although this is not required. When distributed, cloud computing environments may be distributed internationally within an organization and/or have components possessed across multiple organizations.
  • cloud computing is defined as a model for enabling on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services).
  • the definition of “cloud computing” is not limited to any of the other numerous advantages that can be obtained from such a model when properly deployed.
  • a cloud-computing model can be composed of various characteristics, such as on-demand self-service, broad network access, resource pooling, rapid elasticity, measured service, and so forth.
  • a cloud-computing model may also come in the form of various service models such as, for example, Software as a Service (“SaaS”), Platform as a Service (“PaaS”), and Infrastructure as a Service (“IaaS”).
  • SaaS Software as a Service
  • PaaS Platform as a Service
  • IaaS Infrastructure as a Service
  • the cloud-computing model may also be deployed using different deployment models such as private cloud, community cloud, public cloud, hybrid cloud, and so forth.
  • Abbreviations and Defined Terms [000146] To assist in understanding the scope and content of this written description and the appended claims, a select few terms are defined directly below. Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the present disclosure pertains. [000147] The terms “approximately,” “about,” and “substantially,” as used herein, represent an amount or condition close to the specific stated amount or condition that still performs a desired function or achieves a desired result.
  • the terms “approximately,” “about,” and “substantially” may refer to an amount or condition that deviates by less than 10%, or by less than 5%, or by less than 1%, or by less than 0.1%, or by less than 0.01% from a specifically stated amount or condition.
  • Various aspects of the present disclosure, including devices, systems, and methods may be illustrated with reference to one or more embodiments or implementations, which are exemplary in nature.
  • the term “exemplary” means “serving as an example, instance, or illustration,” and should not necessarily be construed as preferred or advantageous over other embodiments disclosed herein.
  • reference to a singular referent includes one, two, or more referents unless implicitly or explicitly understood or stated otherwise.
  • reference to a plurality of referents should be interpreted as comprising a single referent and/or a plurality of referents unless the content and/or context clearly dictate otherwise.
  • reference to referents in the plural form e.g., “widgets” does not necessarily require a plurality of such referents. Instead, it will be appreciated that independent of the inferred number of referents, one or more referents are contemplated herein unless stated otherwise.
  • references in the specification to "one embodiment,” “an embodiment,” “an example embodiment,” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described. [000151] It shall be understood that although the terms “first” and “second” etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another.
  • first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments.
  • the term “and/or” includes any and all combinations of one or more of the associated listed terms.
  • the terms “comprises”, “comprising”, “has”, “having”, “includes” and/or “including”, when used herein, specify the presence of stated features, elements, and/or components etc., but do not preclude the presence or addition of one or more other features, elements, components and/ or combinations thereof.

Abstract

Des procédés et des systèmes, destinés à indiquer la capacité d'informations d'historique de mobilité (MHI) d'un équipement utilisateur (UE) dans un système de communication, sont décrits. Au cours d'une procédure de transfert intercellulaire, une cellule ou un nœud cible peut ne pas connaitre la capacité MHI de l'UE. Dans certains modes de réalisation, un nœud de réseau source peut indiquer la capacité MHI de l'UE dans un message de transfert intercellulaire. Dans certains modes de réalisation, l'UE peut indiquer sa capacité MHI au nœud cible lorsqu'il réalise que le nœud source n'a pas récupéré les MHI.
PCT/IB2022/054706 2021-05-19 2022-05-19 Indication de capacité d'informations d'historique de mobilité WO2022243941A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202163190774P 2021-05-19 2021-05-19
US63/190,774 2021-05-19

Publications (1)

Publication Number Publication Date
WO2022243941A1 true WO2022243941A1 (fr) 2022-11-24

Family

ID=82214122

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2022/054706 WO2022243941A1 (fr) 2021-05-19 2022-05-19 Indication de capacité d'informations d'historique de mobilité

Country Status (1)

Country Link
WO (1) WO2022243941A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2833657A1 (fr) * 2012-03-26 2015-02-04 Samsung Electronics Co., Ltd. Procédé et dispositif pour la préservation de données de mobilité lors d'une transition d'état d'un terminal, et pour un nouvel accès réussi dans un réseau cellulaire hétérogène dans un système de communication mobile
WO2018208199A1 (fr) * 2017-05-12 2018-11-15 Telefonaktiebolaget Lm Ericsson (Publ) Procédés de fonctionnement de terminaux sans fil et de nœuds de réseau, terminaux sans fil et nœuds de réseau associés

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2833657A1 (fr) * 2012-03-26 2015-02-04 Samsung Electronics Co., Ltd. Procédé et dispositif pour la préservation de données de mobilité lors d'une transition d'état d'un terminal, et pour un nouvel accès réussi dans un réseau cellulaire hétérogène dans un système de communication mobile
WO2018208199A1 (fr) * 2017-05-12 2018-11-15 Telefonaktiebolaget Lm Ericsson (Publ) Procédés de fonctionnement de terminaux sans fil et de nœuds de réseau, terminaux sans fil et nœuds de réseau associés

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 16)", vol. RAN WG2, no. V16.5.0, 29 March 2021 (2021-03-29), pages 1 - 391, XP052000108, Retrieved from the Internet <URL:https://ftp.3gpp.org/Specs/archive/36_series/36.300/36300-g50.zip 36300-g50.docx> [retrieved on 20210329] *

Similar Documents

Publication Publication Date Title
WO2023014257A1 (fr) Maintenance de configuration de qualité d&#39;expérience
WO2023203240A1 (fr) Cas d&#39;utilisation du découpage du réseau pour l&#39;accès sans fil fixe (fwa)
WO2023022642A1 (fr) Signalisation de surchauffe prédite d&#39;ue
WO2022243941A1 (fr) Indication de capacité d&#39;informations d&#39;historique de mobilité
WO2024027838A1 (fr) Procédé et appareil pour arrêter un rapport de localisation
WO2024027839A1 (fr) Procédé et appareil de configuration de type de rapport d&#39;emplacement
US20240129704A1 (en) Public Warning System (PWS) Reception by Aerial User Equipment (UE)
WO2023122972A1 (fr) Procédé et appareil permettant de maintenir une session active dans un réseau de communication
WO2024069477A1 (fr) Transfert de rapport de cellule pscell réussi
WO2024035305A1 (fr) Rapport de réussite de changement ou d&#39;ajout de pscell
WO2023068983A1 (fr) Rapport de mesurage basé sur des configurations de mesurage utilisant des indications de priorité spécifiques à la fréquence
WO2024035304A1 (fr) Signalisation de réseau de rapport de pscell réussie
WO2023187685A1 (fr) Collecte de données à partir d&#39;un équipement utilisateur sur une utilisation de politique de sélection d&#39;itinéraire d&#39;équipement utilisateur
WO2023067504A1 (fr) Calcul de priorités de resélection de cellules combinées avec resélection de cellule de base de tranche
WO2024096791A1 (fr) Configuration de changement de scell primaire conditionnel intra-nœud secondaire
WO2023152683A1 (fr) Changement de pscell conditionnel initié par un nœud secondaire
WO2023014260A1 (fr) Approches de signalisation pour plmn de catastrophe
WO2024035309A1 (fr) Procédés, appareil et support lisible par ordinateur associés à un changement conditionnel de cellule
WO2024063692A1 (fr) Gestion de signalisation de positionnement associée à un dispositif de communication au moyen d&#39;une fonction de gestion d&#39;accès et de mobilité locale
WO2023073656A1 (fr) Procédés pour la visibilité de ran d&#39;une session d&#39;enregistrement de qoe
WO2024033811A1 (fr) Signalisation de contexte d&#39;ue et de données de ng-ran à un réseau cœur
WO2023011942A1 (fr) Rapport de relaxation de mesure radio précoce
WO2023068977A1 (fr) Rapport de mesurage de mdt pour équipements utilisateurs se trouvant dans n&#39;importe quel état de sélection de cellule
WO2024019652A1 (fr) Stockage de configurations qoe et rvqoe dans rrc_idle
WO2023166448A1 (fr) Rapport de mesurage b1/a4 optimisé

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE