Method and related wireless device for providing information message including RACH report
By managing and reporting RACH report lists in wireless devices, the problems of frequent RACH conflicts and low efficiency of existing reporting methods are resolved, RACH configuration is optimized, and the efficiency and resource utilization of the RACH process are improved.
Patent Information
- Application Number
- CN202210732349.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2019-12-09
- Filing Date
- 2020-08-19
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2040-08-19
AI Technical Summary
In existing technologies, improper RACH configuration leads to frequent RACH conflicts, affecting call setup and handover delays. Furthermore, existing RACH reporting methods are inefficient and cannot effectively optimize RACH parameters and resource configurations.
By storing and managing a list of RACH reports in wireless devices, including information on multiple RACH processes, and reporting to the network as appropriate, RACH configuration can be optimized, reducing storage requirements and communication overhead.
It improves the efficiency of RACH reporting and radio resource utilization, helps networks identify and resolve RACH-related issues more quickly, optimizes RACH parameter configuration, and reduces collisions and latency.
Smart Images

Figure CN115243287B_ABST
Abstract
Description
[0001] This application is a divisional application of the Chinese national phase application (application number: 202080083385.6) of PCT international application PCT / SE2020 / 050798 (filing date: August 19, 2020) entitled "Method for providing information messages including RACH reports and related wireless devices". Technical Field
[0002] The present disclosure relates generally to communications, and more particularly to communication methods and related devices and nodes that support wireless communications. Background Art
[0003] RACH (Random Access Channel) improvements / optimizations in LTE (Long Term Evolution) are discussed below.
[0004] Improvement / optimization of RACH configuration in a cell is a Release 9 SON feature that is key to optimizing system performance in mobile networks. Improperly configured RACH can lead to higher call setup and handover delays due to frequent RACH collisions or due to low preamble detection probability and limited coverage. The amount of uplink resources reserved for RACH also has an impact on system capacity. Therefore, network operators should carefully monitor whether RACH parameters are set in an appropriate manner, taking into account factors such as RACH load, uplink interference, traffic patterns and population under the cell coverage. The task becomes more complex as these factors can change dynamically. For example, if the antenna elevation angle in a cell changes, it affects the call arrival rate and handover rate in this cell and surrounding cells, which in turn affects the RACH load per preamble in all these cells. Changes in transmit power settings or handover thresholds can have similar effects.
[0005] Whenever such a network configuration change occurs, the RACH self-optimization function should automatically make appropriate measurements of RACH performance and usage within all affected cells and determine any necessary updates to RACH parameters. Some useful measurements are UE reporting of the number of RACH attempts required to achieve access, or the time elapsed from the first attempt until access was finally granted. RACH parameters that may subsequently be adjusted typically include one or more of the following: RACH preamble splitting between contention-free access, contention-based high load access, and contention-based low load access; RACH backoff parameter value or RACH transmit power ramp parameter; and / or any other parameters that the network operator deems useful.
[0006] In addition, the RACH optimization function helps to automatically configure PRACH parameters (including PRACH (Physical Random Access Channel) resource configuration, preamble root sequence and cyclic shift configuration) to avoid preamble conflicts with neighboring cells. The principle of this automatic configuration is similar to the automatic PCI (Physical Cell Identifier) configuration SON (Self-Optimizing / Organizing Network) function: PRACH configuration information is included in the "X2 Setup" and "eNB Configuration Update" processes. Therefore, whenever a new eNodeB is initialized and learns about its neighbors through the ANR (Automatic Neighbor Relation) function, the eNodeB can learn about the neighboring PRACH configurations at the same time. Then, it can choose its own PRACH configuration to avoid conflicts with these neighboring PRACH configurations.
[0007] Whenever a conflict is identified, one of the cells should change its configuration, but the algorithm used to select which cell should be changed and in what manner is not clearly stated. If necessary, network operators can also combine PRACH self-optimization with manual configuration, but this is generally more error-prone and time-consuming than automatic RACH optimization. Reporting of RACH information and failures.
[0008] The logging and reporting of RACH information in LTE is discussed below.
[0009] In LTE, in case the RACH procedure is successful, the network can request to report RACH information when performing the random access procedure via the UE Information procedure in RRC (Section 5.6.5). As described in the RRC (Radio Resource Control) specification, the procedure is summarized as follows.
[0010] The following discusses UE (User Equipment) information from Sections 5.6.5, 5.6.5.1, 5.6.5.2, and 5.6.5.3 of 3GPP TS 36.331 V15.7.0 (2019-09) (referred to as Reference [1]). Figure 6 .5.6.1-1 provides the UE information procedure, which is reproduced as Figure 4 .
[0011] The UE Information procedure is used by E-UTRAN (Evolved Universal Mobile Telecommunications System Terrestrial Radio Access Network) to request the UE to report information.
[0012] As described in section 5.6.5.2 of reference [1], the E-UTRAN initiates this procedure by sending a UEInformationRequest message. The E-UTRAN shall initiate this procedure only after security activation is successful.
[0013] The reception of the UEInformationRequest message is discussed in section 5.6.5.3 of reference [1].
[0014] After receiving the UEInformationRequest message, and only after successful security activation, the UE shall:
[0015] 1> If rach-ReportReq is set to true, the content of rach-Report is set in the UEInformationResponse message as follows:
[0016] 2> numberOfPreamblesSent is set to indicate the number of preambles sent by the MAC for the most recently successfully completed random access procedure;
[0017] 2> If contention resolution was not successful for at least one transmitted preamble of the most recently completed successfully random access procedure (as specified in TS 36.321 [6]):
[0018] 3> Set contentionDetected to true;
[0019] 2> Otherwise:
[0020] 3>Set contentionDetected to false; ...
[0022] 1> Otherwise:
[0023] 2> Submit the UEInformationResponse message to the lower layer for transmission via SRB1;
[0024] UEInformationRequest is a command used by E-UTRAN to obtain information from UE.
[0025] The UEInformationResponse message is used by the UE to transmit the information requested by the E-UTRAN.
[0026] In summary, for each RACH procedure, the UE stores and possibly reports whether contention was detected for at least one transmitted preamble, as described in TS 36.321 (also referred to as reference [2]). Random access in LTE can be configured as contention-based random access (CBRA), meaning that there is an inherent risk of collision, or as contention-free, where resources are reserved by the network for a given UE at a given time.
[0027] In the CBRA procedure, the RACH preamble is randomly selected by the UE, which may result in more than one UE transmitting the same signature at the same time, necessitating a subsequent contention resolution process. For some use cases where random access is used (e.g. handover), the eNodeB may choose to prevent contention by assigning a dedicated signature to the UE, thereby achieving contention-free access. This is faster than contention-based access (a particularly important factor for time-critical handover situations), but it still requires the network to reserve resources, which may not be very efficient. There are a fixed number of preambles available in each LTE cell (64), and the operation of the two types of RACH procedures depends on the division of these signatures between those used for contention-based access and those reserved for assignment to specific UEs on a contention-free basis.
[0028] In LTE, the UE can obtain the RACH configuration in SIB2 (System Information Block 2) in the IE (Information Element) RadioResourceConfigCommonSIB (e.g., when it switches from idle to connected) or in RadioResourceConfigCommon (e.g., when it is handed over to another cell). In both cases, the UE contains the field rach-ConfigCommon of the IE RACH-ConfigCommon.
[0029] Combine the following Figure 5 The message diagram summarizes the CBRA process.
[0030] Combination Figure 5 Operation 1 of FIG. 1 discusses RACH preamble transmission. In operation 1, the UE shall select a preamble to be transmitted. The UE selects an available preamble for CBRA (i.e., 64 minus the number of preambles reserved for CFRA contention-free random access). This maximum value is provided as shown in Table 1 for use in the rach-ConfigCommon information element.
[0031] Table 1
[0032]
[0033] The contention-based signature set is further subdivided into two subgroups so that the selection of a signature can carry 1-bit information about the amount of transmission resources required to send the message in step 3.
[0034] From an L1 (layer 1) perspective, the preamble is sent in the so-called Physical Random Access Channel (PRACH), which is time- and frequency-multiplexed with the PUSCH (Physical Uplink Shared Channel) and the PUCCH (Physical Uplink Control Channel), as shown in Figure 6 shown.
[0035] On the network side, these are the resources that are monitored to detect any RACH attempts. The PRACH time-frequency resources are semi-statically allocated within the PUSCH region and are repeated periodically. The exact PRACH configuration (i.e. the L1 aspect of the RACH) is part of the RadioResourceConfigCommonSIB (e.g. when it transitions from idle to connected) or in the RadioResourceConfigCommon (when it is handed over to another cell). In both cases, the UE contains the field prach-Config of the IE PRACH-ConfigSIB or PRACH-Config.
[0036] Combination Figure 6 Operation 2 of discusses the reception of a RAR (Random Access Response) message with a temporary C-RNTI (Cell Radio Network Temporary Identifier).
[0037] In operation 2, after sending the preamble, the UE starts monitoring the reception of a Random Access Response (RAR) message. This message is sent in a Physical Downlink Shared Channel (PDSCH) and scheduled in a Physical Downlink Control Channel (PDCCH).
[0038] To detect and decode RAR, the UE monitors the SpCell PDCCH identified by the RA-RNTI (e.g., instead of the C-RNTI, typically used for connected mode UEs to schedule data or control information on the PDCCH / PDSCH). The exact RA-RNTI value used by the UE in such monitoring is known based on the selected preamble, since the RA-RNTI sent by the network explicitly identifies which time-frequency resource the MAC (Media Access Control) entity used to send the RACH preamble. Therefore, before monitoring, the UE performs a specified mapping between the PRACH resource it selected to send the preamble and the RA-RNTI that will be monitored in the RAR window to decode its RAR.
[0039] Therefore, if multiple UEs collide by selecting the same preamble in the same time-frequency resources, they will each receive a RAR with the same RA-RNTI (Random Access Radio Network Temporary Identifier). The RAR conveys the identity of the detected preamble, timing alignment instructions for synchronizing subsequent uplink transmissions from the UE, an initial uplink resource grant for transmission of the step 3 message, and an assignment of a temporary Cell Radio Network Temporary Identifier (C-RNTI) (which may or may not become permanent, depending on the next step (contention resolution)). The RAR message may also include a "backoff indicator" that the eNodeB may set to instruct the UE to back off for a period of time before retrying the RACH attempt.
[0040] Figure 5 The elements of MAC (Media Access Control) RAR (Random Access Response) in operation 2 are as follows Figure 7 shown.
[0041] If the timer associated with the RAR time window expires before the UE receives the RAR, the UE applies a power ramp before retransmitting the preamble. This behavior continues until the process succeeds or the maximum number of attempts is reached (then RACH failure is declared).
[0042] In operation 3, message 3 is sent together with the UE-identity on RRC.
[0043] In operation 3, the UE sends the so-called Message 3 (MSG.3). This is the first scheduled uplink transmission on PUSCH. It conveys the actual procedure message, such as RRC Connection Request, RRC Recovery Request, etc. It is addressed to the temporary C-RNTI allocated in the RAR at step 2 and carries the C-RNTI or the initial UE identity. This message relies on HARQ (Hybrid Automatic Repeat Request) retransmissions.
[0044] If a preamble collision has occurred in operation 1, the colliding UEs will receive the same temporary C-RNTI via the RAR and will also collide in the same uplink time-frequency resources when sending their MSG.3 (because they have received the same RAR). This may cause interference that makes the colliding UEs unable to decode, and the UEs restart the RACH process after reaching the maximum number of HARQ retransmissions, which may avoid the need for contention resolution (unless they select the same preamble again, which is unlikely).
[0045] However, if at least one UE is successfully decoded, then in this step the contention remains unresolved for the other UEs. The MAC downlink message (in operation 4) allows this contention to be quickly resolved.
[0046] Contention resolution occurs at operation 4.
[0047] If for at least one UE sending MSG.3 its content can be detected (suitably acknowledged by the network with HARQ), then in operation 4, a contention resolution message is required.
[0048] The contention resolution message also uses HARQ. It is addressed to the C-RNTI (if indicated in the MSG.3 message) or to a temporary C-RNTI (tC-RNTI). In the latter case, the message reproduces the UE identity contained in the RRC message (e.g., recovery identifier, s-TMSI, etc.). The reason for distinguishing these two cases is that if the UE is performing RACH during a handover with CBRA, the target cell will allocate a C-RNTI in the handover command (prepared by the target), and this C-RNTI should be a unique C-RNTI. Therefore, as an indication to the target that MSG.3 (in this example, the RRCConfigurationComplete message) was detected, MSG4 is sent to the same C-RNTI. It is assumed that the C-RNTI allocated by the target is unique and there is no source of confusion, i.e., if another UE receives this message 4 with a C-RNTI that does not belong to it, it knows that a conflict has occurred.
[0049] In another case, when the UE does not have a target assigned C-RNTI, MSG.4 uses a temporary C-RNTI. And, in the case where it may be forwarded to a different UE, the network needs to indicate for which UE MSG.3 has been decoded and for which UE the network wants to indicate that the contention has been resolved. This is done by reproducing the UE identifier (e.g., recovery identifier, S-TMSI, etc.) in the RRC message, which is very unlikely to be the same.
[0050] In the event of a collision after successfully decoding MSG.3, HARQ feedback is sent only by the UE that detects its own UE identity (or C-RNTI); other UEs understand the existence of a collision, do not send HARQ feedback, and can quickly exit the current RACH process and start another RACH process. Therefore, there are three possibilities for the UE's behavior after receiving a contention resolution message: the UE correctly decodes the message and detects its own identity: it sends back a positive acknowledgement (ACKnowledgement, "ACK"); the UE correctly decodes the message and finds that it contains the identity of another UE (contention resolution): it sends nothing back (discontinuous transmission, "DTX"); and, the UE fails to decode the message or misses a DL grant: it sends nothing back ("DTX").
[0051] An example is shown below where two UEs may attempt to perform a transition from idle to connected when a collision occurs. Figure 8 shown.
[0052] The following discusses what happens after a race is detected.
[0053] As described above, if the UE receives in MSG.4 its C-RNTI assigned by the target, or its temporary C-RNTI and its UE identifier sent in MSG.3, the UE considers contention resolution to be successful. Otherwise, if the contention resolution timer expires, or if the UE receives a MSG.4 with its temporary C-RNTI but with a different UE identifier, the UE considers contention resolution to have failed and re-initiates the random access procedure. It should be noted that the network cannot see that a collision has occurred, since the next attempt may succeed. Therefore, the indication in the RACH report is actually the UE detecting a collision by detecting that the MSG.4 content is not addressed to itself.
[0054] Contention detection and contention resolution processing in LTE is described in 3GPP TS 36.321 V15.7.0 (2019-09), also referred to as reference [2]. Random access procedure initialization is discussed in section 5.1.1 of reference [2], while contention resolution is discussed in section 5.1.5 of reference [2].
[0055] As in LTE, the random access procedure is described in the NR MAC specification and the parameters are configured by RRC, for example in system information or in handover (RRCReconfiguration with reconfigurationWithSync). Random access is triggered in many different scenarios, for example when the UE is in RRC_IDLE or RRC_INACTIVE and wants to access the cell it is camping on (i.e. transitioning to RRC_CONNECTED).
[0056] In NR, the RACH configuration is broadcasted in SIB1 as part of servingCellConfigCommon (with DL configuration and UL configuration), where the RACH configuration is in uplinkConfigCommon. The exact RACH parameters are in the so-called initialUplinkBWP, the reason for this is that this is the part of the UL (uplink) frequency that the UE should access and search for RACH resources.
[0057] In LTE, the RACH report used to help the network perform RACH optimization contains an indication that a collision was detected. With this information, it is obvious that at some point before this RACH procedure that had been successful, the same UE attempted to access the network and happened to collide.
[0058] In NR, there is also a contention resolution mechanism for contention-based random access. In NR, random access resource selection needs to be performed within a cell based on measurements performed on SSBs (Synchronization Signal Blocks) or CSI-RS (Channel State Information Reference Signals). A cell in NR is basically defined by a set of these SSBs, which can be Fig. 9A 1 downlink beam as shown (typical implementation at lower frequencies, e.g. below 6 GHz) or Fig. 9B The SSBs are sent in multiple downlink beams as shown (a typical implementation for lower frequencies, e.g. below 6 GHz). For the same cell, these SSBs carry the same physical cell identifier (PCI) and MIB. For standalone operation (i.e. supporting UEs residing in NR cells), they also carry the RACH configuration in SIB1, which includes a mapping between the SSBs covering the UE detected at a given point in time and the PRACH configuration to be used (e.g. time, frequency, preamble, etc.). To this end, each of these beams can send its own SSB, which can be distinguished by the SSB index.
[0059] The mapping between RACH resources and SSBs (or CSI-RS) is also provided as part of the RACH configuration (in RACH-ConfigCommon). The two relevant parameters here are: #SSBs-per-PRACH-occasion: 1 / 8, 1 / 4, 1 / 2, 1, 2, 8, or 16, which indicates the number of SSBs per RACH opportunity; and #CB-preambles-per-SSB preambles to each SS block: how many preambles are allocated within a RACH opportunity;
[0060] Given as Fig.10 In the first example shown, if the number of SSBs per RACH opportunity is 1, and if the UE is under the coverage of a particular SSB (e.g., SSB index 2), there will be a RACH opportunity for that SSB index 2. If the UE moves and is now under the coverage of another particular SSB (e.g., SSB index 5), there will be another RACH opportunity for that SSB index 5, i.e., each SSB detected by a given UE will have its own RACH opportunity. Therefore, on the network side, when a preamble is detected at a particular RACH opportunity, the network knows exactly which SSB the UE has selected and therefore which downlink beam is covering the UE, so that the network can continue with downlink transmissions, such as RAR, etc. This factor of 1 is an indication that each SSB has its own RACH resource, i.e., the preamble detected therein indicates to the network which SSB the UE has selected, i.e., which DL (downlink) beam (e.g., the DL beam that sent the RAR) the network should use to communicate with the UE.
[0061] It should be noted that each SS block is usually mapped to multiple preambles (different cyclic shifts and Zadoff-Chu roots) within the PRACH opportunity, so that multiple different UEs can exist in the same RACH opportunity because they can be covered by the same SSB. Fig.11 In the second example shown, the number of SSBs per RACH opportunity is 2. Therefore, the preamble received in this RACH opportunity indicates to the network that one of the two beams is being selected by the UE. Therefore, the network should have means to distinguish between the two beams by implementation, and / or should perform beam scanning in the downlink by sending RARs in both beams (either synchronously or sending in one beam, waiting for a response from the UE, and sending in the other beam if there is no response).
[0062] Now assume that in the first attempt the UE has selected an SSB (based on measurements performed in that cell), has sent the selected preamble associated with the PRACH resource mapped to the selected SSB at the initial power, and has not received the RAR within the RAR time window. According to the specification, the UE can still perform preamble retransmissions (i.e. the maximum number of allowed transmissions has not been reached).
[0063] The differences in contention resolution between NR and LTE are discussed below.
[0064] As discussed above with respect to contention-based random access in LTE, in LTE, collisions may occur in a cell because multiple UEs have selected the same RACH preamble and therefore may have transmitted in the same time / frequency PRACH resource transmission. In NR, collisions may occur when multiple UEs select the same preamble associated with a beam (i.e., the UEs may have to select the same SSB and CSI-RS), otherwise the time / frequency RACH resources will be different because there may be a different mapping between beams and RACH resources.
[0065] The contention resolution process in NR is very similar to that in LTE, as described in section 5.1.5 of reference [2]. If multiple UEs covered by the same downlink beam select the same preamble, they will also monitor the PDCCH (Physical Downlink Control Channel) using the same RA-RNTI and receive the same RAR content, including the same UL grant for the MSG.3 transmission (especially such as timing advance, etc.). If both are transmitted and if the network is able to decode at least one of them, there is contention resolution (MSG.4), so the UE knows that the contention has been resolved. As in LTE, this MSG.4 uses the C-RNTI (if one is assigned by the target, such as in the case of handover or when the UE is in RRC_CONNECTED) or TC-RNTI (Temporary C-RNTI) to address the UE in the case where this is an incoming UE (e.g. from a state transition). In addition, as in LTE, if the network addresses the UE with the TC-RNTI, it also includes the UE identity used in MSG.3 in the MAC payload, such as the recovery identifier.
[0066] Then, thanks to this mechanism, a UE detecting this contention resolution message is able to detect whether a collision has occurred and whether it needs to restart the RACH again. This is done by analyzing the contention of the message or after expiration of the contention resolution timer.
[0067] If the content of MSG.4 has the UE's TC-RNTI (Temporary Cell Radio Network Temporary Identifier) assigned in MSG.2, and the contention resolution flag in the payload matches the one it sent in MSG.3, then the UE considers the contention resolved and is not even aware that there was any conflict. If it has its TC-RNTI and the contention resolution flag in the payload does not match the one it sent in MSG.3, then the UE declares a conflict and performs further actions, such as declaring a RACH failure or performing another RACH attempt.
[0068] In summary, contention may not be resolved and a conflict may be detected in the following two cases: MSG.4 addressing the TC-RNTI and the UE identity do not match; and the contention resolution timer expires.
[0069] If we draw an analogy with existing LTE solutions for RACH optimization, the UE will log the occurrence of this event in these cases.
[0070] The following shows contention resolution in NR as described in the MAC specification (3GPP TS 38.321 V15.7.0 (2019-09)), also referred to as reference [3].
[0071] Assuming that in the first attempt the UE has selected an SSB (based on measurements performed in that cell), it has sent the selected preamble associated with the PRACH resource mapped to the selected SSB at the initial power, and it has not received the RAR within the RAR time window. According to the specification, the UE may still perform preamble retransmissions (i.e. the maximum number of allowed transmissions has not been reached).
[0072] As in LTE, at each preamble retransmission attempt, the UE can adopt the same SSB as the previous attempt and perform a power ramp similar to LTE. The maximum number of attempts is also defined in NR and it is also controlled by the parameter PREAMBLE_TRANSMISSION_COUNTER.
[0073] On the other hand, unlike LTE, at each preamble retransmission attempt the UE may instead select a different SSB, as long as the new SSB has acceptable quality (i.e. its measurements are above a configurable threshold). In that case, when selecting a new SSB (or more generally a new beam), the UE does not perform a power ramp-up, but instead transmits the preamble at the same previously transmitted power (i.e. the UE should not reinitialize the power to the initial power transmission). This is explained in Fig. 12A , Fig. 12B and Fig. 12C Shown in.
[0074] like Fig. 12A As shown, at time t0, the UE uses the preamble power P0 to select SSB63 and does not receive the RAR. Fig. 12B As shown, at time t1, the UE selects SSB63 again using the preamble power P1 equal to P0 plus the offset, and does not receive the RAR. Fig. 12C As shown, at time t2, the UE selects SSB64 using a preamble power P1 equal to P0 plus an offset, and receives the RAR.
[0075] To this end, a new variable called PREAMBLE_POWER_RAMPING_COUNTER is defined in the NR MAC specification (reference [3]) when the same beam is selected for retransmission. At the same time, the previous LTE variable still exists (PREAMBLE_TRANSMISSION_COUNTER), so that the total number of attempts is still limited, regardless of whether the UE performs SSB / beam reselection or power ramping on each attempt.
[0076] Therefore, if the initial preamble transmission (e.g. associated with SSB-2) is not successful and the UE selects the same SSB / beam, the PREAMBLE_POWER_RAMPING_COUNTER is incremented (i.e. set to 2 in the second attempt) and the transmission power will be:
[0077] PREAMBLE_RECEIVED_TARGET_POWER=preambleReceivedTargetPower+DELTA_PREAMBLE+1*PREAMBLE_POWER_RAMPING_STEP;
[0078] Otherwise, if the UE selects a different SSB / beam instead, the PREAMBLE_POWER_RAMPING_COUNTER is not incremented (i.e. remains at 1) and the transmit power will be the same as in the first transmission:
[0079] PREAMBLE_RECEIVED_TARGET_POWER=preambleReceivedTargetPower+DELTA_PREAMBLE;
[0080] The preamble power ramping process in the case of multiple preamble transmission attempts is further described in the NRMAC specification (reference [3]). Random access procedure initialization is discussed in Section 5.1.1 of reference [3], random access resource selection is discussed in Section 5.1.2 of reference [3], random access preamble transmission is discussed in Section 5.1.3 of reference [3], and random access response reception is discussed in Section 5.1.4 of reference [3].
[0081] In LTE, the UE may be configured to perform CFRA, for example during handover. This configuration goes into the mobilityControlInfo field of the MobilityControlInfo IE, as shown in Table 2 for the MobilityControlInfo information element.
[0082] Table 2
[0083]
[0084] And, RACH-ConfigDedicated is defined, as shown in Table 3 for the RACH-ConfigDedicated information element.
[0085] Table 3
[0086]
[0087]
[0088] If the rach-ConfigDedicated field is not present, the UE applies contention-based random access as specified in TS 36.321 (also referred to as reference [2]). Otherwise, the UE performs CFRA as discussed below in conjunction with Sections 5.1.2, 5.1.3, and 5.1.4 of reference [2]. Section 5.1.2 of reference [2] discusses random access resource selection, Section 5.1.3 of reference [2] discusses random access preamble transmission, and Section 5.1.4 of reference [2] discusses random access response reception.
[0089] When the UE receives the CFRA configuration, it performs a preamble transmission and if the RAR is not received within the RAR time window, the UE is allowed to perform power ramp up and preamble retransmission by selecting the same configured dedicated preamble. Note that from the MAC perspective, this is valid until the UE reaches the maximum number of RACH attempts, where if this occurs, a failure is declared. For example, from the RRC perspective, if a dedicated RACH configuration is provided in the Mobility Control Info during handover, the UE is allowed to do so until the failure timer T304 runs (which is started when the UE receives a handover command (i.e., RRC connection reconfiguration)). This is discussed in sections 5.3.5.4 and 5.3.5.6 of TS 36.331 (reference [1]). UE's reception of RRCConnectionReconfiguration (handover) including mobilityControlInfo is discussed in Section 5.3.5.4 of reference [1], while T304 expiration (handover failure) is discussed in Section 5.3.5.6 of reference [1].
[0090] In NR, as in LTE, the UE can be configured to perform CFRA, for example during handover. This configuration goes into the IEReconfigurationWithSync (which goes into the CellGroupConfig IE sent in the RRCReconfiguration message), as shown in Table 4
[0091] Table 4
[0092]
[0093] The RACH-ConfigDedicated information element is shown in Table 5.
[0094] Table 5
[0095]
[0096]
[0097]
[0098] The first difference between NR and LTE shown above (also combined with Fig. 9A and Fig. 9B ) is that RACH resources may be mapped to beams (e.g., SSB or CSI-RS resources that may be measured by a UE). Therefore, when CFRA resources are provided, they are also mapped to beams, and this may be done only for a subset of beams in a given target cell.
[0099] The consequence of this is that in order to use CFRA resources, the UE needs to select a beam for which it has CFRA resources configured in the dedicated configuration. For example, in the case of SSB, it can be found in the ssb-ResourceList, which is a SEQUENCE(SIZE(1..maxRA-SSB-Resources)) of CFRA-SSB-Resource.
[0100] If we draw an analogy with LTE (i.e. if the NR solution is the same as LTE), when a beam with CFRA resources (e.g., a beam from the configured list) is selected and RAR is not received, the UE will continue to select the same resources and ramp up the power before retransmitting the preamble. However, as in the case of NR CBRA, the UE can select another beam every time the attempt fails. And, this other beam may or may not be in the list of beams for CFRA. In the case where the selected beam is not, the UE performs CBRA.
[0101] It is also important to note that in case CFRA is provided for CSI-RS resources, there is a fallback between CSI-RS selection to SSB selection.
[0102] This is reflected in section 5.1.2 of the NR MAC specification 3GPP TS 38.321 (reference [3]).
[0103] As part of the RAN2107#45 email discussion, several details of RACH reporting were discussed. One of the details was related to when the UE should trigger a RACH report and the company's response and the conclusion of the email discussion investigator is given below.
[0104] The email discussion included questions 1-7: Which RACH scenarios should apply to RACH reporting?
[0105] Based on responses from various companies, the email discussion investigators made the following recommendations:
[0106] Recommendation 1-8: At least the following RACH scenarios apply to RACH reporting:
[0107] - Initial access starting from RRC_IDLE;
[0108] -RRC connection reestablishment process;
[0109] - Switch;
[0110] - Requests made via RRC during synchronous reconfiguration;
[0111] - Transition from RRC_INACTIVE;
[0112] FFS (For further study / future study): Whether the RACH scenarios of "beam failure recovery" and "request for additional SI" are also applicable to RACH reporting is for further study (FFS).
[0113] The email discussion also included questions 1-8: Does the company think it should be made clear that a successful RACH report triggered by RACH scenario A can be covered by another successful RACH report triggered by RACH scenario B?
[0114] Ericsson's response is "yes" and further explains the benefit of having a RACH report list that includes all (up to a maximum number) RACH attempts related to which the network has not yet been informed of the availability of RACH reports. For example, a UE performing three BFR procedures can include the RACH information related to these three BFRs in a single RACH report and inform the RRC when sending the next RRCReconfigurationComplete or RRCReestablishmentComplete or RRCResumeComplete or RRCSetupComplete message.
[0115] Based on the responses from various companies, the email discussion investigators came to the following conclusions and recommendations:
[0116] For questions 1-8, based on company feedback, the following conclusions were drawn: 5 companies (Ericsson / Huawei / CMCC / Nokia / CATT) believed that the RACH report list was acceptable; 1 company believed that it depended on the results of recommendations 1-8.
[0117] Recommendation 1-9: Whether a RACH report list is required may depend on the outcome of Recommendation 1-8.
[0118] Although there are known RACH reporting methods, there is still a need for methods that can improve efficiency. Summary of the invention
[0119] According to some embodiments of the present inventive concept, a method for operating a wireless device that provides communications with a wireless network is provided. The wireless device registers with a first public land mobile network (PLMN) having a first PLMN identity. A first plurality of random access (RA) procedures are performed when registering with the first PLMN. First information is stored in a memory, wherein the first information is related to the first plurality of RA procedures, and the first plurality of RA procedures are associated with the first PLMN having the first PLMN identity. After registering with the first PLMN and after performing the first plurality of RA procedures, the wireless device registers with a second PLMN having a second PLMN identity different from the first PLMN identity. In response to registering with the second PLMN, the first information is discarded from the memory. A second plurality of RA procedures are performed when registering with the second PLMN. Second information is stored in the memory, wherein the second information is related to the second plurality of RA procedures, and the second plurality of RA procedures are associated with the second PLMN having the second PLMN identity. An information message is sent to the second PLMN, wherein the information message includes a plurality of RACH reports, and the plurality of RACH reports correspond to the second plurality of RA procedures associated with the second PLMN identity based on the second information.
[0120] According to some other embodiments of the present invention, a wireless device includes a processing circuit and a memory coupled to the processing circuit. The memory includes instructions that, when executed by the processing circuit, cause the wireless device to: register with a first public land mobile network (PLMN) having a first PLMN identity; perform a first plurality of random access (RA) procedures when registering with the first PLMN; store first information in the memory, the first information being related to the first plurality of RA procedures, the first plurality of RA procedures being associated with the first PLMN having the first PLMN identity; register with a second PLMN having a second PLMN identity different from the first PLMN identity after registering with the first PLMN and after performing the first plurality of RA procedures; discard the first information from the memory in response to registering with the second PLMN; perform a second plurality of RA procedures when registering with the second PLMN; store second information in the memory, the second information being related to the second plurality of RA procedures, the second plurality of RA procedures being associated with the second PLMN having the second PLMN identity; and send an information message to the second PLMN, wherein the information message includes a plurality of RACH reports corresponding to the second plurality of RA procedures associated with the second PLMN identity based on the second information.
[0121] According to other embodiments of the present invention, a wireless device is adapted to: register with a first public land mobile network (PLMN) having a first PLMN identifier; perform a first plurality of random access (RA) procedures when registering with the first PLMN; store first information in a memory, the first information being related to the first plurality of RA procedures, the first plurality of RA procedures being associated with the first PLMN having the first PLMN identifier; register with a second PLMN having a second PLMN identifier different from the first PLMN identifier after registering with the first PLMN and after performing the first plurality of RA procedures; discard the first information from the memory in response to registering with the second PLMN; perform a second plurality of RA procedures when registering with the second PLMN; store second information in the memory, the second information being related to the second plurality of RA procedures, the second plurality of RA procedures being associated with the second PLMN having the second PLMN identifier; and send an information message to the second PLMN, wherein the information message includes a plurality of RACH reports, the plurality of RACH reports corresponding to the second plurality of RA procedures associated with the second PLMN identifier based on the second information.
[0122] According to some embodiments of the present inventive concept, the efficiency of RACH reporting and / or radio resource utilization can be improved by providing a RACH report related to the PLMN to which the wireless device is currently registered (without providing a RACH report of the previous PLMN). In addition, according to some embodiments, the efficiency of memory utilization can be improved by discarding information about RA procedures associated with the previous PLMN from the wireless device memory. BRIEF DESCRIPTION OF THE DRAWINGS
[0123] The accompanying drawings, which are included to provide a further understanding of the present disclosure and are incorporated in and constitute a part of this application, illustrate certain non-limiting embodiments of the inventive concept. In the drawings:
[0124] Figure 1 is a block diagram illustrating a wireless device UE according to some embodiments of the inventive concept;
[0125] Figure 2 is a block diagram illustrating a radio access network RAN node (e.g., a base station eNB / gNB) according to some embodiments of the inventive concept;
[0126] Figure 3 is a block diagram illustrating a core network CN node (eg, AMF node, SMF node, etc.) according to some embodiments of the inventive concept;
[0127] Figure 4 is a message diagram illustrating a UE information procedure;
[0128] Figure 5 is a message diagram illustrating contention-based random access CBRA;
[0129] Figure 6 is a diagram of the layer 1 perspective of the preamble sent in the so-called physical random access channel;
[0130] Figure 7 Is from Figure 5 Figure 2 shows the elements of a medium access control random access response of operation 2;
[0131] Figure 8 is a message diagram illustrating a preamble collision;
[0132] Fig. 9A is a diagram illustrating that a cell in NR transmits in 1 downlink beam;
[0133] Fig. 9B is a diagram illustrating that a cell in NR transmits in multiple downlink beams;
[0134] Fig.10 and Fig.11 is a diagram illustrating a synchronization signal block and a RACH opportunity;
[0135] Fig. 12A , Fig. 12B and Fig. 12C is a diagram illustrating that a cell in NR transmits to a UE in multiple downlink beams;
[0136] Fig.13 is a diagram of a RACH reporting indication according to some embodiments of the present inventive concept;
[0137] Fig.14 is a diagram of an access and mobility indication procedure according to some embodiments of the inventive concept;
[0138] Fig.15 and Fig.16 is a flow chart illustrating the operation of a wireless device according to some embodiments of the present inventive concept;
[0139] Fig.17 is a block diagram of a wireless network according to some embodiments;
[0140] Fig.18 is a block diagram of a user equipment according to some embodiments;
[0141] Fig.19 is a block diagram of a virtualization environment according to some embodiments;
[0142] Fig. 20 is a block diagram of a telecommunications network connected to a host computer via an intermediate network according to some embodiments;
[0143] Fig.21 is a block diagram of a host computer communicating with a user device via a base station over a partially wireless connection according to some embodiments;
[0144] Fig. 22 is a block diagram of a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments;
[0145] Fig.23 is a block diagram of a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments;
[0146] Fig.24 is a block diagram of a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments; and
[0147] Fig.25 is a block diagram of a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments. DETAILED DESCRIPTION
[0148] The inventive concept will now be described more fully below with reference to the accompanying drawings, in which examples of embodiments of the inventive concept are shown. However, the inventive concept can be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein. On the contrary, these embodiments are provided to make the disclosure thorough and complete and to fully convey the scope of the inventive concept to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. It may be assumed by default that a component from one embodiment exists / is used in another embodiment.
[0149] The following description presents various embodiments of the disclosed subject matter. These embodiments are presented as teaching examples and should not be interpreted as limiting the scope of the disclosed subject matter. For example, some details of the described embodiments may be modified, omitted or expanded without departing from the scope of the described subject matter.
[0150] Figure 1 1 is a block diagram illustrating elements of a wireless device UE 300 (also referred to as a mobile terminal, mobile communication terminal, wireless communication device, wireless terminal, mobile device, wireless communication terminal, user equipment, UE, user equipment node / terminal / device, etc.) configured to provide wireless communication according to an embodiment of the present inventive concept. (The wireless device 300 may be provided, for example, as described below in conjunction with Fig.17 As shown in the figure, the wireless device UE may include an antenna 307 (eg, corresponding to Fig.17 antenna QQ111) and transceiver circuit 301 (also referred to as a transceiver, for example, corresponding to Fig.17 The transceiver circuit 301 includes an interface QQ114 configured to provide communication with a base station (eg, corresponding to Fig.17 The wireless device UE may also include a processing circuit 303 (also referred to as a processor, for example, corresponding to a processor) coupled to the transceiver circuit. Fig.17 Processing circuit QQ120) and memory circuit 305 (also referred to as memory, for example, corresponding to Fig.17 The memory circuit 305 may include a computer readable program code that, when executed by the processing circuit 303, causes the processing circuit to perform operations according to the embodiments disclosed herein. According to other embodiments, the processing circuit 303 may be defined to include a memory, so that a separate memory circuit is not required. The wireless device UE may also include an interface (e.g., a user interface) coupled to the processing circuit 303, and / or the wireless device UE may be incorporated into a vehicle.
[0151] As discussed herein, operations of the wireless device UE may be performed by the processing circuit 303 and / or the transceiver circuit 301. For example, the processing circuit 303 may control the transceiver circuit 301 to send communications to a radio access network node (also referred to as a base station) over a radio interface through the transceiver circuit 301 and / or to receive communications from a RAN node over a radio interface through the transceiver circuit 301. In addition, modules may be stored in the memory circuit 305, and these modules may provide instructions such that when the instructions of the modules are executed by the processing circuit 303, the processing circuit 303 performs corresponding operations (e.g., the operations discussed below in conjunction with example embodiments related to wireless devices).
[0152] Figure 2 4 is a block diagram illustrating elements of a radio access network (RAN) node 400 (also referred to as a network node, base station, eNodeB / eNB, gNodeB / gNB, etc.) configured to provide cellular communications according to an embodiment of the inventive concept. (The RAN node 400 may be provided, for example, as described below in conjunction with Fig.17 As shown in the figure, the RAN node may include a transceiver circuit 401 (also referred to as a transceiver, for example, corresponding to Fig.17 The RAN node may include a network interface circuit 407 (also referred to as a network interface, e.g., corresponding to a network interface circuit 407). Fig.17 The network node may also include a processing circuit 403 (also referred to as a processor, for example, corresponding to the processing circuit QQ170) coupled to the transceiver circuit and a memory circuit 405 (also referred to as a memory, for example, corresponding to the memory) coupled to the processing circuit. Fig.17 Device-readable medium Q180). Memory circuit 405 may include computer-readable program code that, when executed by processing circuit 403, causes the processing circuit to perform operations according to the embodiments disclosed herein. According to other embodiments, processing circuit 403 may be defined to include memory, thereby eliminating the need for a separate memory circuit.
[0153] As discussed herein, the operations of the RAN node may be performed by the processing circuit 403, the network interface 407, and / or the transceiver 401. For example, the processing circuit 403 may control the transceiver 401 to send communications to one or more mobile terminals UE via the transceiver 401 over a radio interface and / or to receive communications from one or more mobile terminals UE via the transceiver 401 over a radio interface. Similarly, the processing circuit 403 may control the network interface 407 to send communications to one or more other network nodes via the network interface 407 and / or to receive communications from one or more other network nodes via the network interface. In addition, modules may be stored in the memory 405, and these modules may provide instructions such that when the instructions of the modules are executed by the processing circuit 403, the processing circuit 403 performs corresponding operations (e.g., the operations discussed below in conjunction with the example embodiments related to the RAN node).
[0154] According to some other embodiments, the network node may be implemented as a core network CN node without a transceiver. In such an embodiment, the transmission to the wireless device UE may be initiated by the network node, thereby providing the transmission to the wireless device through the network node including the transceiver (e.g., through a base station or RAN node). According to an embodiment in which the network node is a RAN node including a transceiver, initiating the transmission may include sending through the transceiver.
[0155] Figure 3 is a block diagram showing elements of a core network (CN) node (e.g., SMF node, AMF node, etc.) of a communication network configured to provide cellular communications according to an embodiment of the present invention. As shown, the CN node may include a network interface circuit 507 (also referred to as a network interface) configured to provide communications with other nodes of a core network and / or a radio access network RAN. The CN node may also include a processing circuit 503 (also referred to as a processor) coupled to the network interface circuit and a memory circuit 505 (also referred to as a memory) coupled to the processing circuit. The memory circuit 505 may include a computer-readable program code that, when executed by the processing circuit 503, causes the processing circuit to perform operations according to the embodiments disclosed herein. According to other embodiments, the processing circuit 503 may be defined as including a memory, thereby eliminating the need for a separate memory circuit.
[0156] As discussed herein, operations of the CN node may be performed by the processing circuitry 503 and / or the network interface circuitry 507. For example, the processing circuitry 503 may control the network interface circuitry 507 to send communications to one or more other network nodes through the network interface circuitry 507 and / or to receive communications from one or more other network nodes through the network interface circuitry 507. In addition, modules may be stored in the memory 505, and these modules may provide instructions such that when the instructions of the modules are executed by the processing circuitry 503, the processing circuitry 503 performs corresponding operations (e.g., the operations discussed below in conjunction with the example embodiments related to the core network node).
[0157] In the existing protocol, the company has mentioned that a RACH report list can be sent from the UE. This is to enable the UE to inform the network of the RACH reports for all possible RACH accesses for the CU-CP. In the existing method, the CU is not aware of the RACH access associated with some RACH procedures related to the serving cell (such as beam failure recovery).
[0158] There are two open questions associated with this. The first question is whether a RACH report associated with one cell can be sent to another cell? The second question is how does the CU-CP learn about RACH accesses that were invisible to it so far?
[0159] According to some embodiments of the present inventive concept, three independent methods are proposed.
[0160] Method 1: Based on a message including a RACH report list, which contains information about multiple RACH procedures performed by the UE.
[0161] Method 2: Based on explicit indication from the UE to the RRC regarding the availability of RACH reporting after each UE performs a RACH procedure.
[0162] Method 2a: Based on explicit signaling from the UE's MAC entity to the UE's RRC layer, which indicates the beam index and the timestamp when the UE performs RACH on the selected beam.
[0163] Method 3: Based on the gNB-DU (gNB Distributed Unit) sending an explicit indication to the CU-CP (Central Unit Control Plane) about the successful random access procedure performed by the UE so that the CU-CP can request the UE to send the associated RACH report.
[0164] Based on the method proposed in the embodiment of the present disclosure, since more RACH reports can be collected from the UE, the network can understand the problems related to RACH more quickly.
[0165] The advantage of method 1 is that each RRC message carrying a RACH report can carry multiple RACH reports, which is more efficient than each RRC message carrying a single RACH report. This method also reduces the communication overhead between the gNB-DU and the CU-CP.
[0166] The advantage of method 2 is that this method also reduces the communication overhead between the gNB-DU and the CU-CP. This method also ensures that the UE does not need to increase its memory reservation for RACH reporting, because in this method, the UE is expected to retain only information related to its most recent random access procedure.
[0167] Method 2a allows the RRC layer to collect Layer 3 measurements of the beam that the MAC entity has used to perform the RACH attempt.
[0168] Method 3 ensures that the UE does not need to increase its memory reservation for RACH reporting, since in this method the UE is expected to retain only information related to its most recent random access procedure.
[0169] Specific embodiments of Method 1 are discussed below.
[0170] In this method, the UE stores information related to multiple random access procedures in a RACH report list and provides the RACH report list to the network using RRC communication with the network.
[0171] In one embodiment of the present invention, the UE is allowed to store only random access related information for a specific cell, the UE only indicates the availability of such a report to the cell, that is, a RACH report like this does not contain a cell ID (identifier), and if the UE does not have any communication with the RRC (by using which the availability of such a RACH report can be informed), the UE refreshes this information. An example of this RACH report can be provided, as shown in the ASN.1 code given in Table 6.
[0172] Table 6
[0173]
[0174] To ensure that the serving cell has the best chance of extracting this information from the UE (and avoid refreshing such information during handover), the UE may indicate the presence of an existing RACH report in an additional RRC message such as MeasurementReport (a flag that informs the RRC that RACH reports are available). The MeasurementReport message is illustrated in Table 7.
[0175] Table 7
[0176]
[0177] In another embodiment of the invention, the UE stores the cell ID associated with each random access procedure, since the RACH report relating to the performed random access procedure can be sent to any cell for which the UE performs RRC communications. Table 8 gives an example of what the RACH report represents in ASN.1 code.
[0178] Table 8
[0179]
[0180] By storing the cell ID associated with the random access procedure performed, the UE can aggregate RACH reports related to operations in different cells and include all aggregated RACH reports for different cells in a RACH report list, which is included in a message sent to the network to allow the receiving network node to identify which cells and related network nodes each RACH report involves, and distribute the information in each RACH report to the related network node. This embodiment allows the UE to continue to aggregate RACH reports when performing a handover to a new cell. This embodiment also allows a single RRC message to include RACH reports related to operations in different cells, thereby reducing communication overhead.
[0181] In some sub-embodiments, the UE includes only the local ID or the global ID of the cell, while in some other sub-embodiments, the UE includes both. A cell receiving a RACH report from a UE understands that the report contains RACH information related to other cells (via the local cell ID and / or the global cell ID), and then it forwards these contents of the RACH report to the corresponding cell via the X2 / Xn interface.
[0182] The specification 3GPP TS 38.423 describing the RACH report signaling through the Xn interface may be updated according to this embodiment, for example, as follows:
[0183] The purpose of the RACH indication procedure is to transfer information between NG-RAN nodes related to a RACH performed on a cell belonging to a NG-RAN node indicated in a RACH report requested from a UE. Signalling occurs from the NG-RAN node at which the RACH report is received to the NG-RAN node for which the UE in question may have previously performed a RACH on a cell belonging to that NG-RAN node. This may help detect problems with the RACH procedure and improve the performance of the RACH procedure.
[0184] This process uses non-UE related signaling, such as Fig.13 As shown, this figure illustrates the RACH reporting indication, successful operation.
[0185] When NG-RAN node 2 considers that the UE may have previously performed RACH at a cell controlled by NG-RAN node 1, NG-RAN node 2 sends a RACH INDICATION message to NG-RAN node 1 after receiving a RACH report from the UE at NG-RAN node 2, thereby initiating the procedure.
[0186] Embodiments related to PLMN (Public Land Mobile Network) identification are discussed below.
[0187] In yet another embodiment, the UE includes the PLMN-identity next to the cell ID when collecting RACH reports. Thus, when the registered PLMN is equal to the PLMN-identity recorded by the UE when performing RACH, the UE will be able to report RACH related information to the network. In yet another embodiment, the UE may create a RACH report list for each PLMN identity so that when the UE moves to an area with a different PLMN identity, it creates a new RACH report list associated with the new PLMN identity.
[0188] In yet another embodiment, when the UE is reporting the availability of a RACH report, it checks whether the PLMN registered in the serving cell is the same as the PLMN identity recorded as part of the RACH report (or recorded alongside the RACH report as part of a VarRACHReport).
[0189] RACH reporting may be performed when the UE moves between cells with different PLMN identities.
[0190] When a UE moves between cells with different PLMNs (while logging RACH reports in the RACH report list), the UE can take the following actions:
[0191] In some embodiments, when the UE enters a cell with a different PLMN identity, the UE may discard the collected RACH reports related to RACH procedures performed on the cell with the first PLMN, and only collect RACH reports related to RACH procedures performed on the cell with the second PLMN identity.
[0192] In other embodiments, the UE may retain the RACH report list associated with the first PLMN identity and create a new RACH report list for the RACH procedure performed on the cell belonging to the second PLMN identity.
[0193] In yet other embodiments, the UE may retain RACH reports associated with the first PLMN and avoid logging RACH reports related to RACH procedures performed on a cell with a second PLMN. In other words, the UE may choose to log RACH reports based on a preferred / prioritized PLMN identity.
[0194] The following discusses reporting the RACH reporting list when the UE moves between cells with different PLMN identities.
[0195] If the UE maintains a RACH report list related to RACH procedures performed on the cell associated with the first PLMN identity, it may perform one of the following actions to report the RACH report list as requested by the network:
[0196] • In some embodiments, as requested by the network, the UE reports only RACH reports associated with cells having a PLMN identity equal to the RPLMN of the current serving cell and discards the remaining recorded RACH reports associated with other PLMNs in VarRACHReport.
[0197] • In other embodiments, at the request of the network, the UE reports the RACH reports associated with the cell having the PLMN identity equal to the RPLMN of the current serving cell, and keeps the remaining logged RACH reports in the VarRACHReport associated with other PLMNs.
[0198] In yet other embodiments, upon request of the network, the UE sends RACH reports belonging to all PLMNs.
[0199] Specific embodiments of Method 2 are discussed below.
[0200] In this method, each time the UE successfully completes the random access procedure, the RRC layer of the UE sends an indication to the RRC layer of the RAN node. An example of such a report may be provided as a UEInformationAvailable message, as shown in Table 9.
[0201] Table 9
[0202]
[0203]
[0204] Specific embodiments of method 2a are discussed below.
[0205] In this method, the MAC entity of the UE signals the RRC layer of the UE the selected beam index in which the RACH attempt has been performed.
[0206] In yet other embodiments of the same method, the MAC entity of the UE may signal a timestamp associated with the time at which the UE has performed RACH on the selected beam.
[0207] When the UE's MAC entity performs a RACH, the RRC layer is not aware of this. Therefore, by providing the RRC layer with the selected beam index for the RACH attempt and the timestamp of the RACH attempt (i.e., the absolute or relative time when the UE performed the RACH attempt), this allows the RRC layer to collect measurement values corresponding to the downlink beam quality of the selected beam when the UE performs the measurement.
[0208] In yet other embodiments, the RRC layer at the UE may collect measurements (of the reported beam) performed just after or before the reported timestamp.
[0209] In yet other embodiments, the RRC layer may collect the latest available L3 filtered measurements regardless of the timestamp of the attempted RACH reported by the MAC entity.
[0210] Specific embodiments of Method 3 are discussed below.
[0211] In this method, the F1-C interface is enhanced by a message from the gNB-DU to the CU-CP indicating that the UE has successfully completed the random access procedure. This in turn can trigger the collection of RACH reports from the CU-CP.
[0212] In yet other embodiments, the gNB-DU may signal the gNB-CU with respect to the beam index on which the UE has successfully performed RACH.
[0213] The forwarding of RACH reports over the Xn and F1 interfaces is discussed below.
[0214] In the present method, when a RACH report (which, in the present disclosure, includes multiple RACH reports associated with a cell using a cell ID) is reported to the network, the RAN node receiving the RACH report may forward the RACH report to the RAN node to which the cell with the cell ID in the RACH report belongs.
[0215] In a further embodiment, the RACH report (which is forwarded to a RAN node that owns the cell indicated in the cell ID that is part of the RACH report) will be forwarded from the CU to a DU of the same RAN node that owns the cell indicated by the cell ID in the RACH report (e.g., in a 5G network, over the F1 interface, from the CU to the corresponding DU that owns the cell in which the RACH was performed).
[0216] An example of text that may be applied to 3GPP TS 38.473 (FI interface specification in NG-RAN nodes) embodying embodiments regarding forwarding RACH reports over the F1 interface is discussed below. This text may be included as Section 8.2.x, Section 8.2.x.1, Section 8.2.x2, Figure 8 .2.x2.-1 (as Fig.14 Provided) and Section 9.2.1.x is added to 3GPP TS38.473.
[0217] 8.2.x Access and Mobility Indication
[0218] 8.2.x.1 Overview
[0219] The Access and Mobility Indication procedure is initiated by the gNB-CU to report to the gNB-DU information about the access and mobility functions and the configuration managed by the gNB-DU.
[0220] 8.2.x.2 Successful Operation
[0221] Figure 8 .2.x.2-1: Failure indication procedure. Successful operation (as Fig.14 supply)
[0222] The access and mobility indication procedure is initiated by the ACCESS AND MOBILITY INDICATION message sent from the gNB-CU.
[0223] If the ACCESS AND MOBILITY INDICATION message contains the RLF REPORT CONTAINER IE and / or if the ACCESS AND MOBILITY INDICATION message contains the RACH REPORT CONTAINER IE, the gNB-DU shall take into account possible optimization of the mobility and RACH access procedure. With the help of the ACCESS AND MOBILITY INDICATION message containing the RACH REPORT CONTAINER IE, the gNB-DU may receive information about the RACH access procedure performed for the cell served by the gNB-DU and, therefore, it may use such information to, for example, optimize the RACH configuration or optimize the beam configuration for best coverage and UE access.
[0224] 9.2.1.x Access and Mobility Indication
[0225] This message is sent by the gNB-CU and is used to indicate information related to the access and mobility functions and the configuration managed by the gNB-DU.
[0226] Direction: gNB-CU → gNB-DU
[0227] Table 10
[0228]
[0229] The message structure in Table 10 shows that a single procedure over the F1 interface can be used to forward mobility and access information, such as RACH reports and RLF reports, from the gNB-CU-CP to the gNB-DU.
[0230] Reference will now be made to some embodiments of the present invention. Fig.15 The operation of the wireless device 300 is discussed in detail with reference to the flowchart of Figure 1 For example, the modules can be stored in Figure 1 The memory 305 of the module can provide instructions so that when the instructions of the module are executed by the corresponding operation of the corresponding non-flowchart.
[0231] At block 1501 , the processing circuit 303 may register with a first PLMN having a first PLMN identity.
[0232] At block 1505 , the processing circuit 303 may perform a first plurality of RA procedures when registering with the first PLMN (eg, for each RA procedure, send one or more RA preambles via the transceiver 301 ).
[0233] At block 1509 , the processing circuit 303 may store first information in the memory 305 , the first information being related to the first plurality of random access, RA procedures, the first plurality of RA procedures being associated with a first PLMN having a first public land mobile network, PLMN identity.
[0234] At block 1511 , the processing circuit 303 may register with a second PLMN having a second PLMN identity after registering with the first PLMN and after performing the first plurality of RA procedures.
[0235] At block 1513 , the processing circuit 303 may discard the first information from the memory 305 in response to registering with the second PLMN.
[0236] At block 1515 , the processing circuit 303 may perform a second plurality of RA procedures when registering with the second PLMN (eg, for each RA procedure, send one or more RA preambles via the transceiver 301 ).
[0237] At block 1519 , the processing circuit 303 may store second information in the memory 305 , the second information relating to the second plurality of RA procedures associated with a second PLMN having a second PLMN identity different from the first PLMN identity.
[0238] At block 1521 , the processing circuit 303 may receive (via the transceiver 301 ) a RACH reporting request from the second PLMN after storing the first information and after storing the second information.
[0239] At block 1525, the processing circuit 303 may send (via the transceiver 301) an information message to at least one of the first PLMN and / or the second PLMN, wherein the information message includes a plurality of RACH reports corresponding to the first plurality of RA procedures associated with the first PLMN identity based on the first information and / or corresponding to the second plurality of RA procedures associated with the second PLMN identity based on the second information. For example, the information message may be sent to the second PLMN (at block 1521) in response to receiving a RACH report request from the second PLMN. According to some other embodiments, the RACH report request may be omitted. According to some embodiments in which the first information is discarded in response to registering with the second PLMN, the processing circuit 303 may send the information message only to the second PLMN at block 1525, the information message including a plurality of RACH reports corresponding to the second plurality of RA procedures associated with the second PLMN identity based on the second information.
[0240] According to some embodiments, the processing circuit 303 may send an information message to the second PLMN at block 1525 after performing the second plurality of RA procedures, wherein the information message includes a plurality of RACH reports corresponding to the second plurality of RA procedures associated with the second PLMN identity based on the second information. According to such embodiments, the information message may omit the RACH report corresponding to the first plurality of RA procedures associated with the first PLMN identity, and / or the processing circuit 303 may discard the first information from the memory 305 in response to registering with the second PLMN.
[0241] According to some embodiments, the information message of box 1525 may include a first plurality of RACH reports and a second plurality of RACH reports, wherein the first plurality of RACH reports correspond to the first plurality of RA processes associated with the first PLMN identifier based on the first information, and the second plurality of RACH reports correspond to the second plurality of RA processes associated with the second PLMN identifier based on the second information.
[0242] According to some embodiments, the information message of block 1525 may include a plurality of RACH reports corresponding to the second plurality of RA procedures associated with the second PLMN identity based on the second information, and it may omit the RACH reports corresponding to the first plurality of RA procedures associated with the first PLMN identity based on the first information. According to such embodiments, the processing circuit 303 may discard the first information related to the first plurality of RA procedures from the memory 305 in response to receiving the RACH report request from the second PLMN, or the processing circuit 303 may save the first information in the memory after sending the information message.
[0243] According to some embodiments, each of the plurality of RACH reports corresponding to the second plurality of RA procedures comprises a second PLMN identity. According to some embodiments, the first information comprises, for each RA procedure of the first plurality of RA procedures, an indication of a number of RACH preambles sent for the respective RA procedure, the second information comprises, for each RA procedure of the second plurality of RA procedures, an indication of a number of RACH preambles sent for the respective RA procedure, and each of the plurality of RACH reports comprises an indication of a number of RACH preambles sent for the second plurality of RA procedures. According to some embodiments, for each RA procedure of the first plurality of RA procedures, the first information comprises a contention detection flag indicating whether contention resolution is unsuccessful for at least one RACH preamble sent for the respective RA procedure, for each RA procedure of the second plurality of RA procedures, the second information comprises a contention detection flag indicating whether contention resolution is unsuccessful for at least one RACH preamble sent for the respective RA procedure, and each of the plurality of RACH reports comprises a contention detection flag for a respective one of the second plurality of RA procedures.
[0244] In conjunction with some embodiments of wireless devices and related methods, from Fig.15 Various operations of the flowchart may be optional. For example, with respect to the method of example embodiment 65 (described below), Fig.15 The operations of blocks 1501, 1505, 1511, 1513, 1515, and 1521 may be optional.
[0245] Reference will now be made to some embodiments of the present invention. Fig.16 The operation of the wireless device 300 is discussed in detail with reference to the flowchart of Figure 1 For example, the modules can be stored in Figure 1 The modules may be stored in the memory 305, and these modules may provide instructions, so that when the instructions of the modules are executed by the corresponding wireless device processing circuit 303, the processing circuit 303 performs the corresponding operations of the flowchart.
[0246] At block 1601 , the processing circuit 303 may register with a first public land mobile network (PLMN) having a first PLMN identity.
[0247] At block 1605 , the processing circuit 303 may perform a first plurality of random access (RA) procedures when registering with a first PLMN.
[0248] At block 1609 , the processing circuit 303 may store information related to the first plurality of RA procedures, the first plurality of RA procedures being associated with a first PLMN having a first PLMN identity.
[0249] At block 1610, the processing circuit 303 may send an information message to at least one of the first PLMN and / or the second PLMN, wherein the information message includes a plurality of RACH reports corresponding to the first plurality of RA procedures associated with the first PLMN identity based on the first information. According to some embodiments, the processing circuit 303 may send the information message to the first PLMN before registering with the second PLMN.
[0250] At block 1611 , the processing circuit 303 may register with a second PLMN having a second PLMN identity after registering with the first PLMN and after performing the first plurality of RA procedures, wherein the first PLMN identity and the second PLMN identity are different.
[0251] At block 1615 , the processing circuit 303 may perform a second plurality of RA procedures when registering with the second PLMN without storing information related to the second plurality of RA procedures.
[0252] In accordance with some embodiments, for each RA process in the first plurality of RA processes, the information may include an indication of a number of random access channel (RACH) preambles sent for the corresponding RA process, and each RACH report in the plurality of RACH reports may include an indication of a number of RACH preambles sent for a corresponding one of the first plurality of RA processes.
[0253] According to some embodiments, for each RA process in the first plurality of RA processes, the first information may include a contention detection flag indicating whether contention resolution was unsuccessful for at least one RACH preamble code sent for the corresponding RA process, and each RACH report in the plurality of RACH reports may include a contention detection flag for a corresponding one of the first plurality of RA processes.
[0254] In conjunction with some embodiments of wireless devices and related methods, from Fig.16Various operations of the flowchart may be optional. For example, with respect to the method of example embodiment 82 (described below), Fig.16 The operation of block 1610 may be optional.
[0255] Example embodiments are discussed below.
[0256] 1. A method of operating a wireless device that provides communications with a wireless network, the method comprising: storing information related to a plurality of random access (RA) procedures, wherein for each of the plurality of RA procedures, the information comprises an indication of a number of random access channel (RACH) preambles transmitted for the respective RA procedure; and transmitting an information message to a cell of the wireless network, wherein the information message comprises a plurality of RACH reports corresponding to the plurality of RA procedures, wherein each of the plurality of RACH reports comprises an indication of a number of RACH preambles transmitted for a respective one of the plurality of RA procedures.
[0257] 2. The method of embodiment 1, wherein the information message comprises a radio resource control (RRC) message.
[0258] 3. The method of any one of embodiments 1-2, wherein the information message includes the plurality of RACH reports and a RACH report list size indicating a number of the plurality of RACH reports included in the information message.
[0259] 4. The method according to any one of embodiments 1 to 3 further includes: sending a notification to the wireless network after storing the information, wherein the notification indicates the availability of information related to the multiple RA processes; and after sending the notification, receiving an information request message from a cell of the wireless network; wherein in response to receiving the information request message, the information message is sent as an information response message.
[0260] 5. The method of embodiment 4, wherein the notification is included as an information element of a radio resource control (RRC) message, wherein the information element indicates that RACH information is available.
[0261] 6. The method of any one of embodiments 4 to 5, wherein the notification is included in a measurement report message.
[0262] 7. The method of any one of embodiments 1 to 6, wherein each of the plurality of RACH reports further comprises a contention detection flag indicating whether contention resolution is unsuccessful for at least one RACH preamble sent for the corresponding RA procedure.
[0263] 8. The method according to any one of embodiments 1 to 7 further includes: executing the multiple RA processes, wherein each of the multiple RA processes is executed for a use case including at least one of the following: arrival of downlink or uplink data during a radio resource control (RRC) connection state when the uplink synchronization state is asynchronous, arrival of uplink data during an RRC connection state in which no physical uplink control channel (PUCCH) resources are available for a scheduling request (SR) to establish time alignment when adding an SCell, and / or beam failure recovery.
[0264] 9. The method according to any one of embodiments 1 to 8, wherein all multiple RA processes are for cells.
[0265] 10. A method according to any one of embodiments 1 to 8, wherein, for each RA process in the multiple RA processes, the information also includes a cell identifier associated with the corresponding RA process, and wherein each RACH report in the multiple RACH reports also includes a cell identifier associated with the corresponding RA process.
[0266] 11. The method of embodiment 10, wherein the first cell identifier is associated with a first RA procedure in the plurality of RA procedures, wherein the second cell identifier is associated with a second RA procedure in the plurality of RA procedures, and wherein the first cell identifier and the second cell identifier are different.
[0267] 12. The method according to any one of embodiments 10 to 11, wherein the cell identifier includes at least one of a local identifier of the cell and / or a global identifier of the cell.
[0268] 13. A method according to any one of embodiments 1 to 12, wherein, for each RA process in the multiple RA processes, the information also includes a public land mobile network (PLMN) identifier associated with the corresponding RA process.
[0269] 14. The method of embodiment 13, wherein sending the information message comprises sending the information message in response to the PLMN identifier matching a PLMN identifier associated with the cell.
[0270] 15. A method of operating a radio access network (RAN), the method comprising: receiving an information message from a wireless device, wherein the information message includes a plurality of random access channel (RACH) reports corresponding to a corresponding plurality of random access (RA) procedures, wherein each of the plurality of RACH reports includes an indication of a number of RACH preambles sent for a corresponding one of the plurality of RA procedures.
[0271] 16. The method of embodiment 15, wherein the information message comprises a radio resource control (RRC) message.
[0272] 17. The method of any one of embodiments 15-16, wherein the information message includes the plurality of RACH reports and a RACH report list size indicating a number of the plurality of RACH reports included in the information message.
[0273] 18. The method according to any one of embodiments 15 to 17 further includes: receiving a notification from a wireless device, wherein the notification indicates the availability of RACH information; and in response to receiving the notification, sending an information request message from a cell of the wireless network; wherein the information message is received as an information response message corresponding to the information request message.
[0274] 19. The method of embodiment 18, wherein the notification is included as an information element of a radio resource control (RRC) message, wherein the information element indicates that RACH information is available.
[0275] 20. The method of any one of embodiments 18 to 19, wherein the notification is included in a measurement report message.
[0276] 21. The method of any one of embodiments 15 to 20, wherein each of the plurality of RACH reports further comprises a contention detection flag indicating whether contention resolution is unsuccessful for at least one RACH preamble sent for the corresponding RA procedure.
[0277] 22. A method according to any one of embodiments 15 to 21, wherein each of the multiple RA processes is performed for a use case including at least one of the following: arrival of downlink or uplink data during a radio resource control (RRC) connection state when the uplink synchronization state is asynchronous, arrival of uplink data during an RRC connection state in which no physical uplink control channel (PUCCH) resources are available for a scheduling request (SR) to establish time alignment when adding an SCell, and / or beam failure recovery.
[0278] 23. The method of any one of embodiments 15 to 22, wherein all of the multiple RA procedures are for a cell.
[0279] 24. The method of any one of embodiments 15 to 22, wherein each of the plurality of RACH reports further comprises a cell identifier associated with a corresponding RA process.
[0280] 25. The method of embodiment 24, wherein the first cell identifier is associated with a first RA procedure in the plurality of RA procedures, wherein the second cell identifier is associated with a second RA procedure in the plurality of RA procedures, and wherein the first cell identifier and the second cell identifier are different.
[0281] 26. A method according to embodiment 25, wherein the information message is received at a first RAN node, wherein one of the multiple RACH reports includes a corresponding cell identifier associated with a cell of a second RAN node, and the method further includes: in response to the corresponding cell identifier being associated with the cell of the second RAN node, sending information of the one of the multiple RACH reports from the first RAN node to the second RAN node.
[0282] 27. The method of embodiment 26, wherein information of the one RACH report among the multiple RACH reports is sent to the second RAN node in a RACH indication message.
[0283] 28. The method of any one of embodiments 26 to 27, wherein information of the one RACH report among the multiple RACH reports is sent from the first RAN node to the second RAN node via an X2 / Xn interface.
[0284] 29. The method according to any one of embodiments 24 to 28, wherein the cell identifier includes at least one of a local identifier of the cell and / or a global identifier of the cell.
[0285] 30. The method according to any one of embodiments 15 to 29, wherein, for each RA process in the multiple RA processes, the information further includes a public land mobile network (PLMN) identifier associated with the corresponding RA process.
[0286] 31. A method for operating a radio access network (RAN), the method comprising: receiving an indication at a radio resource control (RRC) entity of the RAN that a wireless device has successfully completed a random access, RA, procedure, wherein the indication is received from a medium access control (MAC) entity; in response to the indication that the wireless device has successfully completed the RA procedure, initiating transmission of an information request message from the RRC entity to the wireless device; and receiving an information response message from the wireless device, wherein the information response message includes a random access channel (RACH) report for the RA procedure, and wherein the information response message corresponds to the information request message.
[0287] 32. The method of embodiment 31, wherein the RACH report includes an indication of the number of RACH preambles sent for the RA procedure.
[0288] 33. The method of any one of embodiments 31-32, wherein the RACH report further includes a contention detection flag indicating whether contention resolution was unsuccessful for at least one RACH preamble sent for the RA procedure.
[0289] 34. The method of any one of embodiments 31 to 33, wherein each of the information request message and the information response message comprises a corresponding radio resource control (RRC) message.
[0290] 35. The method of any one of embodiments 31 to 34, wherein the indication that the wireless device has successfully completed the RA procedure is received at the RRC entity from the MAC entity over the F1 interface.
[0291] 36. The method of embodiment 35, wherein the F1 interface is an F1-C interface.
[0292] 37. A method according to any one of embodiments 31 to 36, wherein the RRC entity is provided in a central unit (CU) node of the RAN, and wherein the MAC entity is provided in a distributed unit (DU) node of the RAN.
[0293] 38. The method of embodiment 37, wherein the CU and DU nodes are provided as elements of a Node B of the RAN.
[0294] 39. The method according to any one of embodiments 31 to 38 also includes: sending a RACH report to a MAC entity.
[0295] 40. A method according to embodiment 39, wherein the RACH report includes a cell identifier associated with a cell supported by the MAC entity, and wherein the RACH report is sent to the MAC entity in response to the RACH report including a cell identifier associated with a cell supported by the MAC entity.
[0296] 41. A method according to any one of embodiments 39 to 40, wherein the RACH report is sent to the MAC entity as an element of an access and mobility indication message.
[0297] 42. The method of any one of embodiments 39 to 41, wherein the RACH report is sent via an F1 interface.
[0298] 43. A method according to any one of embodiments 31 to 38, wherein the RRC entity is a first RRC entity, wherein the first cell identifier is associated with a MAC entity, wherein the RACH report includes a second cell identifier, and wherein the first cell identifier and the second cell identifier are different, the method further comprising: in response to the second cell identifier being associated with the second RRC entity, sending the RACH report to a second RRC entity different from the first RRC entity.
[0299] 44. A method according to any one of embodiments 31 to 38, wherein the RRC entity is provided at a first RAN node, wherein the first cell identifier is associated with a MAC entity, wherein the RACH report includes a second cell identifier, and wherein the first cell identifier and the second cell identifier are different, the method further comprising: in response to the second cell identifier being associated with the second RAN node, sending the RACH report to a second RAN node different from the first RAN node.
[0300] 45. A method according to any one of embodiments 31 to 44, wherein each RA process is performed for a use case including at least one of the following: arrival of downlink or uplink data during a radio resource control (RRC) connection state when the uplink synchronization state is asynchronous, arrival of uplink data during an RRC connection state in which no physical uplink control channel (PUCCH) resources are available for scheduling requests (SRs) to establish time alignment when adding SCells, and / or beam failure recovery.
[0301] 46. A method of operating a wireless device that provides communications with a wireless network, the method comprising: performing a random access (RA) procedure to a cell of the wireless network; and in response to successful completion of the RA procedure to the cell, sending an information available message to the cell, wherein the information available message includes an indication that random access channel (RACH) information for the RA procedure is available.
[0302] 47. The method of embodiment 46, wherein the information available message may be sent as a radio resource control (RRC) message.
[0303] 48. The method of any one of embodiments 46-47, wherein sending the information available message is initiated from a radio resource control (RRC) entity provided at the wireless device.
[0304] 49. The method according to any one of embodiments 46 to 48 further includes: after sending the information available message, receiving an information request message from a cell of the wireless network; and in response to receiving the information request message, sending an information response message, wherein the information response message includes a RACH report for the RA process.
[0305] 50. The method of embodiment 49, wherein the RACH report includes at least one of: an indication of the number of RACH preambles sent for the RA procedure, and / or a contention detection flag indicating whether contention resolution was unsuccessful for at least one RACH preamble sent for the RA procedure.
[0306] 51. The method according to any one of embodiments 46 to 50 also includes: sending information about the RA process from a medium access control (MAC) entity of the wireless device to a radio resource control (RRC) entity of the wireless device.
[0307] 52. The method of embodiment 51, wherein the information availability message is initiated from an RRC entity of the wireless device in response to receiving information about the RA process from a MAC entity of the wireless device.
[0308] 53. A method according to any one of embodiments 51 to 52, wherein the information about the RA process includes at least one of the following: one or more beam indices associated with the RACH preamble code transmission of the RA process, and / or a timestamp associated with the RACH preamble code transmission of the RA process.
[0309] 54. A method according to any one of embodiments 46 to 53, wherein each RA process is performed for a use case including at least one of the following: arrival of downlink or uplink data during a radio resource control (RRC) connection state when the uplink synchronization state is asynchronous, arrival of uplink data during an RRC connection state in which no physical uplink control channel (PUCCH) resources are available for a scheduling request (SR) to establish time alignment when adding an SCell, and / or beam failure recovery.
[0310] 55. A method of operating a radio access network (RAN), the method comprising: receiving an information available message from a wireless device at a cell of the RAN, wherein the information available message includes an indication that random access channel (RACH) information for a RA procedure is available; in response to receiving the information available message, sending an information request message from the cell of the wireless network to the wireless device; and receiving an information response message from the wireless device, wherein the information response message includes a RACH report for the RA procedure, and wherein the information response message corresponds to the information request message.
[0311] 56. The method of embodiment 55, wherein the RACH report includes at least one of: an indication of the number of RACH preambles sent for the RA procedure, and / or a contention detection flag indicating whether contention resolution was unsuccessful for at least one RACH preamble sent for the RA procedure.
[0312] 57. A wireless device (300), comprising: a processing circuit (303); and a memory (305) coupled to the processing circuit, wherein the memory comprises instructions that, when executed by the processing circuit, cause the wireless device to perform operations according to any one of embodiments 1 to 14 and 46 to 54.
[0313] 58. A wireless device (300) adapted to perform according to any one of embodiments 1 to 14 and 46 to 54.
[0314] 59. A computer program comprising program code to be executed by a processing circuit (303) of a wireless device (300), whereby execution of the program code causes the wireless device (300) to perform operations according to any one of embodiments 1 to 14 and 46 to 54.
[0315] 60. A computer program product comprising a non-transitory storage medium including program code to be executed by a processing circuit (303) of a wireless device (300) configured to operate in a communication network, whereby execution of the program code causes the wireless device (300) to perform operations according to any one of embodiments 1 to 14 and 46 to 54.
[0316] 61. A radio access network (RAN) node (400), the RAN node comprising: a processing circuit (303); and a memory (305) coupled to the processing circuit, wherein the memory comprises instructions which, when executed by the processing circuit, cause the RAN node to perform operations according to any one of embodiments 15 to 45 and 55 to 56.
[0317] 62. A first radio access network (RAN) node (400), wherein the RAN node is adapted to perform according to any one of embodiments 15 to 45 and 55 to 56.
[0318] 63. A computer program comprising program code to be executed by a processing circuit (403) of a Radio Access Network RAN node (400), whereby execution of the program code causes the RAN node (400) to perform operations according to any one of embodiments 15 to 45 and 55 to 56.
[0319] 64. A computer program product comprising a non-transitory storage medium comprising program code to be executed by a processing circuit (403) of a Radio Access Network RAN node (400), whereby execution of the program code causes the RAN node (400) to perform operations according to any one of embodiments 15 to 45 and 55 to 56.
[0320] 65. A method of operating a wireless device (300) that provides communications with a wireless network, the method comprising: storing (1509) first information in a memory (305), the first information relating to a first plurality of random access (RA) procedures, the first plurality of RA procedures being associated with a first public land mobile network (PLMN) having a first PLMN identifier; storing (1519) second information in the memory (305), the second information relating to a second plurality of RA procedures, the second plurality of RA procedures being associated with a second PLMN having a second PLMN identifier different from the first PLMN identifier; and sending (1525) an information message to at least one of the first PLMN and / or the second PLMN, wherein the information message comprises a plurality of RACH reports corresponding to the first plurality of RA procedure pairs associated with the first PLMN identifier based on the first information and / or corresponding to the second plurality of RA procedures associated with the second PLMN identifier based on the second information.
[0321] 66. The method according to embodiment 65 further includes: registering (1501) with a first PLMN having a first PLMN identifier; executing (1505) the first multiple RA processes when registering with the first PLMN; after registering with the first PLMN and after executing the first multiple RA processes, registering (1511) with a second PLMN having a second PLMN identifier; and executing (1505) the second multiple RA processes when registering with the second PLMN.
[0322] 67. A method according to embodiment 66, wherein sending the information message includes sending the information message to the second PLMN after performing the second plurality of RA procedures, wherein the information message includes a plurality of RACH reports, and the plurality of RACH reports correspond to the second plurality of RA procedures associated with the second PLMN identity based on the second information.
[0323] 68. The method of embodiment 67, wherein the information message omits RACH reporting corresponding to the first plurality of RA procedures associated with the first PLMN identity.
[0324] 69. The method of any one of embodiments 66 to 68 further comprises discarding the first information from the memory in response to registering with the second PLMN.
[0325] 70. A method according to any one of embodiments 65 to 66, wherein the information message includes a first plurality of RACH reports corresponding to the first plurality of RA processes associated with the first PLMN identifier based on the first information and a second plurality of RACH reports corresponding to the second plurality of RA processes associated with the second PLMN identifier based on the second information.
[0326] 71. The method according to any one of embodiments 65 to 66 further includes: after storing the first information and after storing the second information, receiving (1521) a RACH report request from the second PLMN; wherein sending the information message includes: in response to receiving the RACH report request from the second PLMN, sending the information message to the second PLMN.
[0327] 72. A method according to embodiment 71, wherein the information message includes multiple RACH reports corresponding to the second multiple RA processes associated with the second PLMN identity based on the second information, and omits the RACH report corresponding to the first multiple RA processes associated with the first PLMN identity based on the first information.
[0328] 73. The method of embodiment 72 further comprises discarding first information related to the first plurality of RA procedures from the memory in response to receiving a RACH report request from the second PLMN.
[0329] 74. The method according to embodiment 72 also includes: after sending the information message, saving the first information in a memory.
[0330] 75. A method according to embodiment 71, wherein the information message includes multiple RACH reports, which correspond to the first multiple RA procedures associated with the first PLMN identity based on the first information and correspond to the second multiple RA procedures associated with the second PLMN identity based on the second information.
[0331] 76. A method according to any one of embodiments 65 to 75, wherein, for each RA process in the first plurality of RA processes, the first information includes a first PLMN identifier, and wherein for each RA process in the second plurality of RA processes, the second information includes a second PLMN identifier.
[0332] 77. A method according to embodiment 76, wherein each of the multiple RACH reports corresponding to the first multiple RA processes includes a first PLMN identifier, and / or wherein each of the multiple RACH reports corresponding to the second multiple RA processes includes a second PLMN identifier.
[0333] 78. A method according to any one of embodiments 65 to 75, wherein the first information related to the first plurality of RA procedures includes a first PLMN identifier, and wherein the second information related to the second plurality of RA procedures includes a second PLMN identifier.
[0334] 79. A method according to embodiment 78, wherein the information message includes a first PLMN identifier associated with multiple RACH reports corresponding to the first multiple RA procedures, and / or wherein the information message includes a second PLMN identifier associated with multiple RACH reports corresponding to the second multiple RA procedures.
[0335] 80. A method according to any one of embodiments 65 to 79, wherein, for each RA process in the first plurality of RA processes, the first information includes an indication of the number of random access channel (RACH) preambles sent for the corresponding RA process, wherein for each RA process in the second plurality of RA processes, the second information includes an indication of the number of RACH preambles sent for the corresponding RA process, and wherein each RACH report in the plurality of RACH reports includes an indication of the number of RACH preambles sent for the first plurality of RA processes and / or a corresponding one of the second plurality of RA processes.
[0336] 81. A method according to any one of embodiments 65 to 80, wherein, for each RA process in the first plurality of RA processes, the first information includes a contention detection flag indicating whether contention resolution is unsuccessful for at least one RACH preamble code sent for the corresponding RA process, wherein for each RA process in the second plurality of RA processes, the second information includes a contention detection flag indicating whether contention resolution is unsuccessful for at least one RACH preamble code sent for the corresponding RA process, and wherein each RACH report in the plurality of RACH reports includes a contention detection flag for a corresponding one of the first plurality of RA processes and / or the second plurality of RA processes.
[0337] 82. A method of operating a wireless device that provides communications with a wireless network, the method comprising: registering (1601) with a first public land mobile network (PLMN) having a first PLMN identifier; performing (1605) a first plurality of random access (RA) procedures when registering with the first PLMN; storing (1609) information related to the first plurality of RA procedures, the first plurality of RA procedures being associated with the first PLMN having the first PLMN identifier; after registering with the first PLMN and after performing the first plurality of RA procedures, registering (1611) with a second PLMN having a second PLMN identifier, wherein the first PLMN identifier and the second PLMN identifier are different; and performing (1615) a second plurality of RA procedures when registering with the second PLMN without storing information related to the second plurality of RA procedures.
[0338] 83. The method according to embodiment 82 further includes: sending (1610) an information message to at least one of the first PLMN and / or the second PLMN, wherein the information message includes multiple RACH reports, and the multiple RACH reports correspond to the first multiple RA processes associated with the first PLMN identifier based on the first information.
[0339] 84. The method of embodiment 83, wherein sending the information message includes sending the information message to the first PLMN prior to registering with the second PLMN.
[0340] 85. A method according to any one of embodiments 83 to 84, wherein, for each RA process in the first plurality of RA processes, the information includes an indication of the number of random access channel (RACH) preamble codes sent for the corresponding RA process, and wherein each RACH report in the plurality of RACH reports includes an indication of the number of RACH preamble codes sent for a corresponding one of the first plurality of RA processes.
[0341] 86. A method according to any one of embodiments 83 to 85, wherein, for each RA process in the first plurality of RA processes, the first information includes a contention detection flag indicating whether contention resolution is unsuccessful for at least one RACH preamble code sent for the corresponding RA process, and each RACH report in the plurality of RACH reports includes a contention detection flag for a corresponding one of the first plurality of RA processes.
[0342] 87. A method of operating a wireless device that provides communication with a wireless network, the method comprising: storing first information related to a first random access (RA) process in a memory, the first RA process being associated with a first public land mobile network (PLMN) having a first PLMN identifier; storing second information related to a second RA process in the memory, the second RA process being associated with the first PLMN having a second PLMN identifier different from the first PLMN identifier; and sending an information message to at least one of the first PLMN and / or the second PLMN, wherein the information message includes a RACH report corresponding to a first RA process associated with the first PLMN identifier based on the first information and / or a RACH report corresponding to a second RA process associated with the second PLMN identifier based on the second information.
[0343] 88. The method according to embodiment 87 further includes: registering with a first PLMN having a first PLMN identifier; executing the first multiple RA processes when registering with the first PLMN; registering with a second PLMN having a second PLMN identifier after registering with the first PLMN and after executing the first RA process; and executing the second RA process when registering with the second PLMN.
[0344] 89. The method of embodiment 88, wherein sending the information message includes sending the information message to the second PLMN after performing the second RA procedure, wherein the information message includes a RACH report corresponding to the second RA procedure associated with the second PLMN identity based on the second information.
[0345] 90. The method of embodiment 89, wherein the information message omits any RACH reporting corresponding to a first RA procedure associated with the first PLMN identity.
[0346] 91. The method according to any one of embodiments 88 to 90 also includes: in response to registering with the second PLMN, discarding the first information from the memory.
[0347] 92. A method according to any one of embodiments 87 to 88, wherein the information message includes a first RACH report corresponding to a first RA process associated with a first PLMN identity based on the first information and a second RACH report corresponding to a second RA process associated with a second PLMN identity based on the second information.
[0348] 93. The method according to any one of embodiments 87 to 88 further includes: after storing the first information and after storing the second information, receiving a RACH report request from the second PLMN; wherein sending the information message includes: in response to receiving the RACH report request from the second PLMN, sending the information message to the second PLMN.
[0349] 94. A method according to embodiment 93, wherein the information message includes a RACH report corresponding to a second RA procedure associated with the second PLMN identity based on the second information, and omits any RACH report corresponding to a first RA procedure associated with the first PLMN identity based on the first information.
[0350] 95. The method of embodiment 94 further comprises discarding first information related to the first RA procedure from the memory in response to receiving a RACH report request from the second PLMN.
[0351] 96. The method according to embodiment 94 also includes: after sending the information message, saving the first information in a memory.
[0352] 97. The method of embodiment 93, wherein the information message includes a RACH report corresponding to a first RA procedure associated with a first PLMN identity based on the first information and a RACH report corresponding to a second RA procedure associated with a second PLMN identity based on the second information.
[0353] 98. A method according to any one of embodiments 87 to 97, wherein for the first RA procedure, the first information includes a first PLMN identifier, and wherein for the second RA procedure, the second information includes a second PLMN identifier.
[0354] 99. The method of embodiment 98, wherein the RACH report corresponding to the first RA procedure includes a first PLMN identifier, and / or wherein the RACH report corresponding to the second RA procedure includes a second PLMN identifier.
[0355] 100. The method of any one of embodiments 87 to 97, wherein the first information related to the first RA procedure includes a first PLMN identifier, and wherein the second information related to the second RA procedure includes a second PLMN identifier.
[0356] 101. The method of embodiment 100, wherein the information message includes a first PLMN identifier associated with a RACH report corresponding to a first RA procedure, and / or wherein the information message includes a second PLMN identifier associated with a RACH report corresponding to a second RA procedure.
[0357] 102. A method according to any one of embodiments 87 to 101, wherein, for a first RA process, the first information includes an indication of the number of random access channel (RACH) preamble codes sent for the first RA process, and wherein for a second RA process, the second information includes an indication of the number of RACH preamble codes sent for the second RA process.
[0358] 103. A method according to embodiment 102, wherein the RACH report corresponding to the first RA process includes an indication of the number of RACH preambles sent for the first RA process, and / or wherein the RACH report corresponding to the second RA process includes an indication of the number of RACH preambles sent for the second RA process.
[0359] 104. A method according to any one of embodiments 87 to 103, wherein, for a first RA process, the first information includes a contention detection flag indicating whether contention resolution is unsuccessful for at least one RACH preamble code sent for the first RA process, and wherein for a second RA process, the second information includes a contention detection flag indicating whether contention resolution is unsuccessful for at least one RACH preamble code sent for the second RA process.
[0360] 105. The method of embodiment 104, wherein the RACH report corresponding to the first RA process includes a contention detection flag for the first RA process, and / or wherein the RACH report corresponding to the second RA process includes a contention detection flag for the second RA process.
[0361] 106. A method of operating a wireless device that provides communication with a wireless network, the method comprising: registering with a first public land mobile network (PLMN) having a first PLMN identifier; performing a first random access (RA) procedure when registering with the first PLMN; storing information related to the first RA procedure, the first RA procedure being associated with the first PLMN having the first PLMN identifier; after registering with the first PLMN and after performing the first RA procedure, registering with a second PLMN having a second PLMN identifier, wherein the first PLMN identifier and the second PLMN identifier are different; and performing a second RA procedure when registering with the second PLMN without storing information related to the second RA procedure.
[0362] 107. The method according to embodiment 106 also includes: sending an information message to at least one of the first PLMN and / or the second PLMN, wherein the information message includes a RACH report, and the RACH report corresponds to a first RA process associated with the first PLMN identifier based on the first information.
[0363] 108. The method of embodiment 107, wherein sending the information message includes sending the information message to the first PLMN prior to registering with the second PLMN.
[0364] 109. A method according to any one of embodiments 107 to 108, wherein, for a first RA process, the information includes an indication of the number of random access channel RACH preamble codes sent for the first RA process, and wherein the RACH report includes an indication of the number of RACH preamble codes sent for the first RA process.
[0365] 110. A method according to any one of embodiments 107 to 109, wherein, for a first RA process, the information includes a contention detection flag indicating whether contention resolution is unsuccessful for at least one RACH preamble code sent for the first RA process, and wherein the RACH report includes the contention detection flag for the first RA process.
[0366] 111. A wireless device (300), comprising: a processing circuit (303); and a memory (305) coupled to the processing circuit, wherein the memory comprises instructions that, when executed by the processing circuit, cause the wireless device to perform operations according to any one of embodiments 65 to 110.
[0367] 112. A wireless device (300), wherein the wireless device is adapted to perform according to any one of embodiments 65 to 110.
[0368] 113. A computer program comprising program code to be executed by a processing circuit (303) of a wireless device (300), whereby execution of the program code causes the wireless device (300) to perform operations according to any one of embodiments 65 to 110.
[0369] 114. A computer program product comprising a non-transitory storage medium including program code to be executed by a processing circuit (303) of a wireless device (300), whereby execution of the program code causes the wireless device (300) to perform operations according to any one of embodiments 65 to 110.
[0370] References identified in the above disclosures are cited below.
[0371] References [1] 3GPP TS 36.331 V15.7.0 (2019-09)
[0372] References [2] 3GPP TS 36.321 V15.7.0 (2019-09)
[0373] References [3] 3GPP TS 38.321 V15.7.0 (2019-09)
[0374] References [4] 3GPP TS 38.300 V15.7.0 (2019-09)
[0375] References [5] 3GPP TS 38.423 V15.5.0 (2019-09)
[0376] References [6] 3GPP TS 38.331 V15.7.0 (2019-09)
[0377] References [7] 3GPP TS 38.473 V15.7.0 (2019-09)
[0378] Additional explanation is provided below.
[0379] Generally, all terms used in this article should be interpreted according to their common meaning in the relevant technical field, unless different meanings are clearly given and / or different meanings are implied from the context of its use. Unless clearly stated, all references to one / an / the element, equipment, assembly, device, step, etc. should be interpreted as referring to at least one instance of an element, equipment, assembly, device, step, etc. in an open manner. The steps of any method disclosed herein do not have to be performed in the exact order disclosed, unless a step is clearly described as after or before another step and / or it is implied that a step must be after or before another step. Where appropriate, any feature of any embodiment disclosed herein may be applied to any other embodiment. Similarly, any advantage of any embodiment may be applicable to any other embodiment, and vice versa. Other purposes, features and advantages of the attached embodiments will be apparent from the following description.
[0380] Some embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as being limited to the embodiments set forth herein; rather, these embodiments are provided merely as examples to convey the scope of the subject matter to those skilled in the art.
[0381] Fig.17 A wireless network is illustrated in accordance with some embodiments.
[0382] Although the subject matter described herein may be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are directed to wireless networks such as Fig.17 For simplicity, Fig.17 The wireless network of FIG. 1 depicts only the network QQ106, the network nodes QQ160 and QQ160b, and the WDs QQ110, QQ110b, and QQ110c (also referred to as mobile terminals). In practice, the wireless network may further include any additional elements suitable for supporting communication between wireless devices or between a wireless device and another communication device (e.g., a landline phone, a service provider, or any other network node or terminal device). In the components shown, the network node QQ160 and the wireless device (WD) QQ110 are depicted in additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate wireless devices to access and / or use services provided by or via the wireless network.
[0383] A wireless network may include and / or interface with any type of communication, telecommunication, data, cellular and / or radio network or other similar type of system. In some embodiments, a wireless network may be configured to operate according to a particular standard or other type of predefined rules or procedures. Thus, particular embodiments of a wireless network may implement communication standards such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards such as IEEE 802.11 standards; and / or any other suitable wireless communication standards such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, and / or ZigBee standards.
[0384] The network QQ106 may include one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.
[0385] The network node QQ160 and WD QQ110 include various components described in more detail below. These components work together to provide network node and / or wireless device functions, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may include any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components or systems that can facilitate or participate in the communication of data and / or signals via wired or wireless connections.
[0386] As used herein, a network node refers to a device that is capable of, configured to, arranged to, and / or operable to communicate directly or indirectly with a wireless device and / or with other network nodes or devices in a wireless network to enable and / or provide wireless access to a wireless device and / or perform other functions (e.g., management) in the wireless network. Examples of 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)). Base stations can be classified based on the amount of coverage provided by the base stations (or in other words, their transmit power levels), and then the base stations can also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station can be a relay node or a relay donor node that controls a relay. A network node may also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU) (sometimes also referred to as a remote radio head (RRH)). Such a remote radio unit 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). Other examples of network nodes include multi-standard radio (MSR) equipment such as an MSR BS, a network controller such as a radio network controller (RNC) or a base station controller (BSC), a base transceiver station (BTS), a transmission point, a transmission node, a multi-cell / multicast coordination entity (MCE), a core network node (e.g., MSC, MME), an O&M node, an OSS node, a SON node, a positioning node (e.g., E-SMLC), and / or an MDT. As another example, a network node may be a virtual network node as described in more detail below. However, more generally, a network node may represent any suitable device (or group of devices) that is capable of, configured to, arranged to, and / or operable to enable a wireless device to access a wireless network and / or provide access to a wireless network to a wireless device or provide a certain service to a wireless device that has accessed a wireless network.
[0387] exist Fig.17 In FIG. 1 , the network node QQ160 includes a processing circuit QQ170, a device readable medium QQ180, an interface QQ190, an auxiliary device QQ184, a power supply QQ186, a power supply circuit QQ187, and an antenna QQ162. Fig.17The network node QQ160 shown in the example wireless network may represent a device including a combination of the hardware components shown, and other embodiments may include network nodes with different combinations of components. It should be understood that the network node includes any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. In addition, although the components of the network node QQ160 are depicted as a single box located within a larger box, or nested within multiple boxes, in reality, the network node may include multiple different physical components that make up a single shown component (for example, the device readable medium QQ180 may include multiple separate hard drives and multiple RAM modules).
[0388] Similarly, the network node QQ160 can be composed of multiple physically separated components (e.g., a node B component and an RNC component, or a BTS component and a BSC component, etc.), each of which can have their corresponding components. In certain scenarios where the network node QQ160 includes multiple individual components (e.g., a BTS and a BSC component), one or more individual components can be shared between several network nodes. For example, a single RNC can control multiple node Bs. In this scenario, each unique node B and RNC pair can be considered as a single individual network node in some cases. In some embodiments, the network node QQ160 can be configured to support multiple radio access technologies (RATs). In this embodiment, some components can be copied (e.g., separate device-readable media QQ180 for different RATs), and some components can be reused (e.g., the same antenna QQ162 can be shared by RATs). The network node QQ160 can also include multiple sets of various illustrated components for different wireless technologies (e.g., GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies) integrated into the network node QQ160. These wireless technologies may be integrated into the same or different chips or chipsets and other components within network node QQ 160 .
[0389] The processing circuit QQ170 is configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being provided by the network node. Such operations performed by the processing circuit QQ170 may include processing information obtained by the processing circuit QQ170 in the following manner: for example, by converting the obtained information into other information, comparing the obtained information or the converted information with information stored in the network node, and / or performing one or more operations based on the obtained information or the converted information, and making a determination as a result of the processing.
[0390] The processing circuit QQ170 may include a combination of one or more of the following: a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or a combination of hardware, software, and / or encoded logic operable to provide network node QQ160 functionality alone or in conjunction with other network node QQ160 components (e.g., device readable medium QQ180). For example, the processing circuit QQ170 may execute instructions stored in the device readable medium QQ180 or in a memory within the processing circuit QQ170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, the processing circuit QQ170 may include a system on a chip (SOC).
[0391] In some embodiments, the processing circuitry QQ170 may include one or more of a radio frequency (RF) transceiver circuitry QQ172 and a baseband processing circuitry QQ174. In some embodiments, the radio frequency (RF) transceiver circuitry QQ172 and the baseband processing circuitry QQ174 may be on separate chips (or chipsets), boards, or units (e.g., a radio unit and a digital unit). In alternative embodiments, some or all of the RF transceiver circuitry QQ172 and the baseband processing circuitry QQ174 may be on the same chip or chipset, board, or unit.
[0392] In certain embodiments, some or all of the functions described herein as provided by a network node, base station, eNB or other such network device may be performed by a processing circuit QQ170 executing instructions stored on a device-readable medium QQ180 or a memory within the processing circuit QQ170. In alternative embodiments, some or all of the functions may be provided by the processing circuit QQ170, such as in a hard-wired manner, without the need to execute instructions stored on a separate or independent device-readable medium. In any of those embodiments, whether or not instructions stored on a device-readable storage medium are executed, the processing circuit QQ170 may be configured to perform the described functions. The benefits provided by such functions are not limited to only the processing circuit QQ170 or other components of the network node QQ160, but are enjoyed by the network node QQ160 as a whole and / or generally by end users and wireless networks.
[0393] The device-readable medium QQ180 may include any form of volatile or non-volatile computer-readable memory, including but not limited to permanent memory, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disk (CD), or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable memory device and / or computer-executable memory device that stores information, data, and / or instructions that can be used by the processing circuit QQ170. The device-readable medium QQ180 may store any suitable instructions; data or information, including computer programs; software; applications including one or more of logic, rules, code, tables, etc.; and / or other instructions that can be executed by the processing circuit QQ170 and utilized by the network node QQ160. The device-readable medium QQ180 may be used to store any calculations performed by the processing circuit QQ170 and / or any data received via the interface QQ190. In some embodiments, processing circuitry QQ170 and device readable medium QQ180 may be considered to be integrated.
[0394] Interface QQ190 is used for wired or wireless communication of signaling and / or data between network node QQ160, network QQ106 and / or WD QQ110. As shown, interface QQ190 includes a port / terminal QQ194 for sending and receiving data to network QQ106 via a wired connection, for example. Interface QQ190 also includes a radio front-end circuit QQ192, which can be coupled to antenna QQ162 or is a part of antenna QQ162 in some embodiments. Radio front-end circuit QQ192 includes filter QQ198 and amplifier QQ196. Radio front-end circuit QQ192 can be connected to antenna QQ162 and processing circuit QQ170. The radio front-end circuit can be configured to adjust the signal transmitted between antenna QQ162 and processing circuit QQ170. Radio front-end circuit QQ192 can receive digital data to be sent to other network nodes or WDs via a wireless connection. The radio front end circuit QQ192 may convert the digital data into a radio signal having appropriate channel and bandwidth parameters using a combination of filters QQ198 and / or amplifiers QQ196. The radio signal may then be transmitted via antenna QQ162. Similarly, when receiving data, antenna QQ162 may collect radio signals, which are then converted into digital data by the radio front end circuit QQ192. The digital data may be delivered to the processing circuit QQ170. In other embodiments, the interface may include different components and / or different combinations of components.
[0395] In some alternative embodiments, the network node QQ160 may not include a separate radio front end circuit QQ192, instead the processing circuit QQ170 may include the radio front end circuit and may be connected to the antenna QQ162 without the separate radio front end circuit QQ192. Similarly, in some embodiments, all or some of the RF transceiver circuit QQ172 may be considered part of the interface QQ190. In other embodiments, the interface QQ190 may include one or more ports or terminals QQ194, the radio front end circuit QQ192, and the RF transceiver circuit QQ172 as part of a radio unit (not shown), and the interface QQ190 may communicate with the baseband processing circuit QQ174, which is part of a digital unit (not shown).
[0396] Antenna QQ162 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna QQ162 may be coupled to the radio front end circuit QQ190 and may be any type of antenna capable of wirelessly sending and receiving data and / or signals. In some embodiments, antenna QQ162 may include one or more omnidirectional, sector or flat panel antennas operable to send / receive radio signals between, for example, 2 GHz and 66 GHz. Omnidirectional antennas may be used to send / receive radio signals in any direction, sector antennas may be used to send / receive radio signals from devices within a specific area, and flat panel antennas may be line of sight antennas for sending / receiving radio signals on a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In some embodiments, antenna QQ162 may be separated from network node QQ160 and may be connected to network node QQ160 via an interface or port.
[0397] Antenna QQ162, interface QQ190 and / or processing circuit QQ170 can be configured to perform any receiving operation and / or certain acquisition operations described herein as being performed by a network node. Any information, data and / or signal can be received from a wireless device, another network node and / or any other network device. Similarly, antenna QQ162, interface QQ190 and / or processing circuit QQ170 can be configured to perform any sending operation described herein as being performed by a network node. Any information, data and / or signal can be sent to a wireless device, another network node and / or any other network device.
[0398] The power circuit QQ187 may include or be coupled to a power management circuit and is configured to supply power to the components of the network node QQ160 to perform the functions described herein. The power circuit QQ187 may receive power from a power source QQ186. The power source QQ186 and / or the power circuit QQ187 may be configured to provide power to the various components of the network node QQ160 in a form suitable for the corresponding components (e.g., at the voltage and current levels required by each corresponding component). The power source QQ186 may be included in the power circuit QQ187 and / or the network node QQ160 or outside the power circuit QQ187 and / or the network node QQ160. For example, the network node QQ160 may be connected to an external power source (e.g., an electrical socket) via an input circuit or interface (such as a cable), whereby the external power source supplies power to the power circuit QQ187. As another example, the power supply QQ186 may include a power source in the form of a battery or a battery pack, which is connected to or integrated in the power circuit QQ187. If the external power source fails, the battery can provide backup power. Other types of power sources, such as photovoltaic devices, may also be used.
[0399] Alternative embodiments of network node QQ 160 may include, in addition to Fig.17 Additional components beyond those shown may be responsible for providing certain aspects of the functionality of the network node, including any functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node QQ 160 may include a user interface device that allows information to be input into the network node QQ 160 and allows information to be output from the network node QQ 160. This may allow a user to perform diagnostics, maintenance, repair, and other management functions for the network node QQ 160.
[0400] As used herein, a wireless device (WD) refers to a device that can, is configured to, is arranged to and / or is operable to wirelessly communicate with a network node and / or other wireless devices. Unless otherwise specified, the term WD may be used interchangeably with a user equipment (UE) in this article. Wireless communication may involve the use of electromagnetic waves, radio waves, infrared waves and / or other types of signals suitable for transmitting information through the air to send and / or receive wireless signals. In some embodiments, a WD may be configured to send and / or receive information without direct human interaction. For example, a WD may be designed to send information to a network according to a predetermined schedule when triggered by an internal or external event or in response to a request from a network. Examples of WD include, but are not limited to, smart phones, mobile phones, mobile phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, laptops, laptop embedded devices (LEEs), laptop mounted devices (LMEs), smart devices, wireless user scheduled devices (CPEs), vehicle-mounted wireless terminal devices, etc. WD can support device-to-device (D2D) communication, for example, by implementing 3GPP standards for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-everything (V2X), and in this case can be referred to as a D2D communication device. As another specific example, in an Internet of Things (IoT) scenario, WD can represent a machine or other device that performs monitoring and / or measurement and sends the results of such monitoring and / or measurement to another WD and / or network node. In this case, WD can be a machine-to-machine (M2M) device, which can be referred to as an MTC device in the 3GPP context. As a specific example, WD can be a UE that implements the 3GPP narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or household or personal appliances (e.g., refrigerators, televisions, etc.), personal wearable devices (e.g., watches, fitness trackers, etc.). In other cases, WD can represent a vehicle or other device that can monitor and / or report its operating status or other functions associated with its operation. As mentioned above, WD can represent the end point of wireless connection, in which case, the device can be referred to as a wireless terminal. In addition, as mentioned above, WD can be mobile, in which case, it can also be referred to as a mobile device or a mobile terminal.
[0401] As shown, the wireless device QQ110 includes an antenna QQ111, an interface QQ114, a processing circuit QQ120, a device-readable medium QQ130, a user interface device QQ132, an auxiliary device QQ134, a power supply QQ136, and a power supply circuit QQ137. The WDQQ110 may include multiple sets of one or more of the components shown for different wireless technologies supported by the WDQQ110 (e.g., GSM, WCDMA, LTE, NR, Wi-Fi, WiMAX, or Bluetooth wireless technologies, to name a few). These wireless technologies may be integrated into the same or different chips or chipsets as other components within the WDQQ110.
[0402] Antenna QQ111 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals, and is connected to interface QQ114. In some alternative embodiments, antenna QQ111 may be separated from WD QQ110 and may be connected to WD QQ110 via an interface or port. Antenna QQ111, interface QQ114, and / or processing circuit QQ120 may be configured to perform any receiving or transmitting operation described herein as being performed by WD. Any information, data, and / or signal may be received from a network node and / or another WD. In some embodiments, the radio front-end circuit and / or antenna QQ111 may be considered an interface.
[0403] As shown, the interface QQ114 includes a radio front-end circuit QQ112 and an antenna QQ111. The radio front-end circuit QQ112 includes one or more filters QQ118 and an amplifier QQ116. The radio front-end circuit QQ114 is connected to the antenna QQ111 and the processing circuit QQ120, and is configured to adjust the signal transmitted between the antenna QQ111 and the processing circuit QQ120. The radio front-end circuit QQ112 may be coupled to the antenna QQ111 or as part of the antenna QQ111. In some embodiments, the WD QQ110 may not include a separate radio front-end circuit QQ112; instead, the processing circuit QQ120 may include a radio front-end circuit and may be connected to the antenna QQ111. Similarly, in some embodiments, some or all of the RF transceiver circuit QQ122 may be considered as part of the interface QQ114. The radio front-end circuit QQ112 may receive digital data to be sent to other network nodes or WDs via a wireless connection. The radio front-end circuit QQ112 may convert the digital data into a radio signal with appropriate channel and bandwidth parameters using a combination of filters QQ118 and / or amplifiers QQ116. The radio signals may then be transmitted via antenna QQ111. Similarly, when receiving data, antenna QQ111 may collect radio signals, which are then converted into digital data by radio front-end circuit QQ112. The digital data may be passed to processing circuit QQ120. In other embodiments, the interface may include different components and / or different combinations of components.
[0404] The processing circuit QQ120 may include a combination of one or more of the following: a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or a combination of hardware, software, and / or encoded logic operable to provide WD QQ110 functionality alone or in combination with other WD QQ110 components (e.g., device readable medium QQ130, WD QQ110 functionality). Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, the processing circuit QQ120 may execute instructions stored in the device readable medium QQ130 or in a memory within the processing circuit QQ120 to provide the functionality disclosed herein.
[0405] As shown, the processing circuit QQ120 includes one or more of the following: RF transceiver circuit QQ122, baseband processing circuit QQ124, and application processing circuit QQ126. In other embodiments, the processing circuit may include different components and / or different combinations of components. In some embodiments, the processing circuit QQ120 of WD QQ110 may include a SOC. In some embodiments, the RF transceiver circuit QQ122, the baseband processing circuit QQ124, and the application processing circuit QQ126 may be located on a separate chip or chipset. In an alternative embodiment, part or all of the baseband processing circuit QQ124 and the application processing circuit QQ126 may be combined into one chip or chipset, and the RF transceiver circuit QQ122 may be located on a separate chip or chipset. In other alternative embodiments, part or all of the RF transceiver circuit QQ122 and the baseband processing circuit QQ124 may be on the same chip or chipset, and the application processing circuit QQ126 may be on a separate chip or chipset. In other alternative embodiments, part or all of the RF transceiver circuit QQ122, baseband processing circuit QQ124, and application processing circuit QQ126 may be combined in the same chip or chipset. In some embodiments, the RF transceiver circuit QQ122 may be part of the interface QQ114. The RF transceiver circuit QQ122 may condition the RF signal for the processing circuit QQ120.
[0406] In some embodiments, some or all of the functions described herein as being performed by the WD may be provided by a processing circuit QQ120 executing instructions stored on a device-readable medium QQ130, which may be a computer-readable storage device medium in some embodiments. In alternative embodiments, some or all of the functions may be provided by the processing circuit QQ120, such as in a hard-wired manner, without executing instructions stored on a separate or independent device-readable storage medium. In any of those specific embodiments, the processing circuit QQ120 may be configured to perform the described functions, regardless of whether instructions stored on a device-readable storage medium are executed. The benefits provided by such functions are not limited to only the processing circuit QQ120 or other components of the WD QQ110, but are enjoyed by the WD QQ110 as a whole and / or generally by end users and wireless networks.
[0407] Processing circuit QQ120 may be configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being performed by the WD. Such operations performed by processing circuit QQ120 may include processing information obtained by processing circuit QQ120, such as by converting the obtained information into other information, comparing the obtained information or the converted information with information stored by WD QQ110, and / or performing one or more operations based on the obtained information or the converted information; and making a determination as a result of the processing.
[0408] The device-readable medium QQ130 may be operable to store a computer program; software; an application including one or more of logic, rules, code, tables, etc.; and / or other instructions executable by the processing circuit QQ120. The device-readable medium QQ130 may include a computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), a mass storage medium (e.g., a hard disk), a removable storage medium (e.g., a compact disk (CD) or a digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable storage device that stores information, data, and / or instructions that may be used by the processing circuit QQ120. In some embodiments, the processing circuit QQ120 and the device-readable medium QQ130 may be considered integrated.
[0409] The user interface device QQ132 may provide a component that allows a human user to interact with the WD QQ110. This interaction may have a variety of forms, such as visual, auditory, tactile, etc. The user interface device QQ132 may be operable to generate output to the user and allow the user to provide input to the WD QQ110. The type of interaction may vary depending on the type of user interface device QQ132 installed in the WD QQ110. For example, if the WD QQ110 is a smart phone, the interaction may be through a touch screen; if the WD QQ110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alarm (e.g., if smoke is detected). The user interface device QQ132 may include input interfaces, devices, and circuits, as well as output interfaces, devices, and circuits. The user interface device QQ132 is configured to allow information to be input to the WD QQ110, and is connected to the processing circuit QQ120 to allow the processing circuit QQ120 to process the input information. The user interface device QQ132 may include, for example, a microphone, a proximity sensor or other sensor, a key / button, a touch display, one or more cameras, a USB port, or other input circuits. The user interface device QQ132 is also configured to allow information from the WD QQ110 to be output, and to allow the processing circuit QQ120 to output information from the WD QQ110. The user interface device QQ132 may include, for example, a speaker, a display, a vibration circuit, a USB port, a headphone port, or other output circuits. By using one or more input and output interfaces, devices, and circuits of the user interface device QQ132, the WD QQ110 may communicate with an end user and / or a wireless network and allow them to benefit from the functionality described herein.
[0410] The auxiliary device QQ134 is operable to provide more specific functions that may not normally be performed by the WD. This may include specialized sensors for taking measurements for various purposes, interfaces for additional types of communications (such as wired communications), etc. The inclusion and types of components of the auxiliary device QQ134 may vary depending on the embodiment and / or scenario.
[0411] In some embodiments, the power source QQ136 may be in the form of a battery or battery pack. Other types of power sources may also be used, such as an external power source (e.g., a power outlet), a photovoltaic device, or a battery. WD QQ110 may also include a power circuit QQ137 for delivering power from the power source QQ136 to various parts of the WD QQ110 that require power from the power source QQ136 to perform any functions described or indicated herein. In some embodiments, the power circuit QQ137 may include a power management circuit. The power circuit QQ137 may additionally or alternatively be operable to receive power from an external power source; in this case, the WD QQ110 may be able to connect to an external power source (e.g., a power outlet) via an input circuit or interface (e.g., a power cable). In some embodiments, the power circuit QQ137 may also be operable to deliver power from an external power source to the power source QQ136. This may be used, for example, to charge the power source QQ136. The power circuit QQ137 may perform any formatting, conversion, or other modifications to the power from the power source QQ136 so that the power is suitable for the corresponding components of the WD QQ110 being powered.
[0412] Fig.18 A user equipment according to some embodiments is illustrated.
[0413] Fig.18 An embodiment of a UE according to the various aspects described herein is illustrated. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and / or operates the associated device. Rather, a UE may represent a device that is intended to be sold to or operated by a human user but may not be, or may not initially be, associated with a particular human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended to be sold to or operated by an end user, but may be associated with or operated for the benefit of a user (e.g., a smart power meter). UEQQ2200 may be any UE identified by the Third Generation Partnership Project (3GPP), including a NB-IoT UE, a Machine Type Communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. As Fig.18 As shown, UE QQ200 is an example of a WD configured to communicate according to one or more communication standards promulgated by the Third Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE and / or 5G standards. As previously mentioned, the terms WD and UE may be used interchangeably. Therefore, although Fig.18 It is UE, but the components discussed in this article are also applicable to WD and vice versa.
[0414] exist Fig.18In the embodiment, UE QQ200 includes a processing circuit QQ201, which is operably coupled to an input / output interface QQ205, a radio frequency (RF) interface QQ209, a network connection interface QQ211, a memory QQ215 (including a random access memory (RAM) QQ217, a read-only memory (ROM) QQ219, and a storage medium QQ221, etc.), a communication subsystem QQ231, a power supply QQ233, and / or any other components, or any combination thereof. The storage medium QQ221 includes an operating system QQ223, an application QQ225, and data QQ227. In other embodiments, the storage medium QQ221 may include other similar types of information. Some UEs may utilize Fig.18 All components shown, or only a subset of these components. The degree of integration between components may vary for different UEs. In addition, some UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
[0415] exist Fig.18 In the embodiment of the present invention, the processing circuit QQ201 can be configured to process computer instructions and data. The processing circuit QQ201 can be configured to implement: any sequential state machine operable to execute machine instructions stored as a machine-readable computer program in a memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more general-purpose processors (e.g., microprocessors or digital signal processors (DSPs)) storing programs together with appropriate software; or any combination of the above. For example, the processing circuit QQ201 may include two central processing units (CPUs). The data may be information in a form suitable for use by a computer.
[0416] In the depicted embodiment, the input / output interface QQ205 can be configured to provide a communication interface to an input device, an output device, or an input and output device. The UE QQ200 can be configured to use an output device via the input / output interface QQ205. The output device can use an interface port of the same type as the input device. For example, a USB port can be used to provide input to the UE QQ200 and output from the UE QQ200. The output device can be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, a transmitter, a smart card, another output device, or any combination thereof. The UE QQ200 can be configured to use an input device via the input / output interface QQ205 to allow the user to capture information into the UE QQ200. The input device can include a touch-sensitive display or a presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse, a trackball, a steering wheel, a trackpad, a roller, a smart card, etc. The presence-sensitive display can include a capacitive or resistive touch sensor that senses input from the user. The sensor can be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another similar sensor, or any combination thereof. For example, the input device can be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.
[0417] exist Fig.18 In the embodiment of the present invention, the RF interface QQ209 can be configured to provide a communication interface to RF components such as transmitters, receivers and antennas. The network connection interface QQ211 can be configured to provide a communication interface to the network QQ243a. The network QQ243a can cover a wired and / or wireless network, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network or any combination thereof. For example, the network QQ243a can include a Wi-Fi network. The network connection interface QQ211 can be configured to include a receiver and a transmitter interface for communicating with one or more other devices through a communication network according to one or more communication protocols (e.g., Ethernet, TCP / IP, SONET, ATM, etc.). The network connection interface QQ211 can implement receiver and transmitter functions suitable for communication network links (e.g., optical, electrical, etc.). The transmitter and receiver functions can share circuit components, software or firmware, or alternatively can be implemented separately.
[0418] RAM QQ217 can be configured to interface with processing circuit QQ201 via bus QQ202 to provide storage or cache of data or computer instructions during execution of software programs such as operating systems, applications and device drivers. ROM QQ219 can be configured to provide computer instructions or data to processing circuit QQ201. For example, ROM QQ219 can be configured to store unchanged low-level system code or data for basic system functions (e.g., basic input and output (I / O), startup, or keystrokes received from a keyboard) stored in non-volatile memory. Storage medium QQ221 can be configured to include memory, such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only storage (EEPROM), disk, optical disk, floppy disk, hard disk, removable disk or flash drive. In one example, storage medium QQ221 can be configured to include operating system QQ223, application QQ225 such as web browser application, widget or gadget engine or another application, and data file QQ227. The storage medium QQ221 may store any one of a variety of different operating systems or a combination of operating systems for use by the UE QQ200 .
[0419] The storage medium QQ221 may be configured to include multiple physical drive units, such as a redundant array of independent disks (RAID), a floppy disk drive, a flash memory, a USB flash drive, an external hard drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile disc (HD-DVD) optical drive, an internal hard drive, a Blu-ray optical drive, a holographic digital data storage (HDDS) optical drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro DIMM SDRAM, a smart card memory (e.g., a subscriber identity module (SIM) or a removable user identity (RUIM) module), other memories, or any combination thereof. The storage medium QQ221 may allow the UE QQ200 to access computer executable instructions, applications, etc. stored on a temporary or non-temporary storage medium to unload data or upload data. An article (such as an article utilizing a communication system) may be tangibly embodied in the storage medium QQ221, which may include a device-readable medium.
[0420] exist Fig.18In the embodiment of the present invention, the processing circuit QQ201 can be configured to use the communication subsystem QQ231 to communicate with the network QQ243b. The network QQ243a and the network QQ243b can be the same network or different networks. The communication subsystem QQ231 can be configured to include one or more transceivers for communicating with the network QQ243b. For example, the communication subsystem QQ231 can be configured to include one or more transceivers for communicating with one or more remote transceivers of another device (such as another WD, UE or base station of a radio access network (RAN)) capable of wireless communication according to one or more communication protocols (such as IEEE 802.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc.). Each transceiver can include a transmitter QQ233 and / or a receiver QQ235 that respectively implements a transmitter or receiver function suitable for a RAN link (such as frequency allocation, etc.). In addition, the transmitter QQ233 and the receiver QQ235 of each transceiver can share circuit components, software, or firmware, or can alternatively be implemented separately.
[0421] In the illustrated embodiment, the communication functions of the communication subsystem QQ231 may include data communication, voice communication, multimedia communication, short-range communication (such as Bluetooth, near-field communication), location-based communication (such as using a global positioning system (GPS) to determine location), another similar communication function, or any combination thereof. For example, the communication subsystem QQ231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network QQ243b may cover a wired and / or wireless network (such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network, or any combination thereof). For example, the network QQ243b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power supply QQ213 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE QQ200.
[0422] The features, benefits and / or functions described herein may be implemented in one of the components of UE QQ200, or may be divided across multiple components of UE QQ200. In addition, the features, benefits and / or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, the communication subsystem QQ231 may be configured to include any component described herein. In addition, the processing circuit QQ201 may be configured to communicate with any of such components via bus QQ202. In another example, any such component may be represented by a program instruction stored in a memory, which executes the corresponding function described herein when executed by the processing circuit QQ201. In another example, the function of any such component may be divided between the processing circuit QQ201 and the communication subsystem QQ231. In another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.
[0423] Fig.19 A virtualized environment is illustrated in accordance with some embodiments.
[0424] Fig.19 It is a schematic block diagram illustrating a virtualized environment QQ300 in which the functions implemented by some embodiments can be virtualized. In the current context, virtualization means creating a virtual version of a device or equipment, which may include a virtualized hardware platform, storage device, and network resources. As used herein, virtualization may be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or a device (e.g., a UE, a wireless device, or any other type of communication device) or a component thereof, and relates to an implementation in which at least a portion of the functions are implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines, or containers executed on one or more physical processing nodes in one or more networks).
[0425] In some embodiments, some or all of the functionality described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments QQ300 hosted by one or more hardware nodes QQ330. Furthermore, in embodiments where the virtual nodes are not radio access nodes or do not require radio connectivity (e.g., core network nodes), the network nodes may be fully virtualized.
[0426] These functions may be implemented by one or more applications QQ320 (alternatively referred to as software instances, virtual devices, network functions, virtual nodes, virtual network functions, etc.) to implement certain features, functions, and / or benefits of some embodiments disclosed herein. Application QQ320 runs in a virtualization environment QQ300, which provides hardware QQ330 including processing circuitry QQ360 and memory QQ390. Memory QQ390 contains instructions QQ395 executable by processing circuitry QQ360, whereby application QQ320 is operable to provide one or more of the features, benefits, and / or functions disclosed herein.
[0427] The virtualized environment QQ300 includes a general or dedicated network hardware device QQ330, which includes a set of one or more processors or processing circuits QQ360, which may be commercial off-the-shelf (COTS) processors, specialized application-specific integrated circuits (ASICs), or any other type of processing circuit including digital or analog hardware components or dedicated processors. Each hardware device may include a memory QQ390-1, which may be a non-persistent memory for temporarily storing instructions QQ395 or software executed by the processing circuit QQ360. Each hardware device may include one or more network interface controllers (NICs) QQ370 (also known as network interface cards), which include a physical network interface QQ380. Each hardware device may also include a non-temporary persistent machine-readable storage medium QQ390-2 in which software QQ395 and / or instructions executable by the processing circuit QQ360 are stored. Software QQ395 may include any type of software, including software for instantiating one or more virtual layers QQ350 (also referred to as a hypervisor), software for executing virtual machines QQ340, and software that enables execution of the functions, features and / or benefits described in connection with some of the embodiments described herein.
[0428] The virtual machine QQ340 includes virtual processing, virtual memory, virtual network or interface, and virtual storage, and can be run by a corresponding virtual layer QQ350 or hypervisor. Different embodiments of instances of the virtual device QQ320 can be implemented on one or more virtual machines QQ340, and these implementations can be done in different ways.
[0429] During operation, processing circuitry QQ 360 executes software QQ 395 that instantiates a hypervisor or virtualization layer QQ 350 , which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer QQ 350 may present to virtual machine QQ 340 a virtual operating platform that appears to be network hardware.
[0430] like Fig.19As shown, hardware QQ330 can be an independent network node with common or specific components. Hardware QQ330 can include antenna QQ3225 and can implement some functions via virtualization. Alternatively, hardware QQ330 can be part of a larger hardware cluster (e.g., such as in a data center or customer premise equipment (CPE)), in which many hardware nodes work together and are managed via management and orchestration (MANO) QQ3100 that oversees the life cycle management of application QQ320, among other things.
[0431] In some contexts, virtualization of hardware is referred to as network function virtualization (NFV). NFV can be used to consolidate many network equipment types onto industry-standard high-volume server hardware, physical switches, and physical storage devices, which can be located in data centers and client devices.
[0432] In the context of NFV, a virtual machine QQ 340 may be a software implementation of a physical machine that runs programs as if they were executed on a physical, non-virtualized machine. Each virtual machine QQ 340 and the portion of hardware QQ 330 that executes the virtual machine (whether hardware dedicated to the virtual machine and / or hardware shared by the virtual machine with other virtual machines QQ 340) form a separate virtual network element (VNE).
[0433] Still in the context of NFV, a virtual network function (VNF) is responsible for handling specific network functions in one or more virtual machines QQ340 running on top of the hardware network infrastructure QQ330 and interacting with Fig.19 Corresponding to the application QQ320 in.
[0434] In some embodiments, one or more radio units QQ3200, each including one or more transmitters QQ3220 and one or more receivers QQ3210, may be coupled to one or more antennas QQ3225. The radio unit QQ3200 may communicate directly with the hardware node QQ330 via one or more appropriate network interfaces, and may be used in conjunction with virtual components to provide radio capabilities for a virtual node (e.g., a radio access node or base station).
[0435] In some embodiments, some signaling may be implemented using a control system QQ3230 , which may alternatively be used for communications between the hardware node QQ330 and the radio unit QQ3200 .
[0436] Fig. 20 A telecommunications network is illustrated connected to a host computer via an intermediary network in accordance with some embodiments.
[0437] refer to Fig. 20According to an embodiment, a communication system includes a telecommunication network QQ410 such as a 3GPP type cellular network, which includes an access network QQ411 such as a radio access network and a core network QQ414. The access network QQ411 includes a plurality of base stations QQ412a, QQ412b, QQ412c, such as Node Bs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area QQ413a, QQ413b, QQ413c. Each base station QQ412a, QQ412b, QQ412c may be connected to the core network QQ414 via a wired or wireless connection QQ415. A first UE QQ491 located in the coverage area QQ413c is configured to be wirelessly connected to or paged by the corresponding base station QQ412c. A second UE QQ492 in the coverage area QQ413a may be wirelessly connected to the corresponding base station QQ412a. Although multiple UEs QQ491 , QQ492 are shown in this example, the disclosed embodiments are equally applicable to the case where a single UE is in the coverage area or a single UE is connected to the corresponding base station QQ412 .
[0438] The telecommunications network QQ410 itself is connected to a host computer QQ430, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The host computer QQ430 may be under the ownership or control of a service provider, or may be operated by or on behalf of the service provider. The connections QQ421 and QQ422 between the telecommunications network QQ410 and the host computer QQ430 may extend directly from the core network QQ414 to the host computer QQ430, or may be made via an optional intermediate network QQ420. The intermediate network QQ420 may be one of a public, private, or managed network, or a combination of multiple of these networks; the intermediate network QQ420 (if any) may be a backbone network or the Internet; in particular, the intermediate network QQ420 may include two or more sub-networks (not shown).
[0439] Fig. 20The communication system as a whole implements a connection between the connected UE QQ491, QQ492 and the host computer QQ430. The connection can be described as an Over-the-Top (OTT) connection QQ450. The host computer QQ430 and the connected computer UE QQ491, QQ492 are configured to use the access network QQ411, the core network QQ414, any intermediate network QQ420 and possible other infrastructure (not shown) as intermediaries to deliver data and / or signaling via the OTT connection QQ450. The OTT connection QQ450 can be transparent in the sense that the participating communication devices through which the OTT connection QQ450 passes do not know the routes of the uplink and downlink communications. For example, the past routes of the incoming downlink communications, in which the data originating from the host computer QQ430 will be forwarded (e.g., handed over) to the connected UE QQ491, may not be notified to or need not be notified to the base station QQ412. Similarly, base station QQ412 need not be aware of the future routing of outgoing uplink communications originating from UEQQ491 towards host computer QQ430.
[0440] Fig.21 An example of a host computer communicating with a user device via a base station over a partially wireless connection is illustrated in accordance with some embodiments.
[0441] According to one embodiment, reference will now be made to Fig.21 Describe the example implementations of the UE, base station, and host computer discussed in the previous paragraphs. In the communication system QQ500, the host computer QQ510 includes hardware QQ515, which includes a communication interface QQ516 configured to establish and maintain a wired or wireless connection with different communication devices of the communication system QQ500. The host computer QQ510 also includes a processing circuit QQ518, which may have storage and / or processing capabilities. In particular, the processing circuit QQ518 may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of those (not shown) suitable for executing instructions. The host computer QQ510 also includes software QQ511, which is stored in the host computer QQ510 or can be accessed by the host computer QQ510 and can be executed by the processing circuit QQ518. The software QQ511 includes a host application QQ512. The host application QQ512 can be used to provide services to remote users, such as UE QQ530 connected via an OTT connection QQ550, which terminates at UE QQ530 and host computer QQ510. When providing services to remote users, the host application QQ512 can provide user data sent using the OTT connection QQ550.
[0442] The communication system QQ500 also includes a base station QQ520, which is provided in the telecommunication system and includes hardware QQ525, which enables the base station QQ520 to communicate with the host computer QQ510 and the user QQ530. The hardware QQ525 may include a communication interface QQ526 for establishing and maintaining a wired or wireless connection with the interface of different communication devices of the communication system QQ500, and a radio interface QQ527 for establishing and maintaining a connection with at least the base stations located in the coverage area ( Fig.21 The communication interface QQ526 may be configured to facilitate a connection QQ560 with the host computer QQ510. The connection QQ560 may be direct or may be through a core network (eg, a wireless connection QQ570) of the telecommunications system. Fig.21 ) and / or through one or more intermediate networks outside the telecommunications system. In the illustrated embodiment, the hardware QQ525 of the base station QQ520 also includes processing circuitry QQ528, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) suitable for executing instructions. The base station QQ520 also has software QQ521 stored internally or accessible via an external connection.
[0443] The communication system QQ500 also includes the UE QQ530 already mentioned. Its hardware QQ535 may include a wireless interface QQ537, which is configured to establish and maintain a wireless connection QQ570 with a base station serving the coverage area where the UE QQ530 is currently located. The hardware QQ535 of the UE QQ530 also includes a processing circuit QQ538, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) suitable for executing instructions. The UE QQ530 further includes software QQ531 stored in the UE QQ530 or accessible by the UE QQ530 and executable by the processing circuit QQ538. The software QQ531 includes a client application QQ532. The client application QQ532 may be operable to provide services to human or non-human users via the UE QQ530 with the support of the host computer QQ510. In the host computer QQ510, the executing host application QQ512 can communicate with the executing client application QQ532 via the OTT connection QQ550 terminated at the UE QQ530 and the host computer QQ510. When providing services to users, the client application QQ532 can receive request data from the host application QQ512 and provide user data in response to the request data. The OTT connection QQ550 can transmit both the request data and the user data. The client application QQ532 can interact with the user to generate the user data it provides.
[0444] Notice, Fig.21 The host computer QQ510, base station QQ520 and UE QQ530 shown can be respectively Fig. 20 The host computer QQ430, one of the base stations QQ412a, QQ412b, QQ412c and one of the UEs QQ491, QQ492 may be similar or identical. That is, the internal workings of these entities may be similar to or identical to those of the host computer QQ430, the base stations QQ412a, QQ412b, QQ412c and one of the UEs QQ491, QQ492 Fig.21 As shown, and independently, the surrounding network topology can be Fig. 20 network topology.
[0445] exist Fig.21 , OTT connection QQ550 has been abstractly drawn to illustrate communications between host computer QQ510 and UE QQ530 via base station QQ520, without explicitly referencing any intermediate devices and the precise routing of messages via those devices. The network infrastructure may determine the routing, which may be configured to hide the routing from UE QQ530 or from the service provider operating host computer QQ510, or both. When OTT connection QQ550 is active, the network infrastructure may further make decisions by which it dynamically changes the routing (e.g., based on load balancing considerations or reconfiguration of the network).
[0446] The wireless connection QQ570 between the UE QQ530 and the base station QQ520 is consistent with the teachings of the embodiments described throughout the present disclosure. One or more of the various embodiments may improve the performance of the OTT service provided to the UE QQ530 using the OTT connection QQ550, in which the wireless connection QQ570 forms the last segment. More specifically, the teachings of these embodiments may increase the random access speed and / or reduce the random access failure rate, thereby providing benefits such as faster and / or more reliable random access.
[0447] The measurement process may be provided for the purpose of monitoring the data rate, latency and other factors on which one or more embodiments are improved. There may also be an optional network function for reconfiguring the OTT connection QQ550 between the host computer QQ510 and the UE QQ530 in response to changes in the measurement results. The measurement process and / or network function for reconfiguring the OTT connection QQ550 may be implemented in the software QQ511 and hardware QQ515 of the host computer QQ510 or in the software QQ531 and hardware QQ535 of the UE QQ530 or in both. In an embodiment, a sensor (not shown) may be deployed in or associated with a communication device through which the OTT connection QQ550 passes. The sensor may participate in the measurement process by providing the values of the monitoring quantities exemplified above or providing the values of other physical quantities from which the software QQ511, QQ531 can calculate or estimate the monitoring quantities. The reconfiguration of the OTT connection QQ550 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not need to affect the base station QQ520, and it may be unknown or imperceptible to the base station QQ520. Such processes and functions are known and practiced in the art. In certain embodiments, the measurements may involve proprietary UE signaling that facilitates host computer QQ510 measurements of throughput, propagation time, latency, etc. The measurements may be implemented so that software QQ511 and QQ531 use the OTT connection QQ550 to send messages (particularly empty or "dummy" messages) while monitoring propagation time, errors, etc.
[0448] Fig. 22 A block diagram of a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments is illustrated.
[0449] Fig. 22 is a flowchart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig. 20 and Fig.21 For the sake of simplicity of this disclosure, this section only includes Fig. 22 . In step QQ610, the host computer provides user data. In sub-step QQ611 of step QQ610 (which may be optional), the host computer provides user data by executing a host application. In step QQ620, the host computer initiates a transmission carrying the user data to the UE. In step QQ630 (which may be optional), in accordance with the teachings of the embodiments described throughout the present disclosure, the base station sends the user data carried in the transmission initiated by the host computer to the UE. In step QQ640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.
[0450] Fig.23 A block diagram of a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments is illustrated.
[0451] Fig.23 is a flowchart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig. 20 and Fig.21 For the sake of simplicity of this disclosure, this section only includes Fig.23 . In step QQ710 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In step QQ720, the host computer initiates a transmission carrying the user data to the UE. According to the teachings of the embodiments described throughout the present disclosure, the transmission can be delivered via a base station. In step QQ730 (which may be optional), the UE receives the user data carried in the transmission.
[0452] Fig.24 A block diagram of a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments is illustrated.
[0453] Fig.24 is a flowchart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig. 20 and Fig.21 For the sake of simplicity of this disclosure, this section only includes Fig.24 . In step QQ810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step QQ820, the UE provides user data. In sub-step QQ821 of step QQ820 (which may be optional), the UE provides user data by executing a client application. In sub-step QQ811 of step QQ810 (which may be optional), the UE executes a client application that provides user data in response to received input data provided by the host computer. When providing user data, the executed client application may further consider user input received from the user. Regardless of the specific manner of providing user data, in sub-step QQ830 (which may be optional), the UE initiates transmission of user data to the host computer. In step QQ840 of the method, in accordance with the teachings of the embodiments described throughout the present disclosure, the host computer receives user data sent from the UE.
[0454] Fig.25A block diagram of a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments is illustrated.
[0455] Fig.25 is a flowchart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig. 20 and Fig.21 For the sake of simplicity of this disclosure, only the host computer, base station and UE described in this section are included. Fig.25 In step QQ910 (which may be optional), the base station receives user data from the UE in accordance with the teachings of the embodiments described throughout the present disclosure. In step QQ920 (which may be optional), the base station initiates a transmission of the received user data to the host computer. In step QQ930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.
[0456] Any appropriate steps, methods, features, functions or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include multiple such functional units. These functional units may be implemented by a processing circuit, which may include one or more microprocessors or microcontrollers, and other digital hardware, which may include a digital signal processor (DSP), dedicated digital logic, etc. The processing circuit may be configured to execute program codes stored in a memory, which may include one or more types of memory, such as a read-only memory (ROM), a random access memory (RAM), a cache memory, a flash memory device, an optical storage device, etc. The program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more technologies described herein. In some embodiments, the processing circuit may be used to cause the corresponding functional unit to perform the corresponding functions according to one or more embodiments of the present disclosure.
[0457] The term "unit" may have a conventional meaning in the field of electronic components, electrical devices and / or electronic devices and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logical solid-state and / or discrete devices, computer programs or instructions for performing corresponding tasks, processes, calculations, output and / or display functions, etc., such as those described herein.
[0458] At least some of the following abbreviations may be used in the present disclosure. If there is an inconsistency between abbreviations, the above usage shall take precedence. If listed multiple times below, the first listing shall take precedence over any subsequent listings.
[0459] 1x RTT CDMA2000 1x Radio Transmission Technology
[0460] 3GPP Third Generation Partnership Project
[0461] 5G Fifth Generation
[0462] ABS Almost Blank Subframe
[0463] ARQ Automatic Repeat Request
[0464] AWGN Additive White Gaussian Noise
[0465] BCCH Broadcast Control Channel
[0466] BCH Broadcast Channel
[0467] CA Carrier Aggregation
[0468] CC Carrier Component
[0469] CCCH SDU Common Control Channel SDU
[0470] CDMA Code Division Multiple Access
[0471] CGI Cell Global Identifier
[0472] CIR Channel Impulse Response
[0473] CP Cyclic Prefix
[0474] CPICH Common Pilot Channel
[0475] CPICH Ec / No CPICH received energy per chip divided by the power density in the frequency band
[0476] CQI Channel Quality Information
[0477] C-RNTI Cell RNTI
[0478] CSI Channel State Information
[0479] DCCH Dedicated Control Channel
[0480] DL Downlink
[0481] DM Demodulation
[0482] DMRS Demodulation Reference Signal
[0483] DRX Discontinuous Reception
[0484] DTX Discontinuous Transmission
[0485] DTCH Dedicated Traffic Channel
[0486] DUT Device Under Test
[0487] E-CID Enhanced Cell-ID (positioning method)
[0488] E-SMLC Evolved Service Mobile Location Center
[0489] ECGI Evolved CGI
[0490] eNB E-UTRAN Node B
[0491] ePDCCH Enhanced Physical Downlink Control Channel
[0492] E-SMLC Evolved Service Mobile Location Center
[0493] E-UTRA Evolved UTRA
[0494] E-UTRAN Evolved UTRAN
[0495] FDD Frequency Division Duplex
[0496] FFS needs further research
[0497] GERAN GSM EDGE Radio Access Network
[0498] Base stations in gNB NR
[0499] GNSS Global Navigation Satellite System
[0500] GSM Global System for Mobile Communications
[0501] HARQ Hybrid Automatic Repeat Request
[0502] HO Handover
[0503] HSPA High Speed Packet Access
[0504] HRPD High Rate Packet Data
[0505] LOS Line of Sight
[0506] LPP LTE Positioning Protocol
[0507] LTE Long Term Evolution
[0508] MAC Media Access Control
[0509] MBMS Multimedia Broadcast Multicast Service
[0510] MBSFN Multimedia Broadcast Multicast Service Single Frequency Network
[0511] MBSFN ABS MBSFN Almost Blank Subframe
[0512] MDT Minimized Drive Test
[0513] MIB Master Information Block
[0514] MME Mobility Management Entity
[0515] MSC Mobile Switching Center
[0516] NPDCCH Narrowband Physical Downlink Control Channel
[0517] NR New Radio
[0518] OCNG OFDMA Channel Noise Generator
[0519] OFDM Orthogonal Frequency Division Multiplexing
[0520] OFDMA Orthogonal Frequency Division Multiple Access
[0521] OSS Operation Support System
[0522] OTDOA Observed Time Difference of Arrival
[0523] O&M Operation and Maintenance
[0524] PBCH Physical Broadcast Channel
[0525] P-CCPCH Primary Common Control Physical Channel
[0526] PCell Primary Cell
[0527] PCFICH Physical Control Format Indicator Channel
[0528] PDCCH Physical Downlink Control Channel
[0529] PDP Power Delay Profile
[0530] PDSCH Physical Downlink Shared Channel
[0531] PGW Packet Gateway
[0532] PHICH Physical Hybrid Automatic Repeat Request Indicator Channel
[0533] PLMN Public Land Mobile Network
[0534] PMI precoder matrix indication
[0535] PRACH Physical Random Access Channel
[0536] PRS Positioning Reference Signal
[0537] PSS Primary Synchronization Signal
[0538] PUCCH Physical Uplink Control Channel
[0539] PUSCH Physical Uplink Shared Channel
[0540] RACH Random Access Channel
[0541] QAM Quadrature Amplitude Modulation
[0542] RAN Radio Access Network
[0543] RAT Radio Access Technology
[0544] RLM Radio Link Management
[0545] RNC Radio Network Controller
[0546] RNTI Radio Network Temporary Identifier
[0547] RRC Radio Resource Control
[0548] RRM Radio Resource Management
[0549] RS reference signal
[0550] RSCP Received Signal Code Power
[0551] RSRP Reference symbol received power, or reference signal received power
[0552] RSRQ Reference signal reception quality, or reference symbol reception quality
[0553] RSSI Received Signal Strength Indicator
[0554] RSTD Reference Signal Time Difference
[0555] SCH Synchronization Channel
[0556] SCell Secondary Cell
[0557] SDU Service Data Unit
[0558] SFN System Frame Number
[0559] SGW Service Gateway
[0560] SI System Information
[0561] SIB System Information Block
[0562] SNR Signal to Noise Ratio
[0563] SON Self-Optimizing Network
[0564] SS Sync Signal
[0565] SSS Secondary synchronization signal
[0566] TDD Time Division Duplex
[0567] TDOA Time Difference of Arrival
[0568] TOA Time of Arrival
[0569] TSS three-level synchronization signal
[0570] TTI Transmission Time Interval
[0571] UE User Equipment
[0572] UL Uplink
[0573] UMTS Universal Mobile Telecommunications System
[0574] USIM Universal Subscriber Identity Module
[0575] UTDOA Uplink Time Difference of Arrival
[0576] UTRA Universal Terrestrial Radio Access
[0577] UTRAN Universal Terrestrial Radio Access Network
[0578] WCDMA Wide CDMA
[0579] WLAN Wide Area Network
[0580] Additional definitions and embodiments are discussed below.
[0581] In the above description of various embodiments of the inventive concept, it should be understood that the terms used herein are only used for the purpose of describing specific embodiments and are not intended to limit the inventive concept. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as those commonly understood by those of ordinary skill in the art to which the inventive concept belongs. It should also be understood that terms (such as those defined in commonly used dictionaries) should be interpreted as having a meaning consistent with their meaning in the context of this specification and related fields, and will not be idealized or overly formally interpreted unless explicitly defined as such herein.
[0582] When an element is referred to as being "connected", "coupled", "responsive" or its variants to another element, it may be directly connected, coupled or responsive to another element, or there may be an intermediate element. In contrast, when an element is referred to as being "directly connected", "directly coupled", "directly responsive" or its variants to another element, there is no intermediate element. The same number always refers to the same element. In addition, "coupling", "connection", "responsiveness" or its variants used herein may include wireless coupling, connection or response. As used herein, the singular forms of "one", "an" and "the" are also intended to include plural forms unless the context clearly indicates otherwise. For the sake of brevity and / or clarity, well-known functions or configurations may not be described in detail. The term "and / or" includes any and all combinations of one or more related listed items.
[0583] It will be understood that, although the terms first, second, third, etc. can be used to describe various elements / operations in this article, these elements / operations should not be limited by these terms. These terms are only used to distinguish one element / operation from another element / operation. Therefore, without departing from the teaching of the present invention, the first element / operation in some embodiments can be referred to as the second element / operation in other embodiments. Throughout the specification, the same reference numerals or the same reference numerals represent the same or similar elements.
[0584] As used herein, the terms "comprise / comprising / comprises", "include / including / includes", "have / has / having" or variations thereof are open ended and include one or more stated features, integers, elements, steps, components or functions, but do not preclude the presence or addition of one or more other features, integers, elements, steps, components, functions or groups thereof. In addition, as used herein, the commonly used abbreviation "eg," derived from the Latin phrase "exempli gratia," may be used to introduce or specify one or more general examples of previously mentioned items and is not intended to limit such items. The commonly used abbreviation "ie," derived from the Latin phrase "id est," may be used to specifically specify a particular item from a more general statement.
[0585] Example embodiments are described herein with reference to block diagrams and / or flowchart illustrations of computer-implemented methods, apparatus (systems and / or devices), and / or computer program products. It should be understood that the blocks of the block diagrams and / or flowchart illustrations, and the combination of blocks in the block diagrams and / or flowchart illustrations, can be implemented by computer program instructions executed by one or more computer circuits. These computer program instructions can be provided to processor circuits of general-purpose computer circuits, special-purpose computer circuits, and / or other programmable data processing circuits to produce machines, so that instructions executed by processors of computers and / or other programmable data processing devices convert and control transistors, values stored in memory locations, and other hardware components in such circuits to implement the functions / actions specified in the block diagrams and / or flowchart boxes, thereby creating means (functions) and / or structures for implementing the functions / actions specified in the block diagrams and / or flowchart boxes.
[0586] These computer program instructions may also be stored in a tangible computer-readable medium that can direct a computer or other programmable data processing device to operate in a specific manner so that the instructions stored in the computer-readable medium produce an article of manufacture including instructions for implementing the functions / actions specified in the block diagram and / or flowchart block. Therefore, embodiments of the present invention may be embodied as hardware and / or software (including firmware, resident software, microcode, etc.) running on a processor such as a digital signal processor, which may be collectively referred to as "circuit", "module" or variations thereof.
[0587] It should also be noted that in some alternative implementations, the function / action noted in the frame may not occur in the order noted in the flow chart. For example, according to the function / action involved, the two frames shown in succession can actually be performed substantially simultaneously, or the frame can sometimes be performed in the opposite order. In addition, the function of a given frame of a flow chart and / or a block diagram can be divided into a plurality of frames, and / or the function of two or more frames of a flow chart and / or a block diagram can be integrated at least in part. Finally, without departing from the scope of the present invention, other frames can be added / inserted between the frames shown, and / or the frame / operation can be omitted. In addition, although some figures include arrows on the communication path to show the main direction of communication, it should be understood that communication can occur in the direction opposite to the arrows depicted.
[0588] In the case of not departing substantially from the principles of the inventive concept, many changes and modifications may be made to the embodiments. All of these changes and modifications are intended to be included within the scope of the inventive concept. Therefore, the above disclosed subject matter is considered to be illustrative rather than restrictive, and the examples of the embodiments are intended to cover all such modifications, enhancements, and other embodiments that fall within the spirit and scope of the inventive concept. Therefore, to the maximum extent permitted by law, the scope of the inventive concept will be determined by the broadest permissible interpretation of the present disclosure including examples of the embodiments and their equivalents, and should not be constrained or limited by the foregoing detailed description.
Claims
1. A method of operating a wireless device (300), the wireless device (300) providing communications with a wireless network, the method comprising: Registering with a first PLMN having a first public land mobile network PLMN identity (1501); performing (1505) a first plurality of random access, RA, procedures when registering with the first PLMN; storing (1509) in a memory (305) first information related to the first plurality of RA procedures, the first plurality of RA procedures being associated with the first PLMN having the first PLMN identity; After registering with the first PLMN and after performing the first plurality of RA procedures, registering (1511) with a second PLMN, the second PLMN having a second PLMN identity different from the first PLMN identity; In response to registering with the second PLMN, discarding (1513) the first information from the memory; performing (1515) a second plurality of RA procedures when registering with the second PLMN; storing (1519) in the memory (305) second information related to the second plurality of RA procedures, the second plurality of RA procedures being associated with the second PLMN having the second PLMN identity; as well as An information message is sent (1525) to the second PLMN, wherein the information message includes a plurality of RACH reports corresponding to the second plurality of RA procedures associated with the second PLMN identity based on the second information.
2. The method according to claim 1, wherein: Sending the information message includes sending the information message to the second PLMN after performing the second plurality of RA procedures, wherein the information message includes a plurality of RACH reports corresponding to the second plurality of RA procedures associated with the second PLMN identity based on the second information.
3. The method according to claim 1 or 2, wherein: For each RA procedure in the first plurality of RA procedures, the first information includes the first PLMN identity, and wherein for each RA procedure in the second plurality of RA procedures, the second information includes the second PLMN identity.
4. The method according to claim 3, wherein: Each RACH report of the plurality of RACH reports corresponding to the second plurality of RA procedures includes the second PLMN identity.
5. The method according to claim 1 or 2, wherein: For each RA process in the first plurality of RA processes, the first information comprises an indication of a number of random access channel, RACH, preamble codes sent for the corresponding RA process, wherein for each RA process in the second plurality of RA processes, the second information comprises an indication of a number of RACH preamble codes sent for the corresponding RA process, and wherein each RACH report in the plurality of RACH reports comprises an indication of a number of RACH preamble codes sent for the second plurality of RA processes.
6. The method according to claim 4, wherein: For each RA process in the first plurality of RA processes, the first information comprises an indication of a number of random access channel, RACH, preamble codes sent for the corresponding RA process, wherein for each RA process in the second plurality of RA processes, the second information comprises an indication of a number of RACH preamble codes sent for the corresponding RA process, and wherein each RACH report in the plurality of RACH reports comprises an indication of a number of RACH preamble codes sent for the second plurality of RA processes.
7. The method according to claim 1 or 2, wherein: For each RA process of the first plurality of RA processes, the first information includes a contention detection flag indicating whether contention resolution is unsuccessful for at least one RACH preamble code sent for the corresponding RA process, wherein for each RA process of the second plurality of RA processes, the second information includes a contention detection flag indicating whether contention resolution is unsuccessful for at least one RACH preamble code sent for the corresponding RA process, and wherein each RACH report of the plurality of RACH reports includes the contention detection flag for a corresponding one RA process of the second plurality of RA processes.
8. A wireless device (300), comprising: processing circuit (303); and a memory (305) coupled to the processing circuit, wherein the memory includes instructions that, when executed by the processing circuit, cause the wireless device to: Registering with a first PLMN having a first public land mobile network PLMN identity; performing a first plurality of random access, RA, procedures when registering with the first PLMN; storing in the memory (305) first information related to the first plurality of RA procedures, the first plurality of RA procedures being associated with the first PLMN having the first PLMN identity; After registering with the first PLMN and after performing the first plurality of RA procedures, registering with a second PLMN, the second PLMN having a second PLMN identity different from the first PLMN identity; in response to registering with the second PLMN, discarding the first information from the memory; performing a second plurality of RA procedures when registering with the second PLMN; storing in the memory (305) second information related to the second plurality of RA procedures, the second plurality of RA procedures being associated with the second PLMN having the second PLMN identity; as well as An information message is sent to the second PLMN, wherein the information message includes a plurality of RACH reports corresponding to the second plurality of RA procedures associated with the second PLMN identity based on the second information.
9. The wireless device (300) of claim 8, wherein: Sending the information message includes sending the information message to the second PLMN after performing the second plurality of RA procedures, wherein the information message includes a plurality of RACH reports corresponding to the second plurality of RA procedures associated with the second PLMN identity based on the second information.
10. The wireless device (300) according to claim 8 or 9, wherein: For each RA procedure in the first plurality of RA procedures, the first information includes the first PLMN identity, and wherein for each RA procedure in the second plurality of RA procedures, the second information includes the second PLMN identity.
11. The wireless device (300) of claim 10, wherein: Each RACH report of the plurality of RACH reports corresponding to the second plurality of RA procedures includes the second PLMN identity.
12. The wireless device (300) according to claim 8 or 9, wherein: For each RA process in the first plurality of RA processes, the first information comprises an indication of a number of random access channel, RACH, preamble codes sent for the corresponding RA process, wherein for each RA process in the second plurality of RA processes, the second information comprises an indication of a number of RACH preamble codes sent for the corresponding RA process, and wherein each RACH report in the plurality of RACH reports comprises an indication of a number of RACH preamble codes sent for the second plurality of RA processes.
13. The wireless device (300) of claim 11, wherein: For each RA process in the first plurality of RA processes, the first information comprises an indication of a number of random access channel, RACH, preamble codes sent for the corresponding RA process, wherein for each RA process in the second plurality of RA processes, the second information comprises an indication of a number of RACH preamble codes sent for the corresponding RA process, and wherein each RACH report in the plurality of RACH reports comprises an indication of a number of RACH preamble codes sent for the second plurality of RA processes.
14. The wireless device (300) according to claim 8 or 9, wherein: For each RA process of the first plurality of RA processes, the first information includes a contention detection flag indicating whether contention resolution is unsuccessful for at least one RACH preamble code sent for the corresponding RA process, wherein for each RA process of the second plurality of RA processes, the second information includes a contention detection flag indicating whether contention resolution is unsuccessful for at least one RACH preamble code sent for the corresponding RA process, and wherein each RACH report of the plurality of RACH reports includes the contention detection flag for a corresponding one RA process of the second plurality of RA processes.
15. A computer program product comprising a non-transitory storage medium, the non-transitory storage medium comprising program code to be executed by a processing circuit (303) of a wireless device (300), whereby execution of the program code causes the wireless device (300): Registering with a first PLMN having a first public land mobile network PLMN identity; performing a first plurality of random access, RA, procedures when registering with the first PLMN; storing, in a memory (305), first information related to the first plurality of RA procedures, the first plurality of RA procedures being associated with the first PLMN having the first PLMN identity; After registering with the first PLMN and after performing the first plurality of RA procedures, registering with a second PLMN, the second PLMN having a second PLMN identity different from the first PLMN identity; in response to registering with the second PLMN, discarding the first information from the memory; performing a second plurality of RA procedures when registering with the second PLMN; storing in the memory (305) second information related to the second plurality of RA procedures, the second plurality of RA procedures being associated with the second PLMN having the second PLMN identity; as well as An information message is sent to the second PLMN, wherein the information message includes a plurality of RACH reports corresponding to the second plurality of RA procedures associated with the second PLMN identity based on the second information.
16. The computer program product of claim 15, whereby execution of the program code further causes the wireless device to perform the method of any one of claims 2 to 7.
