Method and apparatus for UE assumptions for CGI reading in NR

Abstract

Provided are a method and apparatus for a UE to determine a cell global identity (CGI) of a target cell.

Description

Technical Field

[0001] The present application relates generally to wireless communication systems, and more particularly to determining a cell global identity of a target cell. Background Art

[0002] Wireless mobile communication technologies use various standards and protocols to transmit data between base stations and wireless mobile devices. Wireless communication system standards and protocols may include the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE); the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, which is commonly referred to by industry organizations as Worldwide Interoperability for Microwave Access (WiMAX); and the IEEE 802.11 standard for wireless local area networks (WLANs), which is commonly referred to by industry organizations as Wi-Fi. In the 3GPP radio access network (RAN) in an LTE system, a base station may include a RAN node such as an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly referred to as an evolved Node B, enhanced Node B, eNodeB, or eNB) and / or a radio network controller (RNC) in the E-UTRAN, which communicates with wireless communication devices called user equipment (UE). In the fifth generation (5G) wireless RAN, the RAN node may include a 5G node, a new radio (NR) node, or a gNodeB (gNB).

[0003] The RAN uses radio access technologies (RATs) to facilitate communication between RAN nodes and UEs. The RAN may include Global System for Mobile Communications (GSM), Enhanced Data for GSM Evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), and / or E-UTRAN, which provide access to communication services through the core network. Each RAN operates according to a specific 3GPP RAT. For example, GERAN implements GSM and / or EDGE RATs, UTRAN implements Universal Mobile Telecommunications System (UMTS) RATs or other 3GPP RATs, and E-UTRAN implements LTE RATs. Summary of the Invention

[0004] In one aspect, the present disclosure provides a method for a user equipment (UE) to identify a cell global identifier (CGI) of a target cell, comprising: determining that the synchronization signal block (SSB) measurement timing configuration (SMTC) periodicity of the target cell has been configured by a serving cell; decoding a master information block (MIB), wherein the MIB includes multiplexing mode information; based on decoding the MIB, identifying whether the SSB and control resource set (CORESET) multiplexing mode is mode 1, mode 2, or mode 3; based on identifying that the SSB and CORESET multiplexing mode is mode 2 or mode 3, periodically reading the system information block type 1 (SIB1) using the SMTC of the target cell; and obtaining the CGI of the target cell in the SIB1.

[0005] In one aspect, the present disclosure provides a method for a user equipment (UE) to identify a cell global identifier (CGI) of a target cell, comprising: determining that a synchronization signal block (SSB) measurement timing configuration (SMTC) periodicity of the target cell has been configured by a serving cell; decoding a master information block (MIB), wherein the MIB includes multiplexing mode information, and wherein the decoding obtains the MIB repetition periodicity; based on decoding the MIB, identifying whether the SSB and control resource set (CORESET) multiplexing mode is mode 1, mode 2, or mode 3; based on identifying that the SSB and CORESET multiplexing mode is mode 2 or mode 3, using the MIB repetition periodicity to read the system information block type 1 (SIB1); and obtaining the CGI of the target cell in the SIB1.

[0006] In one aspect, the present disclosure provides a method for a user equipment (UE) to identify a cell global identifier (CGI) of a target cell, including: determining that the synchronization signal block (SSB) measurement timing configuration (SMTC) periodicity of the target cell has not been configured by a serving cell; decoding a master information block (MIB), wherein the MIB includes multiplexing mode information; based on decoding the MIB, identifying whether the SSB and control resource set (CORESET) multiplexing mode is mode 1, mode 2, or mode 3; based on identifying that the SSB and CORESET multiplexing mode is mode 2 or mode 3, reading a system information block type 1 (SIB1) using a 20 millisecond repetition period; and obtaining the CGI of the target cell in the SIB1.

[0007] In one aspect, the present disclosure provides a method for a user equipment (UE) to identify a cell global identifier (CGI) of a target cell, comprising: determining that the synchronization signal block (SSB) measurement timing configuration (SMTC) periodicity of the target cell has not been configured by a serving cell; decoding a master information block (MIB), wherein the MIB includes multiplexing mode information; based on decoding the MIB, identifying whether the SSB and control resource set (CORESET) multiplexing mode is mode 1, mode 2, or mode 3; based on identifying that the SSB and CORESET multiplexing mode is mode 2 or mode 3, reading a system information block type 1 (SIB1) using a 5 millisecond repetition period; and obtaining the CGI of the target cell in the SIB1.

[0008] In one aspect, the present disclosure provides a method for a user equipment (UE) to identify a cell global identifier (CGI) of a target cell, comprising: determining that the synchronization signal block (SSB) measurement timing configuration (SMTC) periodicity of the target cell has not been configured by a serving cell; decoding a master information block (MIB) using a MIB repetition period, wherein the MIB includes multiplexing mode information; based on decoding the MIB, identifying whether the SSB and control resource set (CORESET) multiplexing mode is mode 1, mode 2, or mode 3; based on identifying that the SSB and CORESET multiplexing mode is mode 2 or mode 3, reading a system information block type 1 (SIB1) using the MIB repetition period; and obtaining the CGI of the target cell in the SIB1.

[0009] In one aspect, the present disclosure provides an electronic device, the device comprising means for executing the above method.

[0010] In one aspect, the present disclosure provides a computer-readable medium comprising instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform the above method.

[0011] In one aspect, the present disclosure provides an electronic device comprising logic components, modules or circuits for executing the above method. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] To easily identify the discussion of any particular element or act, the most significant digit(s) in a reference number refers to the drawing number that first introduces the element.

[0013] Figure 1 A method according to one embodiment is shown.

[0014] Figure 2 A method according to one embodiment is shown.

[0015] Figure 3A method according to one embodiment is shown.

[0016] Figure 4 A method according to one embodiment is shown.

[0017] Figure 5 A method according to one embodiment is shown.

[0018] Figure 6 A method according to one embodiment is shown.

[0019] Figure 7 An example of a service-based architecture according to certain embodiments is shown.

[0020] Figure 8 A UE according to one embodiment is shown.

[0021] Figure 9 A network node according to one embodiment is shown. DETAILED DESCRIPTION

[0022] In NR, the UE decodes both the MIB and SIB1 to read the CGI (Cell Global Identity). The CGI information is carried in the IE "CellIdentity" in the IE "PLMN-IdentityInfoList" in the IE "CellAccessRelatedInfo" in SIB1, which can be found in 3GPP TS 38.331 (shown below).

[0023]

[0024] To read the MIB and SIB1, the UE needs to understand the periodicity and time offset of those MIBs and SIB1s for the target cell. The MIB is carried on the PBCH of the SSB. In some systems, for example, the MIB is always transmitted on the PBCH with an 80ms periodicity and repeated every 80ms (the repetition is the same as for the SSB). The MIB includes the parameters required to obtain the SIB1 from the cell.

[0025] However, depending on different conditions, the current SIB1 reading may have some limitations. For example, SIB1 is transmitted on the DL-SCH with a periodicity of 160ms, and the transmission repetition periodicity within 160ms is variable, as configured in the signaling pdcch-ConfigSIB1 in the MIB. The default transmission repetition periodicity of SIB1 is 20ms, but the actual transmission repetition periodicity depends on the specific network implementation. For SSB and CORESET multiplexing mode 1, the SIB1 repetition transmission period is 20ms. For SSB and CORESET multiplexing mode 2 / 3 (mode 2 or mode 3), the SIB1 transmission repetition period is the same as the SSB period.

[0026] Figure 1 FIG. 1 is a flow chart of an example method 100 for determining the CGI of a target cell in SIB1. Figure 1 As shown, if the SSB and CORESET reuse mode is mode 2 / 3 (2 or 3), the SIB1 transmission repetition period is the same as the SSB period. However, the SSB period information is also carried in SIB1 for the target cell.

[0027] The IE "ServingCellConfigCommonSIB" in SIB1 includes a parameter named "ssb-PeriodicityServingCell", and "ssb-PeriodicityServingCell" indicates the SSB period / periodicity for the cell.

[0028] If the UE uses the SSB period to decode the SIB1, the UE must first know the SSB period of the target cell, which means that the UE must decode the SIB1 of the target cell before. Therefore, the CGI reading assumption is a deadlock for the UE specific implementation.

[0029] Therefore, it may be useful to carefully design UE behavior and assumptions to avoid ambiguity.

[0030] Target cell CGI reading with SMT configuration

[0031] Figure 2 2 is a flow chart of a method 200 for target cell CGI reading with SMTC configuration according to one embodiment. Prior to CGI reading for a target cell, if the serving cell configures SMTC to the UE for detection / measurement of the target cell, the SIB1 repetition transmission period remains at 20 ms for SSB and CORESET reuse mode 1. However, for SSB and CORESET reuse modes 2 / 3, the SIB1 transmission repetition period may be assumed to be the same as the SMTC periodicity for the UE's specific implementation.

[0032] The UE may keep decoding SIB1 for the target cell only within the SMTC duration window.

[0033] The UE periodically disconnects from its serving cell according to the SMTC. The disconnection occurs on both the DL channel to the UE's serving cell and the UL channel from the UE to the serving cell.

[0034] Figure 3 3 is a flow chart of a method 300 for target cell CGI reading with SMTC configuration according to another embodiment. Prior to CGI reading for a target cell, if the serving cell configures SMTC to the UE for detection / measurement of the target cell, the SIB1 repetition transmission period remains at 20 milliseconds for SSB and CORESET reuse mode 1. However, for SSB and CORESET reuse modes 2 / 3, the SIB1 transmission repetition period may be assumed to be the same as the MIB repetition periodicity identified by the UE.

[0035] The UE may use the SMTC for PBCH decoding to read the MIB. However, if the UE identifies more SSB opportunities outside the SMTC window, the UE may also use those SSB opportunities to read the MIB.

[0036] The UE uses the identified MIB repetition periodicity to assume the SIB1 repetition periodicity.

[0037] Target cell CGI reading without SMTC configuration

[0038] Figure 4 4 is a flow chart of a method 400 for target cell CGI reading without SMTC configuration according to one embodiment. Prior to CGI reading for a target cell, if the serving cell does not configure an SMTC for the UE for detection / measurement of the target cell, the SIB1 repetition period may remain at 20 ms for SSB and CORESET reuse mode 1. For SSB and CORESET reuse modes 2 / 3, the SIB1 transmission repetition period may also be assumed to be 20 ms.

[0039] The UE reads the SIB1 for the target cell using a 20 ms repetition periodicity (same as for the initial access case).

[0040] The UE may use 5 ms or 20 ms as the repetition periodicity to read the MIB.

[0041] Figure 55 is a flow chart of a method 500 for target cell CGI reading without SMTC configuration according to another embodiment. Prior to CGI reading for a target cell, if the serving cell does not configure an SMTC for the UE for detection / measurement of the target cell, the SIB1 repetition period remains at 20 ms for SSB and CORESET reuse mode 1. For SSB and CORESET reuse modes 2 / 3, the SIB1 transmission repetition period may be assumed to be 5 ms.

[0042] The UE uses 5 ms as the default periodicity for target cell measurement and detection.

[0043] The UE uses 5 ms, the same as the cell detection / measurement used for target cell SIB1 reading.

[0044] The UE may use 5 ms or 20 ms as the repetition periodicity to read the MIB.

[0045] Figure 6 6 is a flow chart of a method 600 for target cell CGI reading without SMTC configuration according to yet another embodiment. Prior to CGI reading for a target cell, if the serving cell does not configure an SMTC for the UE for detection / measurement of the target cell, the SIB1 repetition transmission period remains at 20 ms for SSB and CORESET reuse mode 1. For SSB and CORESET reuse modes 2 / 3, the SIB1 transmission repetition period may be assumed to be the same as the MIB repetition periodicity identified by the UE.

[0046] The UE uses 5 ms as the default periodicity for target cell measurement and detection.

[0047] The UE may use 5 ms or 20 ms as the repetition periodicity to read the MIB.

[0048] The UE assumes that the SIB1 repetition periodicity is the same as the MIB repetition periodicity.

[0049] Exemplary system architecture

[0050] In certain embodiments, the 5G system architecture supports data connectivity and services, enabling deployment using technologies such as network function virtualization and software-defined networking. The 5G system architecture can utilize service-based interactions between control plane network functions. Separating user plane functions from control plane functions allows independent scalability, evolution, and flexible deployment (e.g., centralized location or distributed (remote) location). Modular function design allows functional reuse and enables flexible and efficient network slicing. A network function and its network function service can interact with another NF and its network function service directly or indirectly via a service communication agent. Another intermediate function can help route control plane messages. The architecture minimizes the dependency between AN and CN. The architecture may include an aggregated core network with a public AN-CN interface that integrates different access types (e.g., 3GPP access and non-3GPP access). The architecture may also support a unified authentication framework, stateless NFs with decoupling of compute and storage resources, capability exposure, concurrent access to local and centralized services (to support low-latency services and access to local data networks, user plane functions may be deployed near the AN), and / or roaming in the visited PLMN with both home-routed traffic as well as local breakout traffic.

[0051] The 5G architecture can be defined as service-based, and the interactions between network functions can include service-based representations, where a network function within the control plane (e.g., AMF) enables other authorized network functions to access its services. The service-based representation can also include point-to-point reference points. The reference point representation can also be used to show the interactions between NF services in network functions described by a point-to-point reference point (e.g., N11) between any two network functions (e.g., AMF and SMF).

[0052] Figure 7 FIG7 shows a service-based architecture 700 in 5GS according to one embodiment. As described in 3GPP TS 23.501, the service-based architecture 700 includes NFs such as NSSF 702, NEF 704, NRF 706, PCF 708, UDM 710, AUSF 712, AMF 714, and SMF 716 for communicating with UE 720, (R)AN 722, UPF 724, and DN 726. NFs and NF services can communicate directly (referred to as direct communication) or indirectly via SCP 718 (referred to as indirect communication). Figure 7 Also shown are the corresponding service-based interfaces including Nutm, Naf, Nudm, Npcf, Nsmf, Nnrf, Namf, Nnef, Nnssf and Nausf and reference points N1, N2, N3, N4 and N6. Figure 7 Some example functions provided by the NF are shown.

[0053] The NSSF 702 supports functions such as: selecting a set of network slice instances to serve the UE; determining the allowed NSSAIs and, if required, the mapping to the subscribed S-NSSAIs; determining the configured NSSAIs and, if required, the mapping to the subscribed S-NSSAIs; and / or determining the set of AMFs to be used to serve the UE, or a list of candidate AMFs, possibly by querying the NRF based on the configuration.

[0054] NEF 704 supports the exposure of capabilities and events. NF capabilities and events can be securely exposed by NEF 704 (e.g., for 3rd parties, application functions and / or edge computing). NEF 704 can store / retrieve information as structured data using a standardized interface to UDR (Nudr). NEF 704 can also securely provide information from external applications to the 3GPP network, and can provide application functions to securely provide information (e.g., expected UE behavior, 5GLAN group information, and service-specific information) to the 3GPP network, where NEF 704 can authenticate and authorize and help limit application functions. NEF 704 can provide internal-external information conversion by converting between information exchanged with AF and information exchanged with internal network functions. For example, NEF 704 converts between AF service identifiers and internal 5G core information (such as DNN and S-NSSAI). NEF 704 can handle the masking of network and user sensitive information of external AF according to network policy. NEF 704 can receive information from other network functions (based on the exposed capabilities of other network functions) and store the received information as structured data using a standardized interface to the UDR. The stored information can then be accessed by NEF 704 and re-exposed to other network functions and application functions, and used for other purposes such as analysis. For external exposure of services related to a specific UE, NEF 704 can reside in the HPLMN. Depending on the operator agreement, the NEF 704 in the HPLMN may have an interface with the NF in the VPLMN. When the UE can switch between the EPC and 5GC, the SCEF+NEF can be used for service exposure.

[0055] The NRF 706 supports service discovery functionality by receiving NF discovery requests from NF instances or SCPs and providing information about the discovered NF instances to the NF instances or SCPs. The NRF 706 may also support P-CSCF discovery (a special case of SMF discovery of AFs), maintain NF profiles of available NF instances and their supported services, and / or notify subscribed NF service consumers or SCPs of newly registered / updated / deregistered NF instances along with their NF services. In the context of network slicing, based on network specific implementation, multiple NRFs may be deployed at different levels, such as PLMN level (NRF configured with information about the entire PLMN), shared slice level (NRF configured with information belonging to a network slice set), and / or slice-specific level (NRF configured with information belonging to the S-NSSAI). In the context of roaming, multiple NRFs may be deployed in different networks, where the NRF in the visited PLMN (called vNRF) is configured with information about the visited PLMN, and where the NRF in the home PLMN (called hNRF) is configured with information about the home PLMN, referenced by the vNRF via the N27 interface.

[0056] The PCF 708 supports a unified policy framework to govern network behavior. The PCF 708 provides policy rules for control plane functions to enforce them. The PCF 708 accesses subscription information related to policy decisions in the Unified Data Repository (UDR). The PCF 708 can access the UDR located in the same PLMN as the PCF.

[0057] The UDM 710 supports the generation of 3GPP AKA authentication credentials, user identification processing (e.g., storage and management of the SUPI for each subscriber in the 5G system), unhiding of the privacy-preserving subscription identifier (SUCI), access authorization based on subscription data (e.g., roaming restrictions), UE registration with the serving NF (e.g., storing the service AMF for the UE and storing the service SMF for the UE's PDU session), service / session continuity (e.g., by maintaining SMF / DNN allocation for ongoing sessions), MT-SMS delivery, lawful intercept functionality (particularly in outbound roaming scenarios where the UDM is the sole point of contact for the LI), subscription management, SMS management, 5G LAN group management processing, and / or external parameter configuration (expected UE behavior parameters or network configuration parameters). To provide such functionality, the UDM 710 uses subscription data (including authentication data) that may be stored in the UDR. In this case, the UDM implements the application logic and may not require internal user data storage, and several different UDMs may serve the same user in different transactions. The UDM 710 may be located in the HPLMN of the subscriber it serves and may access information from UDRs located in the same PLMN.

[0058] AF 728 interacts with the core network to provide services such as supporting application impact on traffic routing; access to NEF 704; interaction with the policy framework for policy control; and / or IMS interaction with 5GC. Based on operator deployment, application functions deemed trusted by the operator may be allowed to interact directly with relevant network functions. Application functions that are not permitted direct access by the operator may interact with relevant network functions using an external exposure framework via NEF 704.

[0059] The AUSF 712 supports authentication for 3GPP access and untrusted non-3GPP access. The AUSF 712 may also provide support for network slice-specific authentication and authorization.

[0060] The AMF 714 supports termination of the RAN CP interface (N2), termination of NAS (N1) for NAS encryption and integrity protection, registration management, connection management, reachability management, mobility management, lawful interception (for AMF events and interfaces to the LI system), transport of SMS messages between the UE and SMF, transparent proxy for routing SM messages, access authentication, access authorization, transport of SMS messages between the UE and SMSF, SEAF, location service management for regulated services, transport of location service messages between the UE and LMF and between the RAN and LMF, EPS bearer ID allocation for interworking with EPS, UE mobility event notification, control plane CIoT 5GS optimization, user plane CIoT 5GS optimization, configuration of external parameters (expected UE behavior parameters or network configuration parameters) and / or network slice-specific authentication and authorization. Some or all of the AMF functions may be supported in a single instance of the AMF 714. Regardless of the number of network functions, in some embodiments, only one NAS interface instance per access network between the UE and the CN terminates at one of the network functions that implements at least NAS security and mobility management. AMF 714 may also include policy-related functions.

[0061] In addition to the above functions, the AMF 714 may also include the following functions to support non-3GPP access networks: support N2 interface with N3IWF / TNGF, on which some information (e.g., 3GPP cell site identity) and procedures (e.g., handover related) defined on 3GPP access may not be applicable, and non-3GPP access specific information that is not applicable to 3GPP access may be applied; support NAS signaling with UE through N3IWF / TNGF, where some procedures supported by NAS signaling through 3GPP access may not be applicable to untrusted non-3GPP (e.g., paging) access; support verification of UEs connected through N3IWF / TNGF; management of mobility, authentication, and separate security context states for UEs connected via non-3GPP access or via both 3GPP access and non-3GPP access; support coordinated RM management context valid on 3GPP access and non-3GPP access; and / or support dedicated CM management context for UEs connected via non-3GPP access. It may not be necessary to support all of the above functions in the instance of network slicing.

[0062] The SMF 716 supports session management (e.g., session establishment, modification, and release, including tunnel maintenance between the UPF and AN nodes), UE IP address allocation and management (including optional authorization) (where the UE IP address may be received from the UPF or from an external data network), DHCPv4 (server and client) and DHCPv6 (server and client) functions, functions for responding to Address Resolution Protocol requests and / or IPv6 neighbor solicitation requests based on locally cached information in Ethernet PDUs (e.g., the SMF responds to ARP and / or IPv6 neighbor solicitation requests by providing a MAC address corresponding to the IP address sent in the request), selection and control of user plane functions (including controlling the UPF to proxy ARP or IPv6 neighbor discovery or forwarding all ARP / IPv6 neighbor solicitation traffic to the SMF for Ethernet PDU sessions), traffic steering configuration at the UPF to route traffic to the appropriate destination, 5G VN group management (e.g., maintaining the topology of the involved PSA UPFs, in which case the SMF may also be used to forward traffic to the SMF for Ethernet PDU sessions), ... Establish and release N19 tunnels between UPFs, configure traffic forwarding at the UPF to apply local switching and / or N6-based forwarding or N19-based forwarding), terminate interfaces towards the policy control function, lawful interception (for SM events and interfaces to the LI system), charging data collection and support for charging interfaces, control and coordination of charging data collection at the UPF, terminate the SM part of the NAS message, downlink data notification, initiator of AN-specific SM information sent to the AN via the AMF over N2, determination of the SSC mode of the session, control plane CIoT 5GS optimization, header compression, act as an I-SMF in deployments where I-SMFs can be inserted / removed / relocated, configure external parameters (expected UE behavior parameters or network configuration parameters), P-CSCF discovery for IMS services, roaming functions (e.g., handling local implementation to apply QoS SLA (VPLMN), charging data collection and charging interface (VPLMN) and / or lawful interception (in VPLMN for SM events and interface to LI system), interaction with external DN to transmit signaling for PDU session authentication / authorization for external DN and / or instructing UPF and NG-RAN to perform redundant transmission on N3 / N9 interface. Some or all SMF functions can be supported in a single instance of SMF. However, in some embodiments, not all functions need to be supported in an instance of network slice. In addition to functions, SMF 716 may include policy-related functions.

[0063] The SCP 718 includes one or more of the following functions: indirect communication; delegated discovery; message forwarding and routing to the destination NF / NF service; communication security (e.g., authorization of NF service consumers to access NF service manufacturer APIs), load balancing, monitoring, overload control, etc.; and / or optionally interacting with the UDR to resolve the UDM group ID / UDR group ID / AUSF group ID / PCF group ID / CHF group ID / HSS group ID based on the UE identity (e.g., SUPI or IMPI / IMPU). Some or all of the SCP functions may be supported in a single instance of the SCP. In certain embodiments, the SCP 718 may be deployed in a distributed manner and / or more than one SCP may be present in the communication path between NF services. The SCP may be deployed at the PLMN level, the shared slice level, and the slice-specific level. Operator deployment may be left to ensure that the SCP can communicate with the relevant NRFs.

[0064] UE 720 may include a device with radio communication capabilities. For example, UE 720 may include a smartphone (e.g., a handheld touchscreen mobile computing device that can connect to one or more cellular networks). UE 720 may also include any mobile or non-mobile computing device, such as a personal data assistant (PDA), a pager, a laptop computer, a desktop computer, a wireless handset, or any computing device that includes a wireless communication interface. UE is also referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, or reconfigurable mobile device. UE 720 may include an IoT UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. The IoT UE may exchange data with an MTC server or device via a PLMN, other UEs using ProSe or D2D communications, a sensor network, or an IoT network using technologies (e.g., M2M, MTC, or mMTC technologies). M2M or MTC data exchanges may be machine-initiated data exchanges. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure). The IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0065] The UE 720 may be configured to connect or communicatively couple with the (R)AN 722 via a radio interface 730, which may be a physical communication interface or layer configured to operate with a cellular communication protocol such as a GSM protocol, a CDMA network protocol, a push-to-talk (PTT) protocol, a PTT over cellular (POC) protocol, a UMTS protocol, a 3GPP LTE protocol, a 5G protocol, an NR protocol, etc. For example, the UE 720 and the (R)AN 722 may use a Uu interface (e.g., an LTE-Uu interface) to exchange control plane data via a protocol stack including a PHY layer, a MAC layer, an RLC layer, a PDCP layer, and an RRC layer. DL transmissions may be from the (R)AN 722 to the UE 720, and UL transmissions may be from the UE 720 to the (R)AN 722. The UE 720 may also use a side link to directly communicate with another UE (not shown) for D2D, P2P, and / or ProSe communication. For example, the ProSe interface may include one or more logical channels, including but not limited to a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), a physical sidelink discovery channel (PSDCH), and a physical sidelink broadcast channel (PSBCH).

[0066] The (R)AN 722 may include one or more access nodes, which may be referred to as a base station (BS), a Node B, an evolved Node B (eNB), a next-generation Node B (gNB), a RAN node, a controller, a transmission reception point (TRP), etc., and may include a ground station (e.g., a terrestrial access point) or a satellite station, which provides coverage within a geographic area (e.g., a cellular base station). The (R)AN 722 may include one or more RAN nodes for providing macrocell base stations, picocell base stations, femtocell base stations, or other types of cellular base stations. A macrocell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by a UE with a service subscription. A picocell may cover a relatively small geographic area and may allow unrestricted access by a UE with a service subscription. A femtocell may cover a relatively small geographic area (e.g., a home) and may allow restricted access to UEs associated with the femtocell (e.g., UEs in a closed subscriber group (CSG), UEs of users in a home, etc.).

[0067] Although not shown, multiple RAN nodes (such as (R)AN 722) may be used, with an Xn interface defined between two or more nodes. In some implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support / provide data forwarding and flow control functions. The Xn-C may provide management and error handling functions for managing the functions of the Xn-C interface; mobility support for the UE 720 in connected mode (e.g., CM-connected) includes functions for managing UE mobility in connected mode between one or more (R)AN nodes. This mobility support may include context transfer from an old (source) serving (R)AN node to a new (target) serving (R)AN node; and control of a user plane tunnel between the old (source) serving (R)AN node and the new (target) serving (R)AN node.

[0068] The UPF 724 can serve as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point interconnected with the DN 726, and a branch point to support multi-homed PDU sessions. The UPF 724 can also perform packet routing and forwarding, packet inspection, enforce the user plane portion of policy rules, lawful interception of packets (UP collection); traffic usage reporting, perform QoS processing on the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic validation (e.g., SDF to QoS flow mapping), transport level packet marking in the uplink and downlink, and downlink packet buffering and downlink data notification triggering. The UPF 724 may include an uplink classifier to support routing of traffic flows to the data network. The DN 726 may represent various network operator services, Internet access, or third-party services. The DN 726 may include, for example, an application server.

[0069] Figure 8 800 is a block diagram of an example UE 800 that can be configured according to various embodiments of the present disclosure, including by executing instructions corresponding to any of the example methods and / or processes described herein on a computer-readable medium. The UE 800 includes one or more processors 802, a transceiver 804, a memory 806, a user interface 808, and a control interface 810.

[0070] The one or more processors 802 may include, for example, an application processor, an audio digital signal processor, a central processing unit, and / or one or more baseband processors. Each of the one or more processors 802 may include internal memory and / or may include an interface for communicating with external memory (including memory 806). The internal or external memory may store software code, programs, and / or instructions for execution by the one or more processors 802 to configure and / or facilitate the UE 800 to perform various operations, including the operations described herein. For example, execution of the instructions may configure the UE 800 to communicate using one or more wired or wireless communication protocols (including one or more wireless communication protocols standardized by 3GPP, such as those commonly referred to as 5G / NR, LTE, LTE-A, UMTS, HSPA, GSM, GPRS, EDGE, etc.) or any other current or future protocol that may be used in conjunction with the one or more transceivers 804, the user interface 808, and / or the control interface 810. For another example, the one or more processors 802 may execute program code stored in the memory 806 or other memory corresponding to the MAC, RLC, PDCP, and RRC layer protocols standardized by 3GPP (e.g., for NR and / or LTE). For another example, the processor 802 may execute program code stored in the memory 806 or other memory that, together with the one or more transceivers 804, implements corresponding PHY layer protocols such as orthogonal frequency division multiplexing (OFDM), orthogonal frequency division multiple access (OFDMA), and single carrier frequency division multiple access (SC-FDMA).

[0071] The memory 806 may include a memory area for the one or more processors 802 to store variables used in protocols, configurations, controls, and other functions of the UE 800 (including operations corresponding to or including any of the example methods and / or processes described herein). In addition, the memory 806 may include non-volatile memory (e.g., flash memory), volatile memory (e.g., static or dynamic RAM), or a combination thereof. In addition, the memory 806 may interact with a memory slot through which removable memory cards of one or more formats (e.g., SD card, memory stick, compact flash, etc.) may be inserted and removed.

[0072] The one or more transceivers 804 may include radio frequency transmitter and / or receiver circuitry that facilitates communication between the UE 800 and other devices supporting similar wireless communication standards and / or protocols. For example, the one or more transceivers 804 may include switches, mixer circuitry, amplifier circuitry, filter circuitry, and synthesizer circuitry. Such RF circuitry may include a receive signal path having circuitry for downconverting RF signals received from a front-end module (FEM) and providing a baseband signal to a baseband processor of the one or more processors 802. The RF circuitry may also include a transmit signal path having circuitry for upconverting baseband signals provided by the baseband processor and providing an RF output signal to the FEM for transmission. The FEM may include a receive signal path having circuitry configured to operate on RF signals received from one or more antennas, amplify the received signals, and provide an amplified version of the received signals to the RF circuitry for further processing. The FEM may also include a transmit signal path having circuitry configured to amplify transmit signals provided by the RF circuitry for transmission via the one or more antennas. In various embodiments, amplification through the transmit or receive signal path may be accomplished in only the RF circuitry, only the FEM, or in both the RF circuitry and the FEM circuitry. In some embodiments, the FEM circuitry may include a TX / RX switch to switch between transmit and receive mode operation.

[0073] In some exemplary embodiments, the one or more transceivers 804 include transmitters and receivers that enable the device to communicate with various 5G / NR networks according to various protocols and / or methods proposed for standardization by 3GPP and / or other standards bodies. For example, such functionality may operate in cooperation with the one or more processors 802 to implement a PHY layer based on OFDM, OFDMA, and / or SC-FDMA techniques, such as described herein with reference to other figures.

[0074] The user interface 808 may take various forms depending on the particular embodiment, or may not be present in the UE 800. In some embodiments, the user interface 808 includes a microphone, a speaker, a slideable button, a depressible button, a display, a touchscreen display, a mechanical or virtual keypad, a mechanical or virtual keyboard, and / or any other user interface features typically present on mobile phones. In other embodiments, the UE 800 may include a tablet computing device with a larger touchscreen display. In such embodiments, one or more of the mechanical features of the user interface 808 may be replaced by comparable or functionally equivalent virtual user interface features (e.g., a virtual keypad, virtual buttons, etc.) implemented using a touchscreen display, as will be familiar to those skilled in the art. In other embodiments, the UE 800 may be a digital computing device, such as a laptop computer, desktop computer, workstation, etc., that includes a mechanical keyboard that may be integrated, detachable, or removable depending on the particular exemplary embodiment. Such digital computing devices may also include a touchscreen display. Many exemplary embodiments of the UE 800 with a touchscreen display are capable of receiving user input, such as input related to the exemplary methods and / or processes described herein or known to those skilled in the art.

[0075] In some exemplary embodiments of the present disclosure, UE 800 may include an orientation sensor that can be used in various ways by the features and functions of UE 800. For example, UE 800 can use the output of the orientation sensor to determine when a user has changed the physical orientation of the touch screen display of UE 800. The indication signal from the orientation sensor can be used for any application executed on UE 800, so that the application can automatically change the orientation of the screen display (e.g., from portrait to landscape) when the indication signal indicates an approximately 90-degree change in the physical orientation of the device. In this way, regardless of the physical orientation of the device, the application can maintain the screen display in a user-readable manner. In addition, the output of the orientation sensor can be used in conjunction with various exemplary embodiments of the present disclosure.

[0076] The control interface 810 can take various forms depending on the particular implementation. For example, the control interface 810 can include an RS-232 interface, an RS-485 interface, a USB interface, an HDMI interface, a Bluetooth interface, an IEEE ("FireWire") interface, an I 2 C interface, PCMCIA interface, etc. In some exemplary embodiments of the present disclosure, the control interface 1260 may include an IEEE 802.3 Ethernet interface, such as described above. In some exemplary embodiments of the present disclosure, the control interface 810 may include an analog interface circuit, which includes, for example, one or more digital-to-analog (D / A) converters and / or analog-to-digital (A / D) converters.

[0077] One of ordinary skill in the art will recognize that the above list of features, interfaces, and radio frequency communication standards is merely exemplary and does not limit the scope of the present disclosure. Figure 8 The UE 800 may include further functionality, including, for example, a video and / or still image camera, a microphone, a media player and / or recorder, and the like. Furthermore, the one or more transceivers 804 may include circuitry for communicating using additional radio frequency communication standards, including Bluetooth, GPS, and / or others. Furthermore, the one or more processors 802 may execute software code stored in the memory 806 to control such additional functionality. For example, the directional velocity and / or position estimate output from the GPS receiver may be used by any application executing on the UE 800, including various exemplary methods and / or computer-readable media according to various exemplary embodiments of the present disclosure.

[0078] Figure 9 is a block diagram of an example network node 900 that may be configured according to various embodiments of the present disclosure, including by executing instructions on a computer-readable medium corresponding to any of the example methods and / or processes described herein.

[0079] The network node 900 includes one or more processors 902, a radio network interface 904, a memory 906, a core network interface 908, and other interfaces 910. The network node 900 may include, for example, a base station, an eNB, a gNB, an access node, or components thereof.

[0080] The one or more processors 902 may include any type of processor or processing circuit and may be configured to perform one of the methods or processes disclosed herein. The memory 906 may store software code, programs, and / or instructions executed by the one or more processors 902 to configure the network node 900 to perform various operations, including the operations described herein. For example, the execution of such stored instructions may configure the network node 900 to communicate with one or more other devices using protocols according to various embodiments of the present disclosure (including one or more methods and / or processes described above). In addition, the execution of such stored instructions may also configure and / or facilitate the network node 900 to communicate with one or more other devices using other protocols or protocol layers (such as one or more of the PHY, MAC, RLC, PDCP, and RRC layer protocols standardized by 3GPP for LTE, LTE-A, and / or NR, or any other high-layer protocols used in conjunction with the radio network interface 904 and the core network interface 908). By way of example and not limitation, the core network interface 908 includes an S1 interface, and the radio network interface 904 may include a Uu interface, such as standardized by 3GPP. The memory 906 may also store variables used in the protocol, configuration, control, and other functions of the network node 900. Thus, the memory 906 may include non-volatile memory (e.g., flash memory, hard disk, etc.), volatile memory (e.g., static or dynamic RAM), network-based (e.g., "cloud") storage, or a combination thereof.

[0081] The radio network interface 904 may include a transmitter, a receiver, a signal processor, an ASIC, an antenna, a beamforming unit, and other circuits that enable the network node 900 to communicate with other equipment (in some embodiments, such as multiple compatible user equipment (UE)). In some embodiments, the network node 900 may include various protocols or protocol layers, such as PHY, MAC, RLC, PDCP, and RRC layer protocols standardized by 3GPP for LTE, LTE-A, and / or 5G / NR. According to another embodiment of the present disclosure, the radio network interface 904 may include a PHY layer based on OFDM, OFDMA, and / or SC-FDMA technology. In some embodiments, the functionality of such a PHY layer may be provided collaboratively by the radio network interface 904 and the one or more processors 902.

[0082] The core network interface 908 may include transmitters, receivers, and other circuits that enable the network node 900 to communicate with other equipment in the core network (in some embodiments, such as a circuit-switched (CS) and / or packet-switched core (PS) network). In some embodiments, the core network interface 908 may include an S1 interface standardized by 3GPP. In some embodiments, the core network interface 908 may include one or more interfaces to one or more SGWs, MMEs, SGSNs, GGSNs, and other physical devices, including functions known to those skilled in the art that exist in GERAN, UTRAN, E-UTRAN, and CDMA2000 core networks. In some embodiments, these one or more interfaces may be multiplexed together on a single physical interface. In some embodiments, the lower layers of the core network interface 908 may include one or more of asynchronous transfer mode (ATM), Internet Protocol (IP) over Ethernet, SDH over fiber, T1 / E1 / PDH over copper, microwave radio, or other wired or wireless transmission technologies known to those skilled in the art.

[0083] Other interfaces 910 may include transmitters, receivers, and other circuits that enable network node 900 to communicate with external networks, computers, databases, etc., for operation, management, and maintenance of network node 900 or other network equipment operably connected thereto.

[0084] Example

[0085] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes and / or methods described in the following embodiments. For example, the baseband circuitry or other processors or processing circuitry described herein may be configured to operate according to one or more of the following embodiments. For another example, the circuitry associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the embodiments described below.

[0086] Example 1 may include an apparatus comprising means for performing one or more elements of the methods described herein.

[0087] Example 2 may include one or more non-transitory computer-readable media that include instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of the method or process described herein.

[0088] Embodiment 3 may include an apparatus comprising logic components, modules, or circuits for executing one or more elements of the methods or processes described herein.

[0089] Embodiment 4 may include the methods, techniques, or processes described in or related to any one of Embodiments 1 to 3, or portions or components thereof.

[0090] Example 5 may include a device comprising: one or more processors and one or more computer-readable media, the one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the methods, techniques, or processes described in or related to any embodiment herein.

[0091] Unless expressly stated otherwise, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of the various embodiments.

[0092] Embodiments and implementations of the systems and methods described herein may include various operations that may be embodied in machine-executable instructions to be executed by a computer system. A computer system may include one or more general-purpose or special-purpose computers (or other electronic devices). A computer system may include hardware components that include specific logic components for performing the operations, or may include a combination of hardware, software, and / or firmware.

[0093] It should be understood that the systems described herein include descriptions of specific embodiments. These embodiments can be combined into a single system, partially integrated into other systems, separated into multiple systems, or otherwise divided or combined. In addition, it is contemplated that parameters, attributes, aspects, etc. of one embodiment can be used in another embodiment. For clarity, these parameters, attributes, aspects, etc. are described only in one or more embodiments, and it should be understood that unless otherwise stated herein, these parameters, attributes, aspects, etc. can be combined with or substituted for parameters, attributes, etc. of another embodiment.

[0094] Although the foregoing has been described in considerable detail for purposes of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles of the invention. It should be noted that there are many alternative ways of implementing both the processes and the apparatus described herein. The embodiments of the present invention are therefore to be considered illustrative and not restrictive, and the description is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

Claims

1. A method for a user equipment (UE) to identify a cell global identifier (CGI) of a target cell, comprising: Determining that a synchronization signal block (SSB) measurement timing configuration (SMTC) periodicity of the target cell has been configured by a serving cell; Decoding a master information block (MIB), wherein the MIB includes multiplexing mode information; Based on decoding the MIB, identifying whether the SSB and control resource set CORESET multiplexing mode is mode 1, mode 2 or mode 3; Based on identifying that the SSB and CORESET multiplexing mode is mode 2 or mode 3, periodically reading system information block type 1 SIB1 using the SMTC of the target cell; as well as Obtain the CGI of the target cell in the SIB1. 2 . The method according to claim 1 , wherein the multiplexing mode information is included in a pdcch-ConfigSIB1 parameter of the MIB. 3 . The method according to claim 1 , further comprising periodically interrupting the connection with the serving cell according to the SMTC period.

4. The method of claim 3, wherein the interruption is associated with a downlink channel from the serving cell to the UE and an uplink channel from the UE to the serving cell.

5. The method of claim 1 , further comprising reading the SIB1 based on a 20 millisecond repetitive transmission period based on identifying the SSB and CORESET multiplexing mode as Mode 1.

6. A method for a user equipment (UE) to identify a cell global identifier (CGI) of a target cell, comprising: Determining that a synchronization signal block (SSB) measurement timing configuration (SMTC) periodicity of the target cell has been configured by a serving cell; decoding a master information block (MIB), wherein the MIB includes multiplexing mode information, and wherein the decoding obtains a MIB repetition periodicity; Based on decoding the MIB, identifying whether the SSB and control resource set CORESET multiplexing mode is mode 1, mode 2 or mode 3; Based on identifying that the SSB and CORESET multiplexing mode is mode 2 or mode 3, repeatedly and periodically reading system information block type 1 SIB1 using the MIB; as well as Obtain the CGI of the target cell in the SIB1. The method according to claim 6 , wherein the multiplexing mode information is included in a pdcch-ConfigSIB1 parameter of the MIB.

8. The method of claim 6, wherein decoding the MIB is performed using the SMTC periodicity to perform Physical Broadcast Channel (PBCH) decoding.

9. The method of claim 8, wherein when the SSB opportunity is identified as being more frequent outside the SMTC periodicity than within the SMTC periodicity, decoding the MIB using the opportunity of the SSB is performed.

10. The method of claim 6, further comprising reading the SIB1 based on a 20 millisecond repetitive transmission period based on identifying the SSB and CORESET multiplexing mode as Mode 1.

11. A method for a user equipment (UE) to identify a cell global identifier (CGI) of a target cell, comprising: Determining that a synchronization signal block (SSB) measurement timing configuration (SMTC) periodicity of the target cell has not been configured by a serving cell; Decoding a master information block (MIB), wherein the MIB includes multiplexing mode information; Based on decoding the MIB, identifying whether the SSB and control resource set CORESET multiplexing mode is mode 1, mode 2 or mode 3; Based on identifying the SSB and CORESET multiplexing mode as mode 2 or mode 3, reading the system information block type 1 SIB1 using a 20 millisecond repetitive transmission period; as well as Obtain the CGI of the target cell in the SIB1. 12 . The method according to claim 11 , wherein the multiplexing mode information is included in a pdcch-ConfigSIB1 parameter of the MIB.

13. The method of claim 11, wherein decoding the MIB is performed with a 5 millisecond periodicity.

14. The method of claim 11, wherein decoding the MIB is performed with a 20 millisecond periodicity.

15. The method of claim 11, further comprising reading the SIB1 based on a 20 millisecond repetitive transmission period based on identifying the SSB and CORESET multiplexing mode as Mode 1.

16. A method for a user equipment (UE) to identify a cell global identifier (CGI) of a target cell, comprising: Determining that a synchronization signal block (SSB) measurement timing configuration (SMTC) periodicity of the target cell has not been configured by a serving cell; Decoding a master information block (MIB), wherein the MIB includes multiplexing mode information; Based on decoding the MIB, identifying whether the SSB and control resource set CORESET multiplexing mode is mode 1, mode 2 or mode 3; Based on identifying the SSB and CORESET multiplexing mode as mode 2 or mode 3, reading the system information block type 1 SIB1 using a 5 millisecond repetitive transmission period; as well as Obtain the CGI of the target cell in the SIB1. 17 . The method according to claim 16 , wherein the multiplexing mode information is included in a pdcch-ConfigSIB1 parameter of the MIB.

18. The method of claim 16, wherein decoding the MIB is performed with a 5 millisecond periodicity.

19. The method of claim 16, wherein decoding the MIB is performed with a 20 millisecond periodicity.

20. The method of claim 16, further comprising reading the SIB1 based on a 20 millisecond repetitive transmission period based on identifying the SSB and CORESET multiplexing mode as Mode 1.

21. A method for a user equipment (UE) to identify a cell global identifier (CGI) of a target cell, comprising: Determining that a synchronization signal block (SSB) measurement timing configuration (SMTC) periodicity of the target cell has not been configured by a serving cell; Decoding a master information block (MIB) using a MIB repetition transmission period, wherein the MIB includes multiplexing mode information; Based on decoding the MIB, identifying whether the SSB and control resource set CORESET multiplexing mode is mode 1, mode 2 or mode 3; Based on identifying that the SSB and CORESET multiplexing mode is mode 2 or mode 3, reading the system information block type 1 SIB1 using the MIB repetition transmission period; as well as Obtain the CGI of the target cell in the SIB1.

22. The method according to claim 21, wherein the multiplexing mode information is included in a pdcch-ConfigSIB1 parameter of the MIB.

23. The method of claim 21, wherein decoding the MIB is performed with a 5 millisecond periodicity.

24. The method of claim 21, wherein decoding the MIB is performed with a 20 millisecond periodicity.

25. The method of claim 21, further comprising reading the SIB1 based on a 20 millisecond repetitive transmission period based on identifying the SSB and CORESET multiplexing mode as Mode 1.

26. An electronic device comprising means for performing the method according to any one of claims 1 to 25.

27. A computer-readable medium storing instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform the method according to any one of claims 1 to 25.

28. An electronic device, comprising: one or more processors; as well as One or more computer-readable media storing instructions that, when executed by the one or more processors, cause the one or more processors to perform the method of any one of claims 1 to 25.

Images