Non-signaling data transmission

Abstract

A user equipment (UE) is configured to: receive (405) configuration information comprising a plurality of configuration sets; receiving (440) a paging message from a base station, the paging message configured to initiate a mobile terminal connection between the UE and the base station; identifying a first configuration set assigned to the UE from the plurality of configuration sets based on the paging message; and exchanging data with the network using the first set of configurations, wherein exchanging data with the network includes at least one of receiving (445) downlink data and transmitting (450) uplink data.

Description

Background Art

[0001] A user equipment (UE) may establish a connection to a base station to receive data from a network and / or transmit data to a network. The UE and base station may perform procedures including signaling exchanges (e.g., random access, etc.) prior to data transmission. Signaling exchanges require UE resources (e.g., power, processing, etc.), radio resources, and network node resources (e.g., power, processing, etc.). However, in some scenarios, signaling exchanges prior to data transmission are an inefficient use of UE and network resources. Summary of the Invention

[0002] Some exemplary embodiments relate to a method performed by a user equipment (UE). The method includes: receiving configuration information including a plurality of configuration sets; receiving a paging message from a base station, the paging message configured to initiate a mobile terminal connection between the UE and the base station; identifying a first configuration set assigned to the UE from the plurality of configuration sets based on the paging message; and exchanging data with a network using the first configuration set, wherein exchanging data with the network includes at least one of receiving downlink data and transmitting uplink data.

[0003] Other exemplary embodiments relate to a user equipment having: a transceiver configured to communicate with a base station; and a processor communicatively coupled to the transceiver. The processor is configured to: receive configuration information including a plurality of configuration sets; receive a paging message from the base station, the paging message configured to initiate a mobile terminal connection between the UE and the base station; identify a first configuration set assigned to the UE from the plurality of configuration sets based on the paging message; and exchange data with a network using the first configuration set, wherein exchanging data with the network includes at least one of receiving downlink data and transmitting uplink data.

[0004] Yet another exemplary embodiment relates to a method performed by a base station. The method includes: transmitting a paging message to a user equipment (UE), the paging message configured to initiate a mobile terminal connection between the UE and the base station; identifying a first configuration set assigned to the UE from a plurality of configuration sets; and exchanging data with the UE using the first configuration set, wherein exchanging data with a network includes at least one of receiving downlink data and transmitting uplink data.

[0005] Additional exemplary embodiments relate to a base station having: a transceiver configured to communicate with a user equipment (UE); and a processor communicatively coupled to the transceiver. The processor is configured to: transmit a paging message to the UE, the paging message configured to initiate a mobile terminal connection between the UE and the base station; identify a first configuration set assigned to the UE from a plurality of configuration sets; and exchange data with the UE using the first configuration set, wherein exchanging data with a network includes at least one of receiving downlink data and transmitting uplink data. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] Figure 1 Exemplary network arrangements are shown according to various exemplary embodiments.

[0007] Figure 2 An exemplary user equipment (UE) is shown in accordance with various exemplary embodiments.

[0008] Figure 3 An exemplary base station is shown in accordance with various exemplary embodiments.

[0009] Figure 4 A signaling diagram for signaling-free data transfer (SLDT) according to various exemplary embodiments is shown.

[0010] Figure 5 An exemplary SLDT data payload structure is shown according to various exemplary embodiments.

[0011] Figure 6 A signaling diagram for SLDT connection Type 1 is shown according to various exemplary embodiments.

[0012] Figure 7 A signaling diagram for compute offloading using SLDT connection Type 1 is shown according to various exemplary embodiments.

[0013] Figure 8 A signaling diagram for compute offloading using SLDT connection Type 1 is shown according to various exemplary embodiments.

[0014] Figure 9 A signaling diagram for SLDT connection Type 2 is shown according to various exemplary embodiments.

[0015] Figure 10 A signaling diagram for localized paging is shown according to various exemplary embodiments.

[0016] Figure 11 Shown are signaling diagrams for paging a UE from multiple cells for SLDT according to various exemplary embodiments.

[0017] Figure 12 An example of a mapping between a paging message and a SLDT configuration set according to various exemplary embodiments is shown.

[0018] Figure 13 Examples of paging records that may be provided in a paging message are shown, according to various exemplary embodiments.

[0019] Figure 14 Examples of static allocation of resources for SLDT according to various exemplary embodiments are shown.

[0020] Figure 15 Examples of dynamic allocation of resources for SLDT according to various exemplary embodiments are shown. DETAILED DESCRIPTION

[0021] The exemplary embodiments may be further understood with reference to the following description and associated drawings, in which like elements are provided with like reference numerals. The exemplary embodiments introduce a data transfer mechanism for a wireless communication system. Throughout this specification, the data transfer mechanism may generally be referred to as "Signalingless Data Transfer (SLDT)". However, reference to the term Signalingless Data Transfer (SLDT) is provided for illustrative purposes only, and different entities may refer to similar concepts by different names. As will be described in more detail below, SLDT uses techniques that require less overhead on user equipment (UE) resources (e.g., power, processing, etc.), radio resources (e.g., public, shared, etc.), and network node resources (e.g., power, processing, etc.) compared to some conventional approaches.

[0022] The exemplary embodiments are described with reference to a UE. However, reference to a UE is provided for illustrative purposes only. The exemplary embodiments may be used with any electronic component configured with hardware, software, and / or firmware for exchanging information and data with a network. Therefore, a UE as described herein is used to represent any suitable electronic component.

[0023] The exemplary embodiments are also described with reference to sixth generation (6G) networks. However, reference to 6G networks is provided for illustrative purposes only. The exemplary embodiments may be utilized with any suitable type of network.

[0024] A UE may establish a connection to a base station of a network to receive data from the network and / or transmit data to the network. In some conventional methods, the UE and the base station may perform a process including a signaling exchange prior to data transmission. For example, a cell access procedure (e.g., random access) may be performed. The signaling exchange requires UE resources, radio resources, and network node resources.

[0025] The exemplary embodiments are described with reference to a mobile terminal connection triggered by the network via a paging message. Following the paging message, data transfer may be performed in the uplink and / or downlink. However, in contrast to conventional approaches in which the UE initiates a random access procedure or some other type of signaling exchange in response to a paging message, the exemplary embodiments allow the UE to directly receive downlink data and / or transmit uplink data.

[0026] In 6G, some UEs (e.g., Internet of Things (IoT) devices, sensors, etc.) may be stationary or have limited mobility. Other UEs may only require a small amount of data (e.g., one or two packets). For these types of devices, establishing a connection in a normal manner (e.g., a cell access process) may add unnecessary overhead to UE resources, radio resources, and / or network node resources. Therefore, the exemplary embodiments introduced herein may provide benefits to these types of devices in 6G systems. However, the exemplary embodiments are not limited to these types of devices or 6G. The exemplary techniques introduced herein may be used by any appropriate type of device in any appropriate type of wireless communication system.

[0027] As indicated above, the exemplary embodiments include techniques for performing data transfer between a UE and a network in response to a paging message without requiring a cell access procedure or some other type of signaling exchange. Furthermore, the exemplary embodiments introduce security schemes for SLDT, different SLDT connection types, paging mechanisms, and techniques for resource allocation. The exemplary embodiments described herein can be implemented independently of each other, in conjunction with other currently implemented data transfer mechanisms, in conjunction with future implementations of data transfer mechanisms, and independently of other data transfer mechanisms.

[0028] Figure 1 An exemplary network arrangement 100 according to various exemplary embodiments is shown. The exemplary network arrangement 100 includes a UE 110. Those skilled in the art will appreciate that the UE 110 can be any type of electronic component configured to communicate via a network, such as a mobile phone, tablet computer, desktop computer, smartphone, phablet, embedded device, wearable device, Internet of Things (IoT) device, sensor, etc. It should also be understood that an actual network arrangement can include any number of UEs used by any number of users. Therefore, the example of a single UE 110 is provided for illustrative purposes only.

[0029] UE 110 can be configured to communicate with one or more networks. In the example of network configuration 100, the network with which UE 110 can wirelessly communicate is a 6G radio access network (RAN) 120. However, UE 110 can also communicate with other types of networks (e.g., fifth generation (5G) new radio (NR) RAN, 5G cloud RAN, next generation RAN (NG-RAN), long term evolution (LTE) RAN, traditional cellular networks, wireless local area networks (WLAN), etc.), and UE 110 can also communicate with the network via a wired connection. Referring to the exemplary embodiment, UE 110 can establish a connection with at least 6G RAN 120. Therefore, UE 110 can have a 6G chipset to communicate with 6G RAN 120.

[0030] The 6G RAN 120 may be part of a cellular network that may be deployed by a network operator, such as Verizon, AT&T, T-Mobile, etc. The 6G RAN 120 may include, for example, cells or base stations (eNBs, gNBs, macro cells, micro cells, small cells, femto cells, etc.) configured to transmit and receive traffic from UEs equipped with appropriate cellular chipsets.

[0031] In network arrangement 100, UE 110 may connect to 6G RAN 120 via base station (BTS) 120A. Those skilled in the art will appreciate that any association process may be performed to connect UE 110 to 6G RAN 120. For example, as discussed above, 6G RAN 120 may be associated with a particular cellular provider, with which UE 110 and / or its user has a contract and credential information (e.g., stored on a SIM card). Upon detecting the presence of 6G RAN 120, UE 110 may transmit corresponding credential information to associate with 6G RAN 120. More specifically, UE 110 may associate with a particular base station (e.g., BTS 120A). However, as mentioned above, reference to 6G RAN 120 is for illustrative purposes only, and any suitable type of RAN may be used.

[0032] The network arrangement 100 also includes a cellular core network 130, the Internet 140, an IP Multimedia Subsystem (IMS) 150, and a network services backbone 160. The cellular core network 130 can be viewed as an interconnected collection of components that manage the operation and traffic of the cellular network. The cellular core network 130 also manages the traffic flowing between the cellular network and the Internet 140. The IMS 150 can generally be described as an architecture for delivering multimedia services to the UE 110 using IP protocols. The IMS 150 can communicate with the cellular core network 130 and the Internet 140 to provide multimedia services to the UE 110. The network services backbone 160 communicates directly or indirectly with the Internet 140 and the cellular core network 130. The network services backbone 160 can generally be described as a collection of components (e.g., servers, network storage arrangements, etc.) that implement a set of services that can be used to extend the functionality of the UE 110 in communicating with various networks.

[0033] Figure 2 An exemplary UE 110 is shown according to various exemplary embodiments. The UE 110 will refer to Figure 1 1. The UE 110 may include a processor 205, a memory arrangement 210, a display device 215, an input / output (I / O) device 220, a transceiver 225, and other components 230. The other components 230 may include, for example, an audio input device, an audio output device, a power supply, a data acquisition device, a port for electrically connecting the UE 110 to other electronic devices, and the like.

[0034] The processor 205 may be configured to execute multiple engines of the UE 110. For example, the engines may include the SLDT engine 235. The SLDT engine 235 may perform various operations related to the exemplary embodiments described herein. These operations may include, but are not limited to, receiving SLDT configuration information from the network, receiving paging messages, receiving data, and transmitting data.

[0035] The engine 235 referenced above is provided as an application (e.g., a program) executed by the processor 205 for illustrative purposes only. The functionality associated with the engine 235 may also be represented as a separate incorporated component of the UE 110, or may be a modular component coupled to the UE 110, such as an integrated circuit with or without firmware. For example, the integrated circuit may include input circuitry for receiving signals and processing circuitry for processing signals and other information. The engine may also be embodied as one application or multiple separate applications. Furthermore, in some UEs, the functionality described with respect to the processor 205 is split between two or more processors, such as a baseband processor and an application processor. The exemplary embodiments may be implemented in any of these or other configurations of the UE.

[0036] The memory arrangement 210 may be a hardware component configured to store data related to operations performed by the UE 110. The display device 215 may be a hardware component configured to display data to a user, while the I / O device 220 may be a hardware component that enables a user to enter input. The display device 215 and the I / O device 220 may be separate components or may be integrated together (such as a touch screen). The transceiver 225 may be a hardware component configured to establish a connection with the 6G RAN 120 and / or any other suitable type of network. Thus, the transceiver 225 may operate on a variety of different frequencies or channels (e.g., a set of contiguous frequencies).

[0037] Figure 3 An exemplary base station 300 is shown in accordance with various exemplary embodiments. Base station 300 may represent any access node (eg, BTS 120A, etc.) that UE 110 may use to establish a connection and manage network operations.

[0038] Base station 300 may include a processor 305, a memory arrangement 310, input / output (I / O) devices 315, a transceiver 320, and other components 325. Other components 325 may include, for example, a battery, a data acquisition device, ports for electrically connecting base station 300 to other electronic devices, and the like.

[0039] Processor 305 may be configured to execute various engines of base station 300. For example, these engines may include SLDT engine 330. SLDT engine 330 may perform various operations related to the exemplary embodiments described herein. These operations may include, but are not limited to, transmitting SLDT configuration information from the network, transmitting paging messages, receiving data from UE 110, and transmitting data to UE 110.

[0040] The engine 330 mentioned above as an application (e.g., a program) executed by the processor 305 is merely exemplary. The functionality associated with the engine 330 may also be represented as a separate integrated component of the base station 300, or may be a modular component coupled to the base station 300, such as an integrated circuit with or without firmware. For example, the integrated circuit may include input circuitry for receiving signals and processing circuitry for processing signals and other information. In addition, in some base stations, the functionality described for the processor 305 is split between multiple processors (e.g., a baseband processor, an application processor, etc.). The exemplary embodiments may be implemented in any of these or other configurations of the base station.

[0041] The memory 310 may be a hardware component configured to store data related to operations performed by the base station 300. The I / O device 315 may be a hardware component or port that enables a user to interact with the base station 300. The transceiver 320 may be a hardware component configured to exchange data with the UE 110 and any other UE in the system 100. The transceiver 320 may operate on a variety of different frequencies or channels (e.g., a set of contiguous frequencies). Thus, the transceiver 320 may include one or more components (e.g., radio components) to enable data exchange with various networks and UEs.

[0042] Figure 4 A signaling diagram 400 for SLDT is shown, according to various exemplary embodiments. The signaling diagram 400 includes a UE 110, a BTS 120A, and a core network 130.

[0043] As indicated above, according to SLDT, UE 110 may receive a paging message. In response to the paging message, UE 110 may use pre-configured information to directly receive downlink data and / or transmit uplink data, rather than performing random access or some other type of signaling exchange with a base station. Signaling diagram 400 will be shown in FIG. Figure 1 A general overview of an example of SLDT is provided within the context of the network arrangement 100. Specific aspects of SLDT are described in more detail below, following the description of the signaling diagram 400.

[0044] In 405, BTS 120A sends SLDT configuration information to UE 110. The SLDT configuration information may be provided in a system information block (SIB), a dedicated configuration message, or one or more messages of any other suitable type.

[0045] Throughout this specification, SLDT configuration information may generally refer to information that may be used by UE 110 to perform data transfer. For example, SLDT configuration may be a semi-dedicated configuration that may be used by UE 110 in response to a trigger condition (eg, a paging message).

[0046] In some embodiments, SLDT configuration information for one or more SLDT configuration sets may be broadcast by BTS 120A, where each SLDT configuration set may correspond to resources assigned to a single specific UE. For example, UE 110 may receive an SIB from BTS 120A that includes SLDT configuration information for multiple SLDT configuration sets. UE 110 may be assigned one of the SLDT configuration sets, and other UEs may be assigned other SLDT configuration sets. This may ensure that there is no contention for SLDT resources.

[0047] UE 110 stores the SLDT configuration information in 410. As will be described in more detail below, UE 110 waits for a triggering condition (eg, a paging message) to use the SLDT configuration information to receive data from and / or transmit data to the network.

[0048] At 415, downlink data is pending at core network 130 for UE 110. At 420, core network 130 determines whether SLDT is available to perform data transfer with UE 110. For example, core network 130 may evaluate conditions such as, but not limited to, the amount of pending downlink data, the device type of UE 110, the capabilities of UE 110, and the mobility state of UE 110. In this example, it is assumed that SLDT is available to perform data transfer with UE 110. However, in actual deployment scenarios, the conditions for SLDT may not be met, and core network 130 may decide to wait until the SLDT conditions are met, perform data transfer using a different mechanism, or behave in any other appropriate manner.

[0049] In 425, core network 130 sends a paging request to BTS 120A. In this example, the paging request may indicate the amount of pending downlink data for UE 110 and allow SLDT to be performed with UE 110. In 430, core network 130 sends the downlink data to BTS 120A.

[0050] At 435, BTS 120A determines whether an SLDT connection can be initiated. For example, BTS 120A may consider whether radio resources are available for SLDT, whether core network 130 has permitted UE 110 to perform SLDT, the amount of downlink data, and the cell load. In this example, it is assumed that SLDT can be initiated. However, in actual deployment scenarios, BTS 120A may determine that an SLDT connection cannot be initiated and may decide to wait until an SLDT connection can be initiated, use a different mechanism to provide downlink data, or behave in any other appropriate manner.

[0051] Returning to UE 110, during 415 to 435, UE 110 may utilize one or more operating modes. In this example, UE 110 may be in an idle mode in which UE 110 does not typically exchange data with the network and radio resources are not assigned to UE 110 within the network. However, while in the idle state, UE 110 may monitor for information and / or data transmitted by the network. This example is provided for illustrative purposes only and is not intended to limit the exemplary embodiments in any way. Specific examples of different types of operating modes that may be utilized by UE 110 will be described in more detail below after describing signaling diagram 400.

[0052] In 440, BTS 120A sends a paging message to UE 110. The paging message may indicate to UE 110 that SLDT will be used for subsequent data transmission. However, reference to the paging message is provided for illustrative purposes only. Example embodiments may use any suitable type of signal to trigger SLDT.

[0053] UE 110 uses the SLDT configuration information to receive downlink data from BTS 120A in 445. For example, based on the timing and / or content of the paging message in 440, UE 110 may know to use a particular SLDT configuration indicating the time and frequency resources to be used for downlink data.

[0054] Similarly, at 450, UE 110 uses the SLDT configuration information to transmit uplink data to BTS 120A. For example, based on the timing and / or content of the paging message at 440, UE 110 may know that a specific SLDT configuration indicating the time and frequency resources to be used for uplink data will be used. In this example, both downlink data and uplink data are exchanged. However, in actual operational scenarios, only downlink data may be received during an SLDT connection, or only uplink data may be transmitted during an SLDT connection.

[0055] In this example, after the transmission of the uplink data in 450, the UE 110 may return to an idle mode of operation. As mentioned above, the signaling diagram 400 is provided as a general overview of SLDT and is not intended to limit the exemplary embodiments in any way. Specific aspects of SLDT, such as, but not limited to, security schemes for SLDT, SLDT connection types, paging mechanisms, and techniques for resource allocation are described in detail below.

[0056] According to one aspect, an exemplary embodiment includes a security scheme for SLDT using integrity protection and user plane protection. The following exemplary SLDT security scheme is described with reference to an exemplary SLDT data payload structure, an example of which is provided in Figure 5 Shown in.

[0057] Figure 5 An exemplary SLDT data payload structure 500 is shown, in accordance with various exemplary embodiments. The exemplary SLDT payload structure 500 includes a header 510, user plane data 515, and an integrity code 520.

[0058] The exemplary SLDT payload structure 500 may be used for downlink or uplink data. Since SLDT involves a mobile-terminated connection in which the network is initiating a connection for a specific UE, the UE context (e.g., capabilities, configuration state, security context, etc.) may already be known on the network side and may therefore be used by the network for downlink data payload preparation and uplink data payload processing. This is in contrast to mobile-originated connections in which the network needs to know the UE's identity before it can retrieve the UE's associated context.

[0059] The header 510 may be configured to include information for synchronizing security parameters (e.g., keys, etc.) used by the UE and the network. Since the exemplary SLDT payload structure 500 may be used for downlink or uplink communications, the user plane data 515 may include downlink data or uplink data. Furthermore, the user plane data 515 may be encrypted using non-access stratum (NAS) / access stratum (AS) security parameters. The integrity code 520 may be generated using the NAS / AS security context and include information for authentication and data integrity.

[0060] In one approach, a NAS layer security context may be used to implement authentication and user plane data protection. For example, the NAS security context may be used for user plane data protection via encryption and authentication via an integrity code generated by the NAS layer. In another approach, an AS context stored by the UE may be used to implement authentication and user plane data protection. For example, the AS security context may be used for user plane protection via encryption and authentication via an integrity code generated by the AS layer. In another approach, authentication and user plane data protection may be implemented using the advance establishment of an AS security context. The above examples are not intended to limit the exemplary embodiments in any way. If authentication and user plane protection are required, the exemplary embodiments may use the schemes referenced above, or may use any other appropriate type of security scheme for the SLDT data payload. In other embodiments, authentication and user plane protection are not required, and any other appropriate type of security technology may be used for the SLDT data payload.

[0061] In another aspect, the exemplary embodiment introduces SLDT connection Type 1 and SLDT connection Type 2. As will be described in more detail below, the main difference between SLDT connection Type 1 and SLDT connection Type 2 is the number of transmissions that can be performed during the SLDT connection. SLDT connection Type 1 will be referred to below. Figures 6 to 8 A more detailed description is given below, and SLDT connection Type 2 will be referred to Figure 9However, references to the terms SLDT Connection Type 1 and SLDT Connection Type 2 are provided for illustrative purposes only, and different entities may refer to similar concepts by different names.

[0062] SLDT Connection Type 1 may refer to an SLDT connection used for a single downlink data transmission and / or a single uplink data transmission. In some embodiments, SLDT Connection Type 1 may be limited to a maximum number of downlink packets and / or a maximum number of uplink packets. For example, SLDT Connection Type 1 may be used for small data transmissions, with a maximum of one downlink packet and / or one uplink packet without any retransmissions (e.g., request and response transactions).

[0063] Figure 6 Shown is a signaling diagram 600 for SLDT connection Type 1, according to various exemplary embodiments. Signaling diagram 600 includes UE 110 and BTS 120A.

[0064] Initially, consider a scenario where UE 110 is in idle mode. When in idle mode, UE 110 generally does not exchange data with the network, and no radio resources are assigned to UE 110 within the network. For example, UE 110 may be in radio resource control (RRC) idle mode. However, the exemplary embodiments are not limited to RRC idle mode and may be applied to RRC inactive mode or any other operating mode in which UE 110 interrupts at least a subset of its data exchange processing functionality. According to some aspects, the exemplary embodiments may use a mode similar to RRC inactive. However, unlike the RRC inactive concept, there may be no need to maintain any AS context for the UE or to retain a dedicated SLDT configuration for the UE.

[0065] At 610, BTS 120A transmits a paging message to UE 110. For SLDT connection Type 1, the paging message may be referred to as "Msg1A." Msg1A may trigger UE 110 to initiate SLDT connection Type 1. In some embodiments, Msg1A may also indicate whether uplink data transmission is to be scheduled. However, the reference to the term "Msg1A" is provided for illustrative purposes only, and different entities may refer to similar concepts by different names.

[0066] In 615a, BTS 120A may transmit a downlink assignment to UE 110. In 615b, BTS 120A may transmit downlink data to UE 110. If data repetition is enabled, the downlink data may be repeated multiple times to reduce the probability of downlink payload transmission failure.

[0067] Downlink assignments and downlink data may be collectively referred to as "Msg2A." In some scenarios, the SLDT connection may not be used to provide downlink data to UE 110, and therefore, Msg2A may not be used during the SLDT connection. For example, an SLDT connection may be established for UE 110 to provide periodic uplink data to UE 110. However, reference to the term "Msg2A" is provided for illustrative purposes only, and different entities may refer to similar concepts by different names.

[0068] Furthermore, the downlink assignment in 615a may be optional based on the SLDT configuration set (eg, static or dynamic assignment).Different types of SLDT configuration sets will be described in more detail below with reference to exemplary resource allocation techniques.

[0069] In 620a, BTS 120A may transmit an uplink assignment to UE 110. The uplink assignment in 620A may be optional based on the SLDT configuration set (e.g., static or dynamic assignment). In 620b, UE 110 transmits uplink information to BTS 120A that may be used for uplink data processing at BTS 120A. For example, a preamble may be sent by UE 110 to implement an uplink timing advance adjustment. In 620c, UE 110 transmits uplink data to BTS 120A. If data repetition is enabled, the uplink data may be repeated multiple times to reduce the probability of uplink payload transmission failure.

[0070] The uplink assignment, uplink information for processing, and uplink data may be collectively referred to as "Msg3A." In some scenarios, the SLDT connection may not be used to provide uplink data to the network, and therefore Msg3A may not be used during the SLDT connection. Once the data transfer is complete (e.g., 615a or 620c), the SLDT connection Type 1 ends, and the UE 110 may return to its idle mode. However, the reference to the term "Msg3A" is provided for illustrative purposes only, and different entities may refer to similar concepts by different names.

[0071] Figure 7A signaling diagram 700 is shown for computation offloading using SLDT connection Type 1 according to various exemplary embodiments. Signaling diagram 700 includes UE 110, BTS 120A, and a computation node 705 of core network 130. As will be described in detail below, in this example, UE 110 requests that one or more computation tasks be offloaded to core network 130. This request is provided during a non-SLDT type connection (e.g., an RRC connection) or in any other suitable manner. The network then provides the computation results to UE 110 using SLDT connection Type 1.

[0072] In 710, UE 110 is in idle mode. In 715, computation offloading is triggered. In 720, UE 110 connects to BTS 120A and enters RRC connected mode.

[0073] In 725, UE 110 transmits a computation offload request to BTS 120A. The computation offload request may include computation data that UE 110 wants processed by computation node 705 of core network 130. In 730, BTS 120A may release the connection to UE 110, and in 735, UE 110 may return to its idle mode.

[0074] On the network side, in 740, BTS 120A may transmit a computation request including the computation data provided by UE 110 in 725 to computation node 705. In 745, computation node 705 transmits a computation response to BTS 120A. In this example, it is assumed that computation node 705 successfully performs the computation task, and the computation response includes a computation result based on the computation data.

[0075] At 750, BTS 120A may transmit a paging message to UE 110. The paging message may include an indication that SLDT connection Type 1 will be used only for downlink data. At 755, BTS 120A transmits a computation offload response including the downlink data to UE 110. For example, the computation offload response may include the computation results from computation node 705. In this example, since SLDT connection Type 1 will be used only for downlink data, the SLDT connection ends after receiving the downlink data at 755. At 760, UE 110 returns to idle mode.

[0076] Figure 8A signaling diagram 800 is shown for computation offloading using SLDT connection Type 1 according to various exemplary embodiments. Signaling diagram 800 includes UE 110, BTS 120A, and a computation node 805 of core network 130. Compared to the example provided above with reference to signaling diagram 700, UE 110 requests offloading of one or more computation tasks and receives computation results during the same SLDT Type 1 connection.

[0077] In 810, UE 110 is in idle mode. In 815, BTS 120A transmits a paging message to UE 110. The paging message may include an indication that SLDT connection Type 1 is to be used for downlink and uplink data.

[0078] In 820, UE 110 transmits a computation offload request including computation data for processing by computation node 805 to BTS 120A. In 825, BTS 120A transmits a computation request including computation data provided by UE 110 to computation node 805. In 830, computation node 805 transmits a computation response including computation results based on processing the computation data provided by UE 110 to BTS 120A.

[0079] In 835, BTS 120A transmits a computation offload response including the downlink data to UE 110. For example, the computation offload response may include the computation result from computation node 805. Since the uplink data was already provided in 820, the SLDT connection ends after receiving the downlink data in 835. In 840, UE 110 returns to idle mode.

[0080] SLDT connection Type 2 may refer to a SLDT connection used for multiple downlink data transmissions and / or multiple uplink data transmissions. In some embodiments, SLDT connection Type 2 may be combined with a hybrid automatic repeat request (HARQ) or any other suitable type of retransmission scheme.

[0081] Figure 9 A signaling diagram 900 for SLDT connection Type 2 is shown, according to various exemplary embodiments. Signaling diagram 900 includes UE 110 and BTS 120A.

[0082] Initially, consider a scenario where UE 110 is in idle mode. When in idle mode, UE 110 typically does not exchange data with the network, and no radio resources are assigned to UE 110 within the network. For example, UE 110 may be in RRC idle mode. However, the exemplary embodiments are not limited to RRC idle mode and may be applied to RRC inactive mode or any other operating mode in which UE 110 interrupts at least a subset of its data exchange processing functionality.

[0083] At 910, BTS 120A transmits a paging message to UE 110. For SLDT connection Type 2, the paging message may be referred to as "Msg1B." Msg1B may trigger UE 110 to initiate SLDT connection Type 2. In some embodiments, Msg1B may also indicate whether uplink data transmission is to be scheduled. However, the reference to the term "Msg1B" is provided for illustrative purposes only, and different entities may refer to similar concepts by different names.

[0084] In 915, UE 110 transmits initial information to BTS 120A. The initial information may include information that can be used by the network to adjust radio resource assignments for UE 110 and process uplink data received from UE 110. For example, the initial information may include a preamble or some other type of information that can be used for timing advance adjustment. In another example, the initial information may include channel state information (CSI) that enables the network to manage radio resource utilization. In another example, the initial information may include an indication of the size of the pending uplink data. For SLDT connection Type 2, the initial information may be referred to as "Msg2B". However, reference to the term "Msg2B" is provided for illustrative purposes only, and different entities may refer to similar concepts by different names.

[0085] In 920a, BTS 120A may transmit a downlink assignment to UE 110. The downlink assignment in 920a may be optional based on a SLDT configuration set (e.g., a static or dynamic assignment). Different types of SLDT configuration sets will be described in more detail below with reference to exemplary resource allocation techniques.

[0086] In 920b, BTS 120A transmits downlink data to UE 110. In some embodiments, the downlink data payload may include information indicating to UE 110 information regarding the uplink data transmission, such as, but not limited to, uplink timing advance information and power control related information.

[0087] In 920c, UE 110 may transmit downlink data feedback to BTS 120A. The downlink data feedback may include one or more acknowledgements (ACKs), one or more negative acknowledgements (NACKs), and / or requests for retransmissions. However, in some embodiments, SLDT connection Type 2 may not use a retransmission scheme and may not utilize downlink data feedback.

[0088] The downlink assignments, downlink data, and downlink data feedback of 920a-920c may be collectively referred to as "Msg3B." The number of messages encompassed by Msg3B may vary based on pending downlink data and required retransmissions (if any). However, reference to the term "Msg3B" is provided for illustrative purposes only, and different entities may refer to similar concepts by different names.

[0089] In 925a, BTS 120A may transmit an uplink assignment to UE 110. The downlink assignment in 920a may be optional based on the SLDT configuration set (e.g., static or dynamic assignment). Different types of SLDT configuration sets will be described in more detail below with reference to exemplary resource allocation techniques.

[0090] In 925b, UE 110 transmits uplink data to BTS 120A. In 925c, BTS 120A transmits uplink data feedback to UE 110. The uplink data feedback may include one or more ACKs, one or more NACKs, and / or a request for retransmission. However, in some embodiments, SLDT connection Type 2 may not use a retransmission scheme and may not utilize uplink data feedback.

[0091] The uplink assignments, uplink data, and uplink data feedback of 925a-925c may be collectively referred to as "Msg4B". The number of messages encompassed by Msg4B may vary based on the pending uplink data and the number of required retransmissions (if any). However, reference to the term "Msg4B" is provided for illustrative purposes only, and different entities may refer to similar concepts by different names.

[0092] At 930, the SLDT connection Type 2 ends, and UE 110 returns to idle mode. In some embodiments, BTS 120A may send a command to UE 110 indicating the end of the SLDT connection. An example of this command is shown as 935a in signaling diagram 900. The command may be provided via downlink control information (DCI), a medium access control (MAC) control element (CE), or in any other suitable manner. This command may be referred to as "Msg5B." However, reference to the term "Msg5B" is provided for illustrative purposes only, and different entities may refer to similar concepts by different names.

[0093] In other embodiments, UE 110 may operate a timer to trigger the termination of SLDT Connection Type 2. An example of such a timer is shown as 935b in signaling diagram 900. UE 110 may initiate the SLDT Connection timer in response to the paging message received in 910. A timeout may occur if a certain type of message or command is not received within a specified time window. For example, if a Connect-End command is not received in 935a before the SLDT Connection timer expires, UE 110 may declare a timeout and terminate the SLDT Connection Type 2. However, the above example is provided for illustrative purposes only, and the exemplary SLDT Connection timer may be operated in an appropriate manner to ensure that UE 110 does not maintain the SLDT connection for an unnecessary amount of time.

[0094] According to some aspects, exemplary embodiments introduce a paging mechanism for SLDT. The network may not know the exact cell on which UE 110 is camped. The following exemplary embodiments can be used to determine on which cell the network will initiate an SLDT connection with UE 110.

[0095] In some embodiments, sending a paging message to initiate an SLDT connection may be limited to the last serving cell or area based on the device type. For example, consider a scenario where UE 110 is a stationary device (e.g., an IoT sensor, etc.). The network may initiate an SLDT connection only on the last serving cell of UE 110 because UE 110 is a stationary device and the network may assume that UE 110 has not moved since the last time UE 110 communicated with the network.

[0096] In some implementations, the network may utilize a localized paging method. Figure 10 A signaling diagram 1000 for localized paging is shown, according to various exemplary embodiments. Signaling diagram 1000 includes UE 110, BTS 120A, and core network 130.

[0097] Signaling diagram 1000 is described with reference to a UE operating mode referred to as “stationed mode.” As will be described in more detail below, example embodiments utilize stationed mode to determine which cell to use to send a paging message to UE 110 for SLDT.

[0098] The term "stationed mode" refers to a state in which UE 110 is deployed as a stationary device or a device with low mobility. For example, UE 110 may be an IoT sensor that is configured at a first location and then delivered to a second location where UE 110 will perform its configured tasks. At the second location, UE 110 may be placed in a stationed mode, which indicates to UE 110 and / or its network that the device will operate in a stationed or low-mobility state. This allows UE 110 and / or the network to behave under the assumption that UE 110 will remain in approximately the same location. However, reference to the term "stationed mode" is provided for illustrative purposes only, and different entities may refer to similar concepts by different names.

[0099] Initially, consider that UE 110 is connected to the network in a normal connection (e.g., RRC connected mode). In 1010, UE 110 sends a stationed mode request to core network 130. UE 110 may register with the network, indicating that it is entering stationed mode with a specific serving cell or within a specific area. In some embodiments, the stationed mode request may be sent as part of a NAS registration procedure or a tracking area update (TAU) procedure and include information about the serving cell and / or location where the stationed mode is triggered. In some embodiments, UE 110 may trigger stationed mode based on being within a specific location and / or in a stationed or low mobility state for a specific amount of time. However, the examples provided above are provided for illustrative purposes only, and the stationed mode may be provided to the network in any suitable manner.

[0100] At 1015, core network 130 stores the indication that UE 110 will operate in the stationed mode, along with the current UE 110 serving cell information. At 1020, core network 130 sends a stationed mode request response to UE 110. In this example, it is assumed that the stationed mode request has been accepted, and thus the stationed mode response may include an indication that the stationed mode is confirmed. However, in actual deployment scenarios, core network 130 may not accept the stationed mode request for any of a variety of different reasons, and the stationed mode response may include a stationed mode reject message.

[0101] At 1020, core network 130 determines to establish a SLDT connection to UE 110. For example, there may be pending downlink data for UE 110. In another example, the network may be triggered to establish the SLDT connection based on scheduling or some other time-based factor (e.g., time, date, etc.). In another example, core network 130 may receive a request from UE 110 or a signal from another UE or remote device indicating that UE 110 will receive data and / or transmit data. However, the above examples are provided for illustrative purposes only. Core network 130 may decide to establish a SLDT connection with UE 110 for any appropriate reason.

[0102] In 1025, core network 130 sends a paging request for UE 110 to BTS 120A. Since UE 110 is in stationed mode, core network 130 can page UE 110 for the SLDT connection using the serving cell information stored in 1015. In 1030, BTS 120A sends a paging message for the SLDT connection (e.g., SLDT connection Type 1, SLDT connection Type 2, etc.) to UE 110. Figure 4 and Figures 6 to 9 Examples of UE-side and network-side behavior in response to a paging message are shown in the various signaling diagrams described.

[0103] Although not shown in signaling diagram 1000, UE 110 may subsequently identify a condition that triggers UE 110 to exit stationed mode. In this type of scenario, UE 110 may send a message to the network indicating that UE 110 has exited stationed mode. In some embodiments, instead of indicating that UE 110 has exited stationed mode, UE 110 may transmit a message to UE 110 to update the network with new serving cell information or location information so that the network can update the stored associations of UE 110.

[0104] Figure 11 Shown is a signaling diagram 1100 for paging UE 110 from multiple cells for SLDT, according to various exemplary embodiments. Signaling diagram 1100 includes UE 110, BTS 1102, BTS 1104, and BTS 1106.

[0105] According to some embodiments, UE 110 may be paged in multiple cells having SLDT connection Type 2. In 1110, BTS 1102 sends a paging message for SLDT connection Type 2 to UE 110. In 1115, BTS 1104 sends a paging message for SLDT connection Type 2 to UE 110. In 1120, BTS 1106 sends a paging message for SLDT connection Type 2 to UE 110.

[0106] In 1125, UE 110 sends Msg2B to BTS 1102. In this example, only cells that receive SLDT connection Type 2 Msg2B will continue the SLDT connection with UE 110. Since BTS 1104 and BTS 1106 have not received a response from UE 110, the network may stop the SLDT connection at BTS 1104 and BTS 1106. Since BTS 1102 receives a response to the paging message, BTS 1102 may receive downlink data for UE 110 from the core network and continue signaling for SLDT connection Type 2. Signaling for SLDT connection Type 2 is described above with reference to at least Figure 9 The signaling diagram 900 is described.

[0107] According to other aspects, exemplary embodiments introduce techniques for SLDT resource allocation. As mentioned above, exemplary embodiments are described with reference to different SLDT configuration sets. Throughout this specification, an SLDT configuration set refers to a set of radio resources that can be used by a single UE during an SLDT connection. The UE can be aware of the location of radio resources used for the SLDT configuration set based on SLDT configuration information. However, reference to the term SLDT configuration set is provided for illustrative purposes, and different entities may refer to similar concepts using different names.

[0108] Figure 12An example 1200 of a mapping between a paging message and a SLDT configuration set according to various exemplary embodiments is shown. In example 1200, a paging message 1210 for UE 110 is shown at time slot (T#n). Based on broadcast or dedicated SLDT configuration information, the paging message is mapped to one of a plurality of SLDT configuration sets. In this example, the SLDT configuration set indicates the radio resources for downlink data 1220 to be transmitted to UE 110 at the second time slot (T#n+x), where the value of x is indicated by the SLDT configuration information. Similarly, the SLDT configuration set includes radio resources for uplink data 1230 to be transmitted by UE 110 at the third time slot (T#n+y), where the value of y is also indicated by the SLDT configuration information. Example 1200 is provided as an example of an SLDT configuration set and is not intended to limit the exemplary embodiments in any way.

[0109] As indicated above, there may be multiple SLDT configuration sets, each to be used by a different UE. In one exemplary scenario, the mapping between the paged UE and the SLDT configuration set may be indicated by the UE order in the paging message. For example, consider the following scenario: multiple UEs are paged in the same paging message, and the SLDT configuration sets are indexed from 0 to N. The first UE to be paged in the paging message for the SLDT connection may have an implicit mapping with the SLDT configuration set indexed 0. The next UE to be paged in the same paging message for the SLDT connection may have an implicit mapping with SLDT configuration set 1. Therefore, the order in which the UEs are paged in the same paging message for the SLDT connection may indicate which SLDT configuration set to use for the UE.

[0110] In another exemplary aspect, the mapping between the paged UE and the SLDT configuration set may be explicitly provided in the paging message. Figure 13 An example of a paging record that may be provided in a paging message according to various exemplary embodiments is shown 1300. The paging record may include a UE identity and SLDT information (SLDT-info).

[0111] SLDT-info may include an sldtType parameter configured to indicate whether SLDT connection Type 1 or SLDT connection Type 2 will be utilized, and an sldtDirection parameter configured to indicate whether the SLDT connection is for uplink only, downlink only, or both. Furthermore, SLDT-info may include an sldtConfigIdx parameter configured to indicate the index of the SLDT configuration set to be used by the UE. This parameter may be a value from 0 to the maximum number of SLDT configuration sets (maxNrOfSldtConfigSets). Furthermore, SLDT-info may include an sldtConfigType parameter configured to indicate whether the SLDT resources are static or dynamic. Example 1300 is provided as an example of an SLDT configuration set and is not intended to limit the exemplary embodiments in any way.

[0112] In another exemplary embodiment, the UE may be pre-configured with a semi-dedicated SLDT configuration. With this embodiment, the UE 110 may apply the pre-configured SLDT configuration in response to the paging message. The above exemplary embodiments are provided as examples and are not intended to limit the exemplary embodiments in any way. The exemplary embodiments may provide the UE with SLDT configuration information to indicate which radio resources will be used by the UE 110 during the SLDT connection in any suitable manner.

[0113] Because the use of an SLDT configuration set by a UE is triggered by a mobile terminal connection message (e.g., paging), if the SLDT configuration set is not to be used by any UE, the network can utilize the corresponding radio resources for other radio activities. For example, a base station may have a relatively large number of SLDT configuration sets configured / broadcasted. If there are no UEs scheduled to use the SLDT configuration set, their corresponding resources can be used by the network for any other purpose. Therefore, whether the SLDT radio resources are used for SLDT connections or for other activities is under network control.

[0114] Figure 14 An example 1400 of static allocation of resources for SLDT according to various exemplary embodiments is shown. With this approach, SLDT configuration information defines radio resources and parameters that can be used for uplink and / or downlink data transmission. For example, the SLDT configuration information may indicate physical resource blocks (PRBs), time domain information (e.g., time slots, symbols, etc.), and their repetition patterns. Furthermore, the SLDT configuration information may include receive (RX) / transmit (TX) parameters, such as modulation and channel coding schemes. The information provided by the network means that the UE 110 will perform minimal physical layer activity. For example, the UE 110 does not need to monitor physical layer common control channels for grants because the UE 110 is configured based on the SLDT configuration information.

[0115] In example 1400, a paging message including SLDT configuration information for UE-1 and UE-3 is provided at time slot (T#n). The paging message also includes information for a UE (UE-2) that is not configured for SLDT. In this example, the paging record for UE-1 is mapped to SLDT configuration set #1, and the paging message for UE-3 is mapped to SLDT configuration set #2.

[0116] SLDT configuration set #1 is mapped to the radio resources shown in example 1400 at time slots (T#n+x), (T#n+y), and (T#n+z). At time slot (T#n+x), downlink resources are allocated to UE-1 for downlink data. At time slot (T#n+y), uplink resources are allocated to UE-1 for uplink data, and uplink resources are allocated for downlink data feedback. At time slot (T#n+z), downlink resources are allocated to UE-1 for uplink data feedback.

[0117] SLDT configuration set #2 is mapped to the radio resources shown in example 1400 at time slots (T#n+x), (T#n+y), and (T#n+z). At time slot (T#n+x), downlink resources are allocated to UE-3 for downlink data. At time slot (T#n+y), uplink resources are allocated to UE-3 for uplink data, and uplink resources are allocated for downlink data feedback. At time slot (T#n+z), downlink resources are allocated to UE-3 for uplink data feedback.

[0118] In example 1400 , SLDT configuration set #3 and SLDT configuration set #4 are not assigned to any UE, and thus the network may use the corresponding radio resources for any other appropriate purpose.

[0119] Figure 15 An example 1500 of dynamic allocation of resources for SLDT according to various exemplary embodiments is shown. With this approach, SLDT configuration information defines the minimum amount of information required to perform SLDT. For example, the SLDT configuration information may include a radio network temporary identifier (RNTI) corresponding to an SLDT configuration set. UE 110 may then monitor a physical layer common control channel (e.g., a physical downlink common control channel (PDCCH), etc.) for radio resource assignments associated with the corresponding identifier.

[0120] In example 1500, a paging message including SLDT configuration information for UE-1 and UE-3 is provided at the first time slot (T#n). The paging message also includes information for a UE (UE-2) that is not using SLDT. In this example, the paging record for UE-1 is mapped to SLDT configuration set #1 corresponding to RNTI#1, and the paging message for UE-3 is mapped to SLDT configuration set #2 corresponding to RNTI#2.

[0121] RNTI#1 is used to transmit a downlink grant 1510 to UE-1 at time slot (T#n+x). Downlink grant 1510 may indicate that downlink data 1512 will also be transmitted to UE-1 during time slot (T#n+x). RNTI#1 may also be used to transmit an uplink grant 1515 to UE-1 at time slot (T#n+y). Uplink grant 1515 may indicate that uplink data 1517 will be transmitted by UE-1 at time slot (T#n+z). Although not shown in example 1500, the radio resources used for downlink data feedback may have a predefined offset relative to downlink data 1512 or may be indicated to UE 110 in downlink grant 1510 or uplink grant 1515. Similarly, the radio resources used for uplink data feedback may have a predefined offset relative to uplink data 1517 or may be indicated to UE 110 in downlink grant 1510 or uplink grant 1515 .

[0122] RNTI #2 is used to transmit a downlink grant 1550 to UE-3 at time slot (T#n+x). Downlink grant 1550 may indicate that downlink data 1552 will also be transmitted to UE-3 during time slot (T#n+x). RNTI #2 may also be used to transmit an uplink grant 1555 to UE-2 at time slot (T#n+y). Uplink grant 1555 may indicate that uplink data 1557 will be transmitted by UE-3 at time slot (T#n+z). Although not shown in example 1500, the radio resources used for downlink data feedback may have a predefined offset relative to downlink data 1552 or may be indicated to UE 110 in downlink grant 1550 or uplink grant 1555. Similarly, the radio resources used for uplink data feedback may have a predefined offset relative to uplink data 1557 or may be indicated to UE 110 in downlink grant 1550 or uplink grant 1555 .

[0123] Example

[0124] In a first embodiment, a method performed by a user equipment (UE), the method comprising: receiving configuration information comprising a plurality of configuration sets; receiving a paging message from a base station, the paging message being configured to initiate a mobile terminal connection between the UE and the base station; identifying a first configuration set assigned to the UE from the plurality of configuration sets based on the paging message; and using the first configuration set to exchange data with a network, wherein exchanging data with the network comprises at least one of receiving downlink data and transmitting uplink data.

[0125] In a second embodiment, the method according to the first embodiment, wherein the paging message indicates a first type of mobile terminal connection from a set of two different types of mobile terminal connections.

[0126] In a third embodiment, according to the method of the second embodiment, the first type of mobile terminal connection is configured to include a plurality of messages, the plurality of messages including at least: a downlink message including downlink data or an uplink message including uplink data.

[0127] In a fourth embodiment, the method of the third embodiment is according to which the paging is a first message of the first type of mobile terminating connection and a second message of the first type of mobile terminating connection includes the downlink data.

[0128] In a fifth embodiment, the method according to the fourth embodiment, wherein the second message further includes a downlink assignment for the downlink data.

[0129] In a sixth embodiment, according to the method of the fourth embodiment, the second message further includes downlink data feedback in response to the downlink data.

[0130] In a seventh embodiment, the method according to the third embodiment, wherein the paging is a first message of the first type of mobile terminating connection, and a second message of the first type of mobile terminating connection includes the uplink data.

[0131] In an eighth embodiment, the method according to the seventh embodiment, wherein the second message further includes an uplink assignment for the uplink data.

[0132] In a ninth embodiment, according to the method of the seventh embodiment, the second message further includes uplink data feedback in response to the uplink data.

[0133] In a tenth embodiment, the method according to the first embodiment, wherein identifying the first configuration assigned to the UE is based on a UE order in the paging message, wherein the UE order corresponds to a configuration set index.

[0134] In an eleventh embodiment, the method according to the first embodiment, wherein identifying the first configuration assigned to the UE is based on a configuration set index value included in the paging message.

[0135] In a twelfth embodiment, the method according to the first embodiment, wherein the first configuration set defines radio resources to be used to exchange data with the network.

[0136] In a thirteenth embodiment, according to the method of the first embodiment, the first configuration set further includes transmission (TX) or reception (RX) parameters for the mobile terminal connection.

[0137] In a fourteenth embodiment, the method according to the first embodiment, wherein the first configuration set includes a UE identifier to be used by the network to address downlink assignments or uplink assignments transmitted to the UE during the mobile terminal connection.

[0138] In a fifteenth embodiment, according to the method of the first embodiment, the method further includes identifying a condition that triggers a stationed mode for the UE, and transmitting a stationed mode request to the base station, the stationed mode request including information associated with a serving cell or a location of the UE, wherein the network uses the information associated with the serving cell or the location of the UE to select the base station for providing the paging message to the UE.

[0139] In a sixteenth embodiment, according to the method of the fifteenth embodiment, the method further comprises transmitting a message to the base station, the message indicating that the UE has exited the stationed mode.

[0140] In a seventeenth embodiment, according to the method of the fifteenth embodiment, the method further comprises transmitting a message to the base station, the message including updated serving cell information or updated location information for stationary mode.

[0141] In an eighteenth embodiment, according to the method of the first embodiment, the method further comprises receiving a command from the network, the command indicating the end of the mobile terminal connection.

[0142] In a nineteenth embodiment, according to the method of the first embodiment, the UE is configured to end the mobile terminal connection in response to expiration of a timer.

[0143] In a twentieth embodiment, the method according to the first embodiment, wherein exchanging data with the network includes receiving downlink data repetitions.

[0144] In a twenty-first embodiment, according to the method of the ninth embodiment, the second message further includes one or more retransmissions in response to the uplink data feedback.

[0145] In a twenty-second embodiment, the method according to the first embodiment, wherein the first configuration set includes radio resources that the UE is to monitor for uplink or downlink radio resource assignments.

[0146] In a twenty-third embodiment, the method according to the first embodiment, wherein the first configuration set includes an indication of physical resource blocks (PRBs), time domain information, and a repetition pattern.

[0147] In a twenty-fourth embodiment, a method performed by a base station includes: transmitting a paging message to a user equipment (UE), wherein the paging message is configured to initiate a mobile terminal connection between the UE and the base station; identifying a first configuration set assigned to the UE from a plurality of configuration sets; and using the first configuration set to exchange data with the UE, wherein exchanging data with a network includes at least one of receiving downlink data and transmitting uplink data.

[0148] In a twenty-fifth embodiment, according to the method of the twenty-fourth embodiment, the method further includes transmitting configuration information including the multiple configuration sets to the UE in a system information block (SIB).

[0149] In a twenty-sixth embodiment, according to the method of the twenty-fourth embodiment, the method further includes transmitting configuration information including the multiple configuration sets to the UE in a dedicated message.

[0150] In a twenty-seventh embodiment, according to the method of the twenty-fourth embodiment, the first configuration set is assigned only to the UE during the mobile terminal connection.

[0151] In a twenty-eighth embodiment, the method according to the twenty-fourth embodiment, wherein the radio resources corresponding to the first configuration set can be used for any radio activity when the mobile terminal connection utilizing these resources is not assigned to any UE.

[0152] In a twenty-ninth embodiment, according to the method of the twenty-fourth embodiment, the method further includes receiving a paging request from a core network based on a cell that previously served as a serving cell for the UE.

[0153] In a thirtieth embodiment, according to the method of the twenty-ninth embodiment, the UE transmits an indication of UE stationary mode to the core network via a previous connection between the UE and the base station.

[0154] In a thirty-first embodiment, the method according to the twenty-fourth embodiment is described, wherein the data payload structure for the mobile terminal connection includes a header, user plane data and an integrity code, wherein a non-access stratum (NAS) security context is used for user plane data protection, and wherein the integrity code generated by the NAS layer is used for authentication.

[0155] In a thirty-second embodiment, a method is described according to the twenty-fourth embodiment, wherein the data payload structure for the mobile terminal connection includes a header, user plane data and an integrity code, wherein an access stratum (AS) security context is used for user plane data protection, and wherein the integrity code generated by the AS layer is used for authentication.

[0156] In a thirty-third embodiment, the method according to the twenty-fourth embodiment, wherein the mobile terminal connection is a connection type configured for a maximum number of downlink packets, and wherein the mobile terminal connection ends after receiving the maximum number of downlink packets.

[0157] In a thirty-fourth embodiment, the method according to the twenty-fourth embodiment, wherein the mobile terminal connection is a connection type configured for a maximum number of uplink packets, and wherein the mobile terminal connection ends after transmitting the maximum number of uplink packets.

[0158] In a thirty-fifth embodiment, the method of the twenty-fourth embodiment, wherein the paging message indicates a first type of mobile terminal connection from a set of two different types of mobile terminal connections.

[0159] In a thirty-sixth embodiment, the method according to the thirty-fifth embodiment, wherein the first type of mobile terminal connection is configured to include three messages.

[0160] In a thirty-seventh embodiment, the method according to the thirty-fifth embodiment, wherein the paging message is a first message of the first type of mobile terminal connection, and a second message of the first type of mobile terminal connection includes downlink data.

[0161] In a thirty-eighth embodiment, the method according to the thirty-seventh embodiment, wherein the second message further includes a downlink assignment for the downlink data.

[0162] In a thirty-ninth embodiment, the method according to the thirty-fourth embodiment, wherein the paging message is a first message of the first type of mobile terminal connection, and a second message of the first type of mobile terminal connection includes uplink data.

[0163] In a fortieth embodiment, according to the method of the thirty-ninth embodiment, the second message further includes an uplink assignment for the uplink data.

[0164] In a forty-first embodiment, according to the method of the thirty-ninth embodiment, the second message further includes uplink information for uplink data processing at the base station.

[0165] In a forty-second embodiment, the method according to the thirty-fourth embodiment, wherein the first type of mobile terminal connection is configured to include at least four messages.

[0166] In a forty-third embodiment, the method according to the forty-second embodiment, wherein the paging message is a first message of the first type of mobile terminal connection, and the second message of the first type of mobile terminal connection includes initial information to be used by the network for radio resource management.

[0167] In a forty-fourth embodiment, the method according to the forty-third embodiment, wherein the initial information includes at least one of a preamble and channel state information (CSI).

[0168] In a forty-fifth embodiment, the method according to the forty-fourth embodiment, wherein the paging is a first message of the first type of mobile terminating connection, and a second message of the first type of mobile terminating connection includes downlink data.

[0169] In a forty-sixth embodiment, the method according to the forty-fifth embodiment, wherein the second message further includes a downlink assignment for the downlink data.

[0170] In a forty-seventh embodiment, according to the method of the thirty-fifth embodiment, the second message further includes downlink data feedback in response to the downlink data.

[0171] In a forty-eighth embodiment, the method according to the forty-second embodiment, wherein the paging is a first message of the first type of mobile terminal connection, and a second message of the first type of mobile terminal connection includes uplink data.

[0172] In a forty-ninth embodiment, the method according to the forty-eighth embodiment, wherein the second message further includes an uplink assignment for the uplink data.

[0173] In a fiftieth embodiment, according to the method of the forty-eighth embodiment, the second message further includes uplink data feedback in response to the uplink data.

[0174] In a fifty-first embodiment, according to the method of the twenty-fourth embodiment, the first configuration assigned to the UE is indicated to the UE based on a UE order in the paging message, wherein the UE order corresponds to a configuration set index.

[0175] In a fifty-second embodiment, according to the method of the twenty-fourth embodiment, the first configuration assigned to the UE is indicated to the UE based on a configuration set index value included in the paging message.

[0176] In a fifty-third embodiment, the method according to the twenty-fourth embodiment, wherein the first configuration set defines radio resources to be used to exchange data with the UE.

[0177] In a fifty-fourth embodiment, according to the method of the twenty-fourth embodiment, the first configuration set further includes transmission (TX) or reception (RX) parameters for the mobile terminal connection.

[0178] In a fifty-fifth embodiment, the method according to the twenty-fourth embodiment, wherein the first configuration set includes a UE identifier, which is used by the network to address downlink assignments or uplink assignments transmitted to the UE during the connection of the mobile terminal.

[0179] In a fifty-sixth embodiment, according to the method of the twenty-fourth embodiment, the method further includes transmitting a command to the UE, the command indicating the end of the mobile terminal connection.

[0180] In a fifty-seventh embodiment, according to the method of the twenty-fourth embodiment, the UE is configured to end the mobile terminal connection in response to expiration of a timer.

[0181] In a fifty-eighth embodiment, according to the method of the twenty-fourth embodiment, exchanging data with the UE includes transmitting downlink data repetitions.

[0182] In a fifty-ninth embodiment, the method according to the twenty-fourth embodiment, wherein the first configuration set includes radio resources that the UE is to monitor for uplink or downlink radio resource assignments.

[0183] In a sixtieth embodiment, the method according to the twenty-fourth embodiment, wherein the first configuration set includes an indication of physical resource blocks (PRBs), time domain information, and a repetition pattern.

[0184] Those skilled in the art will appreciate that the exemplary embodiments described above can be implemented with any suitable software configuration or hardware configuration or combination thereof. Exemplary hardware platforms for implementing the exemplary embodiments may include, for example, Intel x86-based platforms with compatible operating systems, Windows OS, Mac platforms and MAC OS, mobile devices with operating systems such as iOS, Android, etc. The exemplary embodiments described above may be embodied as a program comprising lines of code stored on a non-transitory computer-readable storage medium, which, when compiled, can be executed on a processor or microprocessor.

[0185] Although this application describes various embodiments, each having different features in various combinations, those skilled in the art will understand that any feature of one embodiment may be combined with features of other embodiments in any manner that is not expressly disavowed or that is not functionally or logically inconsistent with the operation of the device or the stated function of the disclosed embodiment.

[0186] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly stated to users.

[0187] It will be apparent to those skilled in the art that various modifications may be made to the present disclosure without departing from the spirit or scope of the present disclosure. Therefore, it is intended that the present disclosure covers modifications and variations of the present disclosure as long as they come within the scope of the appended claims and their equivalents.

Claims

1. A method comprising: At the User Equipment (UE): receiving configuration information including a plurality of configuration sets; receiving a paging message from a base station, the paging message being configured to initiate a mobile terminal connection between the UE and the base station; identifying, based on the paging message, a first configuration set assigned to the UE from the plurality of configuration sets; as well as Data is exchanged with a network using the first configuration set, wherein exchanging data with the network includes at least one of receiving downlink data and transmitting uplink data. 2 . The method of claim 1 , wherein the configuration information including the plurality of configuration sets is received in a system information block (SIB). 3 . The method of claim 1 , wherein the configuration information including the plurality of configuration sets is received from the base station in a dedicated message. 4 . The method of claim 1 , wherein the first configuration set is assigned only to the UE during the mobile terminal connection.

5. The method according to claim 1, further comprising: receiving the paging message from a plurality of cells; selecting a first cell among the plurality of cells for connection by the mobile terminal; as well as A signal is transmitted to the first cell, wherein the signal indicates to a network which cell of the plurality of cells is to be used for the mobile terminal connection.

6. The method of claim 1 , wherein the data payload structure for the mobile terminal connection comprises a header, user plane data, and an integrity code, Wherein the non-access stratum (NAS) security context is used for user plane data protection, and The integrity code generated by the NAS layer is used for authentication.

7. The method of claim 1 , wherein the data payload structure for the mobile terminal connection comprises a header, user plane data, and an integrity code, The access stratum (AS) security context is used for user plane data protection, and the integrity code generated by the AS layer is used for authentication.

8. The method of claim 1, wherein the mobile terminal connection is a connection type configured for a maximum number of downlink packets, and wherein the mobile terminal connection ends after receiving the maximum number of downlink packets.

9. The method of claim 1, wherein the mobile terminal connection is a connection type configured for a maximum number of uplink packets, and wherein the mobile terminal connection ends after transmitting the maximum number of uplink packets.

10. The method of claim 1, wherein the paging message indicates a first type of mobile terminal connection from a set of two different types of mobile terminal connections. The method of claim 10 , wherein the first type of mobile terminal connection is configured to include three messages.

12. The method of claim 10, wherein the paging message is a first message of the first type of mobile terminal connection and a second message of the first type of mobile terminal connection includes downlink data.

13. The method of claim 12, wherein the second message further includes a downlink assignment for the downlink data.

14. The method of claim 10, wherein the paging message is a first message of the first type of mobile terminal connection and a second message of the first type of mobile terminal connection includes uplink data. The method of claim 14 , wherein the second message further comprises an uplink assignment for the uplink data.

16. The method of claim 14, wherein the second message further includes uplink information for uplink data processing at the base station.

17. The method according to claim 10, wherein the first type of mobile terminal connection is configured to include a plurality of messages, the plurality of messages including at least: A downlink message including downlink data or an uplink message including uplink data.

18. The method of claim 17, wherein the paging message is a first message of the first type of mobile terminal connection, and a second message of the first type of mobile terminal connection includes initial information to be used by the network for radio resource management.

19. The method of claim 18, wherein the initial information comprises at least one of a preamble, channel state information (CSI), and an indication of an amount of pending uplink data.

20. The method of claim 17, wherein the paging is a first message of the first type of mobile terminating connection and a second message of the first type of mobile terminating connection includes the downlink data.

Images