Ambient IoT service management

Abstract

A wireless device sends, to an access and mobility management function (AMF), a registration request message indicating an ambient internet of things (AloT) reader capability. The wireless sdevice receives, from the AMF, a registration accept message, and from a AloT device, a failure message comprising a cause value indicating insufficient energy to complete a writing command. The wireless device sends, to an AloT function (AIOTF), the cause value.

Description

Docket No.: 24-1271 PCTTITLEAmbient loT Service ManagementCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 733,439, filed December12, 2024, which is hereby incorporated by reference in its entirety.BRIEF DESCRIPTION OF THE DRAWINGS

[0002] Examples of several of the various embodiments of the present disclosure are described herein with reference to the drawings.

[0003] FIG. 1A and FIG. 1B illustrate example communication networks including an access network and a core network.

[0004] FIG. 2A, FIG. 2B, FIG. 2C, and FIG. 2D illustrate various examples of a framework for a servicebased architecture within a core network.

[0005] FIG. 3 illustrates an example communication network including core network functions.

[0006] FIG. 4A and FIG. 4B illustrate example of core network architecture with multiple user plane functions and untrusted access.

[0007] FIG. 5 illustrates an example of a core network architecture for a roaming scenario.

[0008] FIG. 6 illustrates an example of network slicing.

[0009] FIG. 7A, FIG. 7B, and FIG. 7C illustrate a user plane protocol stack, a control plane protocol stack, and services provided between protocol layers of the user plane protocol stack.

[0010] FIG. 8 illustrates an example of a quality of service model for data exchange.

[0011] FIG. 9A, FIG. 9B, FIG. 9C, and FIG. 9D illustrate example states and state transitions of a wireless device.

[0012] FIG. 10 illustrates an example of a registration procedure for a wireless device.

[0013] FIG. 11 illustrates an example of a service request procedure for a wireless device.

[0014] FIG. 12 illustrates an example of a protocol data unit session establishment procedure for a wireless device.

[0015] FIG. 13 illustrates examples of components of the elements in a communications network.

[0016] FIG. 14A, FIG. 14B, FIG. 14C, and FIG. 14D illustrate various examples of physical core network deployments, each having one or more network functions or portions thereof.

[0017] FIG. 15 is a diagram of an aspect of an example embodiment of the present disclosure.

[0018] FIG. 16 is a diagram of an aspect of an example embodiment of the present disclosure.

[0019] FIG. 17 is a diagram of an aspect of an example embodiment of the present disclosure.

[0020] FIG. 18 is a diagram of an aspect of an example embodiment of the present disclosure.

[0021] FIG. 19A, 19B, 19C, 19D and 19E is a diagram of an aspect of an example embodiment of the present disclosure.Docket No.: 24-1271 PCT

[0022] FIG. 20 is a diagram of an aspect of an example embodiment of the present disclosure.

[0023] FIG. 21 A and 21 B is a diagram of an aspect of an example embodiment of the present disclosure.

[0024] FIG. 22 is a diagram of an aspect of an example embodiment of the present disclosure.

[0025] FIG. 23 is a diagram of an aspect of an example embodiment of the present disclosure.

[0026] FIG. 24 is a diagram of an aspect of an example embodiment of the present disclosure.

[0027] FIG. 25 is a diagram of an aspect of an example embodiment of the present disclosure.

[0028] FIG. 26 is a diagram of an aspect of an example embodiment of the present disclosure.

[0029] FIG. 27 is a diagram of an aspect of an example embodiment of the present disclosure.

[0030] FIG. 28 is a diagram of an aspect of an example embodiment of the present disclosure.DETAILED DESCRIPTION

[0031] In the present disclosure, various embodiments are presented as examples of how the disclosed techniques may be implemented and / or how the disclosed techniques may be practiced in environments and scenarios. It will be apparent to persons skilled in the relevant art that various changes in form and detail can be made therein without departing from the scope. In fact, after reading the description, it will be apparent to one skilled in the relevant art how to implement alternative embodiments. The present embodiments should not be limited by any of the described exemplary embodiments. The embodiments of the present disclosure will be described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed example embodiments may be combined to create further embodiments within the scope of the disclosure. Any figures which highlight the functionality and advantages are presented for example purposes only. The disclosed architecture is sufficiently flexible and configurable, such that it may be utilized in ways other than that shown. For example, the actions listed in any flowchart may be re-ordered or only optionally used in some embodiments.

[0032] Embodiments may be configured to operate as needed. The disclosed mechanism may be performed when certain criteria are met, for example, in a wireless device, a base station, a radio environment, a network, a combination of the above, and / or the like. Example criteria may be based, at least in part, on for example, wireless device or network node configurations, traffic load, initial system set up, packet sizes, traffic characteristics, a combination of the above, and / or the like. When the one or more criteria are met, various example embodiments may be applied. Therefore, it may be possible to implement example embodiments that selectively implement disclosed protocols.

[0033] A base station may communicate with a mix of wireless devices. Wireless devices and / or base stations may support multiple technologies, and / or multiple releases of the same technology. Wireless devices may have one or more specific capabilities. When this disclosure refers to a base station communicating with a plurality of wireless devices, this disclosure may refer to a subset of the total wireless devices in a coverage area. This disclosure may refer to, for example, a plurality of wireless devices of a given LTE or 5G release with a given capability and in a given sector of the base station. The plurality ofDocket No.: 24-1271 PCT wireless devices in this disclosure may refer to a selected plurality of wireless devices, and / or a subset of total wireless devices in a coverage area which perform according to disclosed methods, and / or the like. There may be a plurality of base stations or a plurality of wireless devices in a coverage area that may not comply with the disclosed methods, for example, those wireless devices or base stations may perform based on older releases of LTE or 5G technology.

[0034] In this disclosure, "a” and “an” and similar phrases refer to a single instance of a particular element, but should not be interpreted to exclude other instances of that element. For example, a bicycle with two wheels may be described as having “a wheel”. Any term that ends with the suffix “(s)” is to be interpreted as “at least one" and / or “one or more.” In this disclosure, the term “may” is to be interpreted as “may, for example.” In other words, the term “may” is indicative that the phrase following the term “may” is an example of one of a multitude of suitable possibilities that may, or may not, be employed by one or more of the various embodiments. The terms “comprises” and “consists of’, as used herein, enumerate one or more components of the element being described. The term “comprises" is interchangeable with “includes” and does not exclude unenumerated components from being included in the element being described. By contrast, “consists of’ provides a complete enumeration of the one or more components of the element being described.

[0035] The phrases “based on”, “in response to”, “depending on”, “employing”, “using”, and similar phrases indicate the presence and / or influence of a particular factor and / or condition on an event and / or action, but do not exclude unenumerated factors and / or conditions from also being present and / or influencing the event and / or action. For example, if action X is performed “based on” condition Y, this is to be interpreted as the action being performed “based at least on” condition Y. For example, if the performance of action X is performed when conditions Y and Z are both satisfied, then the performing of action X may be described as being “based on Y”.

[0036] The term “configured” may relate to the capacity of a device whether the device is in an operational or non-operational state. Configured may refer to specific settings in a device that affect the operational characteristics of the device whether the device is in an operational or non-operational state. In other words, the hardware, software, firmware, registers, memory values, and / or the like may be “configured" within a device, whether the device is in an operational or nonoperational state, to provide the device with specific characteristics. Terms such as “a control message to cause in a device” may mean that a control message has parameters that may be used to configure specific characteristics or may be used to implement certain actions in the device, whether the device is in an operational or non-operational state.

[0037] In this disclosure, a parameter may comprise one or more information objects, and an information object may comprise one or more other objects. For example, if parameter J comprises parameter K, and parameter K comprises parameter L, and parameter L comprises parameter M, then J comprises L, and J comprises M. A parameter may be referred to as a field or information element. In an exampleDocket No.: 24-1271 PCT embodiment, when one or more messages comprise a plurality of parameters, it implies that a parameter in the plurality of parameters is in at least one of the one or more messages, but does not have to be in each of the one or more messages.

[0038] This disclosure may refer to possible combinations of enumerated elements. For the sake of brevity and legibility, the present disclosure does not explicitly recite each and every permutation that may be obtained by choosing from a set of optional features. The present disclosure is to be interpreted as explicitly disclosing all such permutations. For example, the seven possible combinations of enumerated elements A, B, C consist of: (1) “A”; (2) “B”; (3) “C”; (4) “A and B”; (5) "A and C”; (6) “B and C”; and (7) “A, B, and C". For the sake of brevity and legibility, these seven possible combinations may be described using any of the following interchangeable formulations: “at least one of A, B, and C”; “at least one of A, B, or C”; “one or more of A, B, and C”; “one or more of A, B, or C”; “A, B, and / or C”. It will be understood that impossible combinations are excluded. For example, “X and / or not-X” should be interpreted as “X or not-X”. It will be further understood that these formulations may describe alternative phrasings of overlapping and / or synonymous concepts, for example, “identifier, identification, and / or ID number”.

[0039] This disclosure may refer to sets and / or subsets. As an example, set X may be a set of elements comprising one or more elements. If every element of X is also an element of Y, then X may be referred to as a subset of Y. In this disclosure, only non-empty sets and subsets are considered. For example, if Y consists of the elements Y1 , Y2, and Y3, then the possible subsets of Y are {Y1 , Y2, Y3}, {Y1 , Y2}, {Y1 , Y3}, {Y2, Y3}, {Y1 }, {Y2}, and {Y3}.

[0040] FIG. 1A illustrates an example of a communication network 100 in which embodiments of the present disclosure may be implemented. The communication network 100 may comprise, for example, a public land mobile network (PLMN) run by a network operator. As illustrated in FIG. 1A, the communication network 100 includes a wireless device 101 , an access network (AN) 102, a core network (CN) 105, and one or more data network (DNs) 108.

[0041] The wireless device 101 may communicate with DNs 108 via AN 102 and CN 105. In the present disclosure, the term wireless device may refer to and encompass any mobile device or fixed (non-mobile) device for which wireless communication is needed or usable. For example, a wireless device may be a telephone, smart phone, tablet, computer, laptop, sensor, meter, wearable device, Internet of Things (loT) device, vehicle roadside unit (RSU), relay node, automobile, unmanned aerial vehicle, urban air mobility, and / or any combination thereof. The term wireless device encompasses other terminology, including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, handset, wireless transmit and receive unit (WTRU), and / or wireless communication device.

[0042] The AN 102 may connect wireless device 101 to CN 105 in any suitable manner. The communication direction from the AN 102 to the wireless device 101 is known as the downlink and the communication direction from the wireless device 101 to AN 102 is known as the uplink. DownlinkDocket No.: 24-1271 PCT transmissions may be separated from uplink transmissions using frequency division duplexing (FDD), timedivision duplexing (TDD), and / or some combination of the two duplexing techniques. The AN 102 may connect to wireless device 101 through radio communications over an air interface. An access network that at least partially operates over the air interface may be referred to as a radio access network (RAN). The CN 105 may set up one or more end-to-end connection between wireless device 101 and the one or more DNs 108. The CN 105 may authenticate wireless device 101 and provide charging functionality.

[0043] In the present disclosure, the term base station may refer to and encompass any element of AN 102 that facilitates communication between wireless device 101 and AN 102. Access networks and base stations have many different names and implementations. The base station may be a terrestrial base station fixed to the earth. The base station may be a mobile base station with a moving coverage area. The base station may be in space, for example, on board a satellite. For example, WiFi and other standards may use the term access point. As another example, the Third-Generation Partnership Project (3GPP) has produced specifications for three generations of mobile networks, each of which uses different terminology. Third Generation (3G) and / or Universal Mobile Telecommunications System (UMTS) standards may use the term Node B. 4G, Long Term Evolution (LTE), and / or Evolved Universal Terrestrial Radio Access (E- UTRA) standards may use the term Evolved Node B (eNB). 5G and / or New Radio (NR) standards may describe AN 102 as a next-generation radio access network (NG-RAN) and may refer to base stations as Next Generation eNB (ng-eNB) and / or Generation Node B (gNB). Future standards (for example, 6G, 7G, 8G) may use new terminology to refer to the elements which implement the methods described in the present disclosure (e g., wireless devices, base stations, ANs, CNs, and / or components thereof). A base station may be implemented as a repeater or relay node used to extend the coverage area of a donor node. A repeater node may amplify and rebroadcast a radio signal received from a donor node. A relay node may perform the same / similar functions as a repeater node but may decode the radio signal received from the donor node to remove noise before amplifying and rebroadcasting the radio signal.

[0044] The AN 102 may include one or more base stations, each having one or more coverage areas. The geographical size and / or extent of a coverage area may be defined in terms of a range at which a receiver of AN 102 can successfully receive transmissions from a transmitter (e.g., wireless device 101) operating within the coverage area (and / or vice-versa). The coverage areas may be referred to as sectors or cells (although in some contexts, the term cell refers to the carrier frequency used in a particular coverage area, rather than the coverage area itself). Base stations with large coverage areas may be referred to as macrocell base stations. Other base stations cover smaller areas, for example, to provide coverage in areas with weak macrocell coverage, or to provide additional coverage in areas with high traffic (sometimes referred to as hotspots). Examples of small cell base stations include, in order of decreasing coverage area, microcell base stations, picocell base stations, and femtocell base stations or home base stations. Together, the coverage areas of the base stations may provide radio coverage to wireless device 101 overDocket No.: 24-1271 PCT a wide geographic area to support wireless device mobility.

[0045] A base station may include one or more sets of antennas for communicating with the wireless device 101 over the air interface. Each set of antennas may be separately controlled by the base station. Each set of antennas may have a corresponding coverage area. As an example, a base station may include three sets of antennas to respectively control three coverage areas on three different sides of the base station. The entirety of the base station (and its corresponding antennas) may be deployed at a single location. Alternatively, a controller at a central location may control one or more sets of antennas at one or more distributed locations. The controller may be, for example, a baseband processing unit that is part of a centralized or cloud RAN architecture. The baseband processing unit may be either centralized in a pool of baseband processing units or virtualized. A set of antennas at a distributed location may be referred to as a remote radio head (RRH).

[0046] FIG. 1 B illustrates another example communication network 150 in which embodiments of the present disclosure may be implemented. The communication network 150 may comprise, for example, a PLMN run by a network operator. As illustrated in FIG. 1 B, communication network 150 includes UEs 151 , a next generation radio access network (NG-RAN) 152, a 5G core network (5G-CN) 155, and one or more DNs 158. The NG-RAN 152 includes one or more base stations, illustrated as generation node Bs (gNBs) 152A and next generation evolved Node Bs (ng eNBs) 152B. The 5G-CN 155 includes one or more network functions (NFs), including control plane functions 155A and user plane functions 155B. The one or more DNs 158 may comprise public DNs (e.g., the Internet), private DNs, and / or intra-operator DNs. Relative to corresponding components illustrated in FIG. 1 A, these components may represent specific implementations and / or terminology.

[0047] The base stations of the NG-RAN 152 may be connected to the UEs 151 via Uu interfaces. The base stations of the NG-RAN 152 may be connected to each other via Xn interfaces. The base stations of the NG-RAN 152 may be connected to 5G CN 155 via NG interfaces. The Uu interface may include an air interface. The NG and Xn interfaces may include an air interface, or may consist of direct physical connections and / or indirect connections over an underlying transport network (e.g., an internet protocol (IP) transport network).

[0048] Each of the Uu, Xn, and NG interfaces may be associated with a protocol stack. The protocol stacks may include a user plane (UP) and a control plane (CP). Generally, user plane data may include data pertaining to users of the UEs 151 , for example, internet content downloaded via a web browser application, sensor data uploaded via a tracking application, or email data communicated to or from an email server. Control plane data, by contrast, may comprise signaling and messages that facilitate packaging and routing of user plane data so that it can be exchanged with the DN(s). The NG interface, for example, may be divided into an NG user plane interface (NG-U) and an NG control plane interface (NG- C). The NG-U interface may provide delivery of user plane data between the base stations and the one orDocket No.: 24-1271 PCT more user plane network functions 155B. The NG-C interface may be used for control signaling between the base stations and the one or more control plane network functions 155A. The NG-C interface may provide, for example, NG interface management, UE context management, UE mobility management, transport of NAS messages, paging, PDU session management, and configuration transfer and / or warning message transmission. In some cases, the NG-C interface may support transmission of user data (for example, a small data transmission for an loT device).

[0049] One or more of the base stations of the NG-RAN 152 may be split into a central unit (CU) and one or more distributed units (DUs). A CU may be coupled to one or more DUs via an F1 interface. The CU may handle one or more upper layers in the protocol stack and the DU may handle one or more lower layers in the protocol stack. For example, the CU may handle RRC, PDCP, and SDAP, and the DU may handle RLC, MAC, and PHY. The one or more DUs may be in geographically diverse locations relative to the CU and / or each other. Accordingly, the CU / DU split architecture may permit increased coverage and / or better coordination.

[0050] The gNBs 152A and ng-eNBs 152B may provide different user plane and control plane protocol termination towards the UEs 151. For example, the gNB 154A may provide new radio (NR) protocol terminations over a Uu interface associated with a first protocol stack. The ng-eNBs 152B may provide Evolved UMTS Terrestrial Radio Access (E-UTRA) protocol terminations over a Uu interface associated with a second protocol stack.

[0051] The 5G-CN 155 may authenticate UEs 151 , set up end-to-end connections between UEs 151 and the one or more DNs 158, and provide charging functionality. The 5G-CN 155 may be based on a servicebased architecture, in which the NFs making up the 5G-CN 155 offer services to each other and to other elements of the communication network 150 via interfaces. The 5G-CN 155 may include any number of other NFs and any number of instances of each NF.

[0052] FIG. 2A, FIG. 2B, FIG. 2C, and FIG. 2D illustrate various examples of a framework for a servicebased architecture within a core network. In a service-based architecture, a service may be sought by a service consumer and provided by a service producer. Prior to obtaining a particular service, an NF may determine where such a service can be obtained. To discover a service, the NF may communicate with a network repository function (NRF). As an example, an NF that provides one or more services may register with a network repository function (NRF). The NRF may store data relating to the one or more services that the NF is prepared to provide to other NFs in the service-based architecture. A consumer NF may query the NRF to discover a producer NF (for example, by obtaining from the NRF a list of NF instances that provide a particular service).

[0053] In the example of FIG. 2A, an NF 211 (a consumer NF in this example) may send a request 221 to an NF 212 (a producer NF). The request 221 may be a request for a particular service and may be sent based on a discovery that NF 212 is a producer of that service. The request 221 may comprise dataDocket No.: 24-1271 PCT relating to NF 211 and / or the requested service. The NF 212 may receive request 221 , perform one or more actions associated with the requested service (e.g., retrieving data), and provide a response 221 . The one or more actions performed by the NF 212 may be based on request data included in the request 221 , data stored by NF 212, and / or data retrieved by NF 212. The response 222 may notify NF 211 that the one or more actions have been completed. The response 222 may comprise response data relating to NF 212, the one or more actions, and / or the requested service.

[0054] In the example of FIG. 2B, an NF 231 sends a request 241 to an NF 232. In this example, part of the service produced by NF 232 is to send a request 242 to an NF 233. The NF 233 may perform one or more actions and provide a response 243 to NF 232. Based on response 243, NF 232 may send a response 244 to NF 231 . It will be understood from FIG. 2B that a single NF may perform the role of producer of services, consumer of services, or both. A particular NF service may include any number of nested NF services produced by one or more other NFs.

[0055] FIG. 2C illustrates examples of subscribe-notify interactions between a consumer NF and a producer NF. In FIG. 2C, an NF 251 sends a subscription 261 to an NF 252. An NF 253 sends a subscription 262 to the NF 252. Two NFs are shown in FIG. 2C for illustrative purposes (to demonstrate that the NF 252 may provide multiple subscription services to different NFs), but it will be understood that a subscribe-notify interaction only requires one subscriber. The NFs 251 , 253 may be independent from one another. For example, the NFs 251 , 253 may independently discover NF 252 and / or independently determine to subscribe to the service offered by NF 252. In response to receipt of a subscription, the NF 252 may provide a notification to the subscribing NF. For example, NF 252 may send a notification 263 to NF 251 based on subscription 261 and may send a notification 264 to NF 253 based on subscription 262.

[0056] As shown in the example illustration of FIG. 2C, the sending of the notifications 263, 264 may be based on a determination that a condition has occurred. For example, the notifications 263, 264 may be based on a determination that a particular event has occurred, a determination that a particular condition is outstanding, and / or a determination that a duration of time associated with the subscription has elapsed (for example, a period associated with a subscription for periodic notifications). As shown in the example illustration of FIG. 2C, NF 252 may send notifications 263, 264 to NFs 251 , 253 simultaneously and / or in response to the same condition. However, it will be understood that the NF 252 may provide notifications at different times and / or in response to different notification conditions. In an example, the NF 251 may request a notification when a certain parameter, as measured by the NF 252, exceeds a first threshold, and the NF 252 may request a notification when the parameter exceeds a second threshold different from the first threshold. In an example, a parameter of interest and / or a corresponding threshold may be indicated in the subscriptions 261 , 262.

[0057] FIG. 2D illustrates another example of a subscribe-notify interaction. In FIG. 2D, an NF 271 sends a subscription 281 to an NF 272. In response to receipt of subscription 281 and / or a determination that aDocket No.: 24-1271 PCT notification condition has occurred, NF 272 may send a notification 284. The notification 284 may be sent to an NF 273. Unlike the example in FIG. 2C (in which a notification is sent to the subscribing NF), FIG. 2D demonstrates that a subscription and its corresponding notification may be associated with different NFs. For example, NF 271 may subscribe to the service provided by NF 272 on behalf of NF 273.

[0058] FIG. 3 illustrates another example communication network 300 in which embodiments of the present disclosure may be implemented. Communication network 300 includes a user equipment (UE) 301 , an access network (AN) 302, and a data network (DN) 308. The remaining elements depicted in FIG. 3 may be included in and / or associated with a core network. Each element of the core network may be referred to as a network function (NF).

[0059] The NFs depicted in FIG. 3 include a user plane function (UPF) 305, an access and mobility management function (AMF) 312, a session management function (SMF) 314, a policy control function (PCF) 320, a network repository function (NRF) 330, a network exposure function (NEF) 340, a unified data management (UDM) 350, an authentication server function (AUSF) 360, a network slice selection function (NSSF) 370, a charging function (CHF) 380, a network data analytics function (NWDAF) 390, and an application function (AF) 399. The UPF 305 may be a user-plane core network function, whereas the NFs 312, 314, and 320-390 may be control-plane core network functions. Although not shown in the example of FIG. 3, the core network may include additional instances of any of the NFs depicted and / or one or more different NF types that provide different services. Other examples of NF type include a gateway mobile location center (GMLC), a location management function (LMF), an operations, administration, and maintenance function (OAM), a public warning system (PWS), a short message service function (SMSF), a unified data repository (UDR), and an unstructured data storage function (UDSF).

[0060] Each element depicted in FIG. 3 has an interface with at least one other element. The interface may be a logical connection rather than, for example, a direct physical connection. Any interface may be identified using a reference point representation and / or a service-based representation. In a reference point representation, the letter ‘N’ is followed by a numeral, indicating an interface between two specific elements. For example, as shown in FIG. 3, AN 302 and UPF 305 interface via ‘N3’, whereas UPF 305 and DN 308 interface via 'N6' . By contrast, in a service-based representation, the letter ‘N’ is followed by letters. The letters identify an NF that provides services to the core network. For example, PCF 320 may provide services via interface ‘Npcf . The PCF 320 may provide services to any NF in the core network via ‘Npcf . Accordingly, a service-based representation may correspond to a bundle of reference point representations. For example, the Npcf interface between PCF 320 and the core network generally may correspond to an N7 interface between PCF 320 and SMF 314, an N30 interface between PCF 320 and NEF 340, etc.

[0061] The UPF 305 may serve as a gateway for user plane traffic between AN 302 and DN 308. The UE 301 may connect to UPF 305 via a Uu interface and an N3 interface (also described as NG-U interface).Docket No.: 24-1271 PCTThe UPF 305 may connect to DN 308 via an N6 interface. The UPF 305 may connect to one or more other UPFs (not shown) via an N9 interface. The UE 301 may be configured to receive services through a protocol data unit (PDU) session, which is a logical connection between UE 301 and DN 308. The UPF 305 (or a plurality of UPFs if desired) may be selected by SMF 314 to handle a particular PDU session between UE 301 and DN 308. The SMF 314 may control the functions of UPF 305 with respect to the PDU session. The SMF 314 may connect to UPF 305 via an N4 interface. The UPF 305 may handle any number of PDU sessions associated with any number of UEs (via any number of ANs). For purposes of handling the one or more PDU sessions, UPF 305 may be controlled by any number of SMFs via any number of corresponding N4 interfaces.

[0062] The AMF 312 depicted in FIG. 3 may control UE access to the core network. The UE 301 may register with the network via AMF 312. It may be necessary for UE 301 to register prior to establishing a PDU session. The AMF 312 may manage a registration area of UE 301 , enabling the network to track the physical location of UE 301 within the network. For a UE in connected mode, AMF 312 may manage UE mobility, for example, handovers from one AN or portion thereof to another. For a UE in idle mode, AMF 312 may perform registration updates and / or page the UE to transition the UE to connected mode.

[0063] The AMF 312 may receive, from UE 301 , non-access stratum (NAS) messages transmitted in accordance with NAS protocol. NAS messages relate to communications between UE 301 and the core network. Although NAS messages may be relayed to AMF 312 via AN 302, they may be described as communications via the N1 interface. NAS messages may facilitate UE registration and mobility management, for example, by authenticating, identifying, configuring, and / or managing a connection of UE 301 . NAS messages may support session management procedures for maintaining user plane connectivity and quality of service (QoS) of a session between UE 301 and DN 309. If the NAS message involves session management, AMF 312 may send the NAS message to SMF 314. NAS messages may be used to transport messages between UE 301 and other components of the core network (e.g ., core network components other than AMF 312 and SMF 314). The AMF 312 may act on a particular NAS message itself, or alternatively, forward the NAS message to an appropriate core network function (e.g., SMF 314, etc.)

[0064] The SMF 314 depicted in FIG. 3 may establish, modify, and / or release a PDU session based on messaging received UE 301. The SMF 314 may allocate, manage, and / or assign an IP address to UE 301 , for example, upon establishment of a PDU session. There may be multiple SMFs in the network, each of which may be associated with a respective group of wireless devices, base stations, and / or UPFs. A UE with multiple PDU sessions may be associated with a different SMF for each PDU session. As noted above, SMF 314 may select one or more UPFs to handle a PDU session and may control the handling of the PDU session by the selected UPF by providing rules for packet handling (PDR, FAR, QER, etc.). Rules relating to QoS and / or charging for a particular PDU session may be obtained from PCF 320 and provided to UPF 305.Docket No.: 24-1271 PCT

[0065] The PCF 320 may provide, to other NFs, services relating to policy rules. The PCF 320 may use subscription data and information about network conditions to determine policy rules and then provide the policy rules to a particular NF which may be responsible for enforcement of those rules. Policy rules may relate to policy control for access and mobility, and may be enforced by the AMF. Policy rules may relate to session management, and may be enforced by the SMF 314. Policy rules may be, for example, networkspecific, wireless device-specific, session-specific, or data flow-specific.

[0066] The NRF 330 may provide service discovery. The NRF 330 may belong to a particular PLMN. The NRF 330 may maintain NF profiles relating to other NFs in the communication network 300. The NF profile may include, for example, an address, PLMN, and / or type of the NF, a slice identifier, a list of the one or more services provided by the NF, and the authorization required to access the services.

[0067] The NEF 340 depicted in FIG. 3 may provide an interface to external domains, permitting external domains to selectively access the control plane of the communication network 300. The external domain may comprise, for example, third-party network functions, application functions, etc. The NEF 340 may act as a proxy between external elements and network functions such as AMF 312, SMF 314, PCF 320, UDM 350, etc. As an example, NEF 340 may determine a location or reachability status of UE 301 based on reports from AMF 312, and provide status information to an external element. As an example, an external element may provide, via NEF 340, information that facilitates the setting of parameters for establishment of a PDU session. The NEF 340 may determine which data and capabilities of the control plane are exposed to the external domain. The NEF 340 may provide secure exposure that authenticates and / or authorizes an external entity to which data or capabilities of the communication network 300 are exposed. The NEF 340 may selectively control the exposure such that the internal architecture of the core network is hidden from the external domain.

[0068] The UDM 350 may provide data storage for other NFs. The UDM 350 may permit a consolidated view of network information that may be used to ensure that the most relevant information can be made available to different NFs from a single resource. The UDM 350 may store and / or retrieve information from a unified data repository (UDR). For example, UDM 350 may obtain user subscription data relating to UE 301 from the UDR.

[0069] The AUSF 360 may support mutual authentication of UE 301 by the core network and authentication of the core network by UE 301 . The AUSF 360 may perform key agreement procedures and provide keying material that can be used to improve security.

[0070] The NSSF 370 may select one or more network slices to be used by the UE 301 . The NSSF 370 may select a slice based on slice selection information. For example, the NSSF 370 may receive Single Network Slice Selection Assistance Information (S-NSSAI) and map the S-NSSAI to a network slice instance identifier (NSI).

[0071] The CHF 380 may control billing-related tasks associated with UE 301 . For example, UPF 305 mayDocket No.: 24-1271 PCT report traffic usage associated with UE 301 to SMF 314. The SMF 314 may collect usage data from UPF 305 and one or more other UPFs. The usage data may indicate how much data is exchanged, what DN the data is exchanged with, a network slice associated with the data, or any other information that may influence billing. The SMF 314 may share the collected usage data with the CHF. The CHF may use the collected usage data to perform billing-related tasks associated with UE 301 . The CHF may, depending on the billing status of UE 301 , instruct SMF 314 to limit or influence access of UE 301 and / or to provide billing-related notifications to UE 301.

[0072] The NWDAF 390 may collect and analyze data from other network functions and offer data analysis services to other network functions. As an example, NWDAF 390 may collect data relating to a load level for a particular network slice instance from UPF 305, AMF 312, and / or SMF 314. Based on the collected data, NWDAF 390 may provide load level data to the PCF 320 and / or NSSF 370, and / or notify the PC220 and / or NSSF 370 if load level for a slice reaches and / or exceeds a load level threshold.

[0073] The AF 399 may be outside the core network, but may interact with the core network to provide information relating to the QoS requirements or traffic routing preferences associated with a particular application. The AF 399 may access the core network based on the exposure constraints imposed by the NEF 340. However, an operator of the core network may consider the AF 399 to be a trusted domain that can access the network directly.

[0074] FIGS. 4A, 4B, and 5 illustrate other examples of core network architectures that are analogous in some respects to the core network architecture 300 depicted in FIG. 3. For conciseness, some of the core network elements depicted in FIG 3 are omitted. Many of the elements depicted in FIGS. 4A, 4B, and 5 are analogous in some respects to elements depicted in FIG. 3. For conciseness, some of the details relating to their functions or operation are omitted.

[0075] FIG. 4A illustrates an example of a core network architecture 400A comprising an arrangement of multiple UPFs. Core network architecture 400A includes a UE 401 , an AN 402, an AMF 412, and an SMF 414. Unlike previous examples of core network architectures described above, FIG. 4A depicts multiple UPFs, including a UPF 405, a UPF 406, and a UPF 407, and multiple DNs, including a DN 408 and a DN 409. Each of the multiple UPFs 405, 406, 407 may communicate with the SMF 414 via an N4 interface. The DNs 408, 409 communicate with the UPFs 405, 406, respectively, via N6 interfaces. As shown in FIG. 4A, the multiple UPFs 405, 406, 407 may communicate with one another via N9 interfaces.

[0076] The UPFs 405, 406, 407 may perform traffic detection, in which the UPFs identify and / or classify packets. Packet identification may be performed based on packet detection rules (PDR) provided by the SMF 414. A PDR may include packet detection information comprising one or more of: a source interface, a UE IP address, core network (CN) tunnel information (e.g . , a CN address of an N3 / N9 tunnel corresponding to a PDU session), a network instance identifier, a quality of service flow identifier (QFI), a filter set (for example, an IP packet filter set or an ethernet packet filter set), and / or an application identifier.Docket No.: 24-1271 PCT

[0077] In addition to indicating how a particular packet is to be detected, a PDR may further indicate rules for handling the packet upon detection thereof. The rules may include, for example, forwarding action rules (FARs), multi-access rules (MARs), usage reporting rules (URRs), QoS enforcement rules (QERs), etc. For example, the PDR may comprise one or more FAR identifiers, MAR identifiers, URR identifiers, and / or QER identifiers. These identifiers may indicate the rules that are prescribed for the handling of a particular detected packet.

[0078] The UPF 405 may perform traffic forwarding in accordance with a FAR. For example, the FAR may indicate that a packet associated with a particular PDR is to be forwarded, duplicated, dropped, and / or buffered. The FAR may indicate a destination interface, for example, “access” for downlink or “core” for uplink. If a packet is to be buffered, the FAR may indicate a buffering action rule (BAR). As an example, UPF 405 may perform data buffering of a certain number of downlink packets if a PDU session is deactivated.

[0079] The UPF 405 may perform QoS enforcement in accordance with a QER. For example, the QER may indicate a guaranteed bitrate that is authorized and / or a maximum bitrate to be enforced for a packet associated with a particular PDR. The QER may indicate that a particular guaranteed and / or maximum bitrate may be for uplink packets and / or downlink packets. The UPF 405 may mark packets belonging to a particular QoS flow with a corresponding QFI. The marking may enable a recipient of the packet to determine a QoS of the packet.

[0080] The UPF 405 may provide usage reports to the SMF 414 in accordance with a URR. The URR may indicate one or more triggering conditions for generation and reporting of the usage report, for example, immediate reporting, periodic reporting, a threshold for incoming uplink traffic, or any other suitable triggering condition. The URR may indicate a method for measuring usage of network resources, for example, data volume, duration, and / or event.

[0081] As noted above, the DNs 408, 409 may comprise public DNs (e.g., the Internet), private DNs (e.g., private, internal corporate-owned DNs), and / or intra-operator DNs. Each DN may provide an operator service and / or a third-party service. The service provided by a DN may be the Internet, an IP multimedia subsystem (IMS), an augmented or virtual reality network, an edge computing or mobile edge computing (MEG) network, etc. Each DN may be identified using a data network name (DNN). The UE 401 may be configured to establish a first logical connection with DN 408 (a first PDU session), a second logical connection with DN 409 (a second PDU session), or both simultaneously (first and second PDU sessions).

[0082] Each PDU session may be associated with at least one UPF configured to operate as a PDU session anchor (PSA, or “anchor”). The anchor may be a UPF that provides an N6 interface with a DN.

[0083] In the example of FIG. 4A, UPF 405 may be the anchor for the first PDU session between UE 401 and DN 408, whereas the UPF 406 may be the anchor for the second PDU session between UE 401 and DN 409. The core network may use the anchor to provide service continuity of a particular PDU session (forDocket No.: 24-1271 PCT example, IP address continuity) as UE 401 moves from one access network to another. For example, suppose that UE 401 establishes a PDU session using a data path to the DN 408 using an access network other than AN 402. The data path may include UPF 405 acting as anchor. Suppose further that the UE 401 later moves into the coverage area of the AN 402. In such a scenario, SMF 414 may select a new UPF (UPF 407) to bridge the gap between the newly-entered access network (AN 402) and the anchor UPF (UPF 405). The continuity of the PDU session may be preserved as any number of UPFs are added or removed from the data path. When a UPF is added to a data path, as shown in FIG. 4A, it may be described as an intermediate UPF and / or a cascaded UPF.

[0084] As noted above, UPF 406 may be the anchor for the second PDU session between UE 401 and DN 409. Although the anchor for the first and second PDU sessions are associated with different UPFs in FIG 4A, it will be understood that this is merely an example. It will also be understood that multiple PDU sessions with a single DN may correspond to any number of anchors. When there are multiple UPFs, a UPF at the branching point (UPF 407 in FIG. 4A) may operate as an uplink classifier (UL-CL). The UL-CL may divert uplink user plane traffic to different UPFs.

[0085] The SMF 414 may allocate, manage, and / or assign an IP address to UE 401 , for example, upon establishment of a PDU session. The SMF 414 may maintain an internal pool of IP addresses to be assigned. The SMF 414 may, if necessary, assign an IP address provided by a dynamic host configuration protocol (DHCP) server or an authentication, authorization, and accounting (AAA) server. IP address management may be performed in accordance with a session and service continuity (SSC) mode. In SSC mode 1 , an IP address of UE 401 may be maintained (and the same anchor UPF may be used) as the wireless device moves within the network. In SSC mode 2, the IP address of UE 401 changes as UE 401 moves within the network (e.g., the old IP address and UPF may be abandoned and a new IP address and anchor UPF may be established). In SSC mode 3, it may be possible to maintain an old IP address (similar to SSC mode 1 ) temporarily while establishing a new IP address (similar to SSC mode 2), thus combining features of SSC modes 1 and 2. Applications that are sensitive to IP address changes may operate in accordance with SSC mode 1.

[0086] UPF selection may be controlled by SMF 414. For example, upon establishment and / or modification of a PDU session between UE 401 and DN 408, SMF 414 may select UPF 405 as the anchor for the PDU session and / or UPF 407 as an intermediate UPF. Criteria for UPF selection include path efficiency and / or speed between AN 402 and DN 408. The reliability, load status, location, slice support and / or other capabilities of candidate UPFs may also be considered.

[0087] FIG. 4B illustrates an example of a core network architecture 400B that accommodates untrusted access. Similar to FIG. 4A, UE 401 as depicted in FIG. 4B connects to DN 408 via AN 402 and UPF 405. The AN 402 and UPF 405 constitute trusted (e g., 3GPP) access to the DN 408. By contrast, UE 401 may also access DN 408 using an untrusted access network, AN 403, and a non-3GPP interworking functionDocket No.: 24-1271 PCT(N3IWF) 404.

[0088] The AN 403 may be, for example, a wireless land area network (WLAN) operating in accordance with the IEEE 802.11 standard. The UE 401 may connect to AN 403, via an interface Y1 , in whatever manner is prescribed for AN 403. The connection to AN 403 may or may not involve authentication. The UE 401 may obtain an IP address from AN 403. The UE 401 may determine to connect to core network 400B and select untrusted access for that purpose. The AN 403 may communicate with N3IWF 404 via a Y2 interface. After selecting untrusted access, the UE 401 may provide N3IWF 404 with sufficient information to select an AMF. The selected AMF may be, for example, the same AMF that is used by UE 401 for 3GPP access (AMF 412 in the present example). The N3IWF 404 may communicate with AMF 412 via an N2 interface. The UPF 405 may be selected and N3IWF 404 may communicate with UPF 405 via an N3 interface. The UPF 405 may be a PDU session anchor (PSA) and may remain the anchor for the PDU session even as UE 401 shifts between trusted access and untrusted access.

[0089] FIG. 5 illustrates an example of a core network architecture 500 in which a UE 501 is in a roaming scenario. In a roaming scenario, UE 501 is a subscriber of a first PLMN (a home PLMN, or HPLMN) but attaches to a second PLMN (a visited PLMN, or VPLMN). Core network architecture 500 includes UE 501 , an AN 502, a UPF 505, and a DN 508. The AN 502 and UPF 505 may be associated with a VPLMN. The VPLMN may manage the AN 502 and UPF 505 using core network elements associated with the VPLMN, including an AMF 512, an SMF 514, a PCF 520, an NRF 530, an NEF 540, and an NSSF 570. An AF 599 may be adjacent the core network of the VPLMN.

[0090] The UE 501 may not be a subscriber of the VPLMN. The AMF 512 may authorize UE 501 to access the network based on, for example, roaming restrictions that apply to UE 501 . In order to obtain network services provided by the VPLMN, it may be necessary for the core network of the VPLMN to interact with core network elements of a HPLMN of UE 501 , in particular, a PCF 521 , an NRF 531 , an NEF 541 , a UDM 551 , and / or an AUSF 561. The VPLMN and HPLMN may communicate using an N32 interface connecting respective security edge protection proxies (SEPPs). In FIG. 5, the respective SEPPs are depicted as a VSEPP 590 and an HSEPP 591 .

[0091] The VSEPP 590 and the HSEPP 591 communicate via an N32 interface for defined purposes while concealing information about each PLMN from the other. The SEPPs may apply roaming policies based on communications via the N32 interface. The PCF 520 and PCF 521 may communicate via the SEPPs to exchange policy-related signaling. The NRF 530 and NRF 531 may communicate via the SEPPs to enable service discovery of NFs in the respective PLMNs. The VPLMN and HPLMN may independently maintain NEF 540 and NEF 541 . The NSSF 570 and NSSF 571 may communicate via the SEPPs to coordinate slice selection for UE 501 . The HPLMN may handle all authentication and subscription related signaling. For example, when the UE 501 registers or requests service via the VPLMN, the VPLMN may authenticate UE 501 and / or obtain subscription data of UE 501 by accessing, via the SEPPs, the UDM 551 and AUSF 561Docket No.: 24-1271 PCT of the HPLMN.

[0092] The core network architecture 500 depicted in FIG. 5 may be referred to as a local breakout configuration, in which UE 501 accesses DN 508 using one or more UPFs of the VPLMN (i.e., UPF 505). However, other configurations are possible. For example, in a home-routed configuration (not shown in FIG. 5), UE 501 may access a DN using one or more UPFs of the HPLMN. In the home-routed configuration, an N9 interface may run parallel to the N32 interface, crossing the frontier between the VPLMN and the HPLMN to carry user plane data. One or more SMFs of the respective PLMNs may communicate via the N32 interface to coordinate session management for UE 501 . The SMFs may control their respective UPFs on either side of the frontier.

[0093] FIG. 6 illustrates an example of network slicing. Network slicing may refer to division of shared infrastructure (e.g., physical infrastructure) into distinct logical networks. These distinct logical networks may be independently controlled, isolated from one another, and / or associated with dedicated resources.

[0094] Network architecture 600A illustrates an un-sliced physical network corresponding to a single logical network. The network architecture 600A comprises a user plane wherein UEs 601 A, 601 B, 601 C (collectively, UEs 601) have a physical and logical connection to a DN 608 via an AN 602 and a UPF 605. The network architecture 600A comprises a control plane wherein an AMF 612 and a SMF 614 control various aspects of the user plane.

[0095] The network architecture 600A may have a specific set of characteristics (e.g., relating to maximum bit rate, reliability, latency, bandwidth usage, power consumption, etc.). This set of characteristics may be affected by the nature of the network elements themselves (e.g., processing power, availability of free memory, proximity to other network elements, etc.) or the management thereof (e.g., optimized to maximize bit rate or reliability, reduce latency or power bandwidth usage, etc.). The characteristics of network architecture 600A may change over time, for example, by upgrading equipment or by modifying procedures to target a particular characteristic. However, at any given time, network architecture 600A will have a single set of characteristics that may or may not be optimized for a particular use case. For example, UEs 601 A, 601 B, 6010 may have different requirements, but network architecture 600A can only be optimized for one of the three.

[0096] Network architecture 600B is an example of a sliced physical network divided into multiple logical networks. In FIG 6, the physical network is divided into three logical networks, referred to as slice A, slice B, and slice C. For example, UE 601 A may be served by AN 602A, UPF 605A, AMF 612, and SMF 614A. UE 601 B may be served by AN 602B, UPF 605B, AMF 612, and SMF 614B. UE 6010 may be served by AN 602C, UPF 605C, AMF 612, and SMF 614C. Although the respective UEs 601 communicate with different network elements from a logical perspective, these network elements may be deployed by a network operator using the same physical network elements.

[0097] Each network slice may be tailored to network services having different sets of characteristics. ForDocket No.: 24-1271 PCT example, slice A may correspond to enhanced mobile broadband (eMBB) service. Mobile broadband may refer to internet access by mobile users, commonly associated with smartphones Slice B may correspond to ultra-reliable low-latency communication (URLLC), which focuses on reliability and speed. Relative to eMBB, URLLC may improve the feasibility of use cases such as autonomous driving and telesurgery. Slice C may correspond to massive machine type communication (mMTC), which focuses on low-power services delivered to a large number of users. For example, slice C may be optimized for a dense network of battery-powered sensors that provide small amounts of data at regular intervals. Many mMTC use cases would be prohibitively expensive if they operated using an eMBB or URLLC network.

[0098] If the service requirements for one of the UEs 601 changes, then the network slice serving that UE can be updated to provide better service. Moreover, the set of network characteristics corresponding to eMBB, URLLC, and mMTC may be varied, such that differentiated species of eMBB, URLLC, and mMTC are provided. Alternatively, network operators may provide entirely new services in response to, for example, customer demand.

[0099] In FIG. 6, each of the UEs 601 has its own network slice. However, it will be understood that a single slice may serve any number of UEs and a single UE may operate using any number of slices. Moreover, in the example network architecture 600B, the AN 602, UPF 605 and SMF 614 are separated into three separate slices, whereas the AMF 612 is unsliced. However, it will be understood that a network operator may deploy any architecture that selectively utilizes any mix of sliced and unsliced network elements, with different network elements divided into different numbers of slices. Although FIG. 6 only depicts three core network functions, it will be understood that other core network functions may be sliced as well. A PLMN that supports multiple network slices may maintain a separate network repository function (NFR) for each slice, enabling other NFs to discover network services associated with that slice.

[0100] Network slice selection may be controlled by an AMF, or alternatively, by a separate network slice selection function (NSSF). For example, a network operator may define and implement distinct network slice instances (NSIs). Each NSI may be associated with single network slice selection assistance information (S-NSSAI). The S-NSSAI may include a particular slice / service type (SST) indicator (indicating eMBB, URLLC, mMTC, etc.). As an example, a particular tracking area may be associated with one or more configured S-NSSAIs. UEs may identify one or more requested and / or subscribed S-NSSAIs (e.g., during registration) The network may indicate to the UE one or more allowed and / or rejected S-NSSAIs.

[0101] The S-NSSAI may further include a slice differentiator (SD) to distinguish between different tenants of a particular slice and / or service type. For example, a tenant may be a customer (e.g., vehicle manufacture, service provider, etc.) of a network operator that obtains (for example, purchases) guaranteed network resources and / or specific policies for handling its subscribers. The network operator may configure different slices and / or slice types, and use the SD to determine which tenant is associated with a particular slice.Docket No.: 24-1271 PCT

[0102] FIG. 7A, FIG. 7B, and FIG. 7C illustrate a user plane (UP) protocol stack, a control plane (CP) protocol stack, and services provided between protocol layers of the UP protocol stack.

[0103] The layers may be associated with an open system interconnection (OSI) model of computer networking functionality. In the OSI model, layer 1 may correspond to the bottom layer, with higher layers on top of the bottom layer. Layer 1 may correspond to a physical layer, which is concerned with the physical infrastructure used for transfer of signals (for example, cables, fiber optics, and / or radio frequency transceivers). In New Radio (NR), layer 1 may comprise a physical layer (PHY). Layer 2 may correspond to a data link layer. Layer 2 may be concerned with packaging of data (into, e.g., data frames) for transfer, between nodes of the network, using the physical infrastructure of layer 1 . In NR, layer 2 may comprise a media access control layer (MAC), a radio link control layer (RLC), a packet data convergence layer (PDCP), and a service data application protocol layer (SDAP).

[0104] Layer 3 may correspond to a network layer. Layer 3 may be concerned with routing of the data which has been packaged in layer 2. Layer 3 may handle prioritization of data and traffic avoidance. In NR, layer 3 may comprise a radio resource control layer (RRC) and a non-access stratum layer (NAS). Layers 4 through 7 may correspond to a transport layer, a session layer, a presentation layer, and an application layer. The application layer interacts with an end user to provide data associated with an application. In an example, an end user implementing the application may generate data associated with the application and initiate sending of that information to a targeted data network (e.g., the Internet, an application server, etc.). Starting at the application layer, each layer in the OSI model may manipulate and / or repackage the information and deliver it to a lower layer. At the lowest layer, the manipulated and / or repackaged information may be exchanged via physical infrastructure (for example, electrically, optically, and / or electromagnetically). As it approaches the targeted data network, the information will be unpackaged and provided to higher and higher layers, until it once again reaches the application layer in a form that is usable by the targeted data network (e.g., the same form in which it was provided by the end user). To respond to the end user, the data network may perform this procedure in reverse.

[0105] FIG. 7A illustrates a user plane protocol stack. The user plane protocol stack may be a new radio (NR) protocol stack for a Uu interface between a UE 701 and a gNB 702. In layer 1 of the UP protocol stack, the UE 701 may implement PHY 731 and the gNB 702 may implement PHY 732. In layer 2 of the UP protocol stack, the UE 701 may implement MAC 741 , RLC 751 , PDCP 761 , and SDAP 771. The gNB 702 may implement MAC 742, RLC 752, PDCP 762, and SDAP 772.

[0106] FIG. 7B illustrates a control plane protocol stack. The control plane protocol stack may be an NR protocol stack for the Uu interface between the UE 701 and the gNB 702 and / or an N1 interface between the UE 701 and an AMF 712. In layer 1 of the CP protocol stack, the UE 701 may implement PHY 731 and the gNB 702 may implement PHY 732. In layer 2 of the CP protocol stack, the UE 701 may implement MAC 741 , RLC 751 , PDCP 761 , RRC 781 , and NAS 791 . The gNB 702 may implement MAC 742, RLCDocket No.: 24-1271 PCT752, PDCP 762, and RRC 782. The AMF 712 may implement NAS 792.

[0107] The NAS may be concerned with the non-access stratum, in particular, communication between the UE 701 and the core network (e.g., the AMF 712). Lower layers may be concerned with the access stratum, for example, communication between the UE 701 and the gNB 702. Messages sent between the UE 701 and the core network may be referred to as NAS messages. In an example, a NAS message may be relayed by the gNB 702, but the content of the NAS message (e.g., information elements of the NAS message) may not be visible to the gNB 702.

[0108] FIG. 70 illustrates an example of services provided between protocol layers of the NR user plane protocol stack illustrated in FIG. 7A. The UE 701 may receive services through a PDU session, which may be a logical connection between the UE 701 and a data network (DN). The UE 701 and the DN may exchange data packets associated with the PDU session. The PDU session may comprise one or more quality of service (QoS) flows. SDAP 771 and SDAP 772 may perform mapping and / or demapping between the one or more QoS flows of the PDU session and one or more radio bearers (e.g., data radio bearers). The mapping between the QoS flows and the data radio bearers may be determined in the SDAP 772 by the gNB 702, and the UE 701 may be notified of the mapping (e.g., based on control signaling and / or reflective mapping). For reflective mapping, the SDAP 772 of the gNB 220 may mark downlink packets with a QoS flow indicator (QFI) and deliver the downlink packets to the UE 701 . The UE 701 may determine the mapping based on the QFI of the downlink packets.

[0109] PDCP 761 and PDCP 762 may perform header compression and / or decompression. Header compression may reduce the amount of data transmitted over the physical layer. The PDCP 761 and PDCP 762 may perform ciphering and / or deciphering. Ciphering may reduce unauthorized decoding of data transmitted over the physical layer (e.g., intercepted on an air interface), and protect data integrity (e.g., to ensure control messages originate from intended sources). The PDCP 761 and PDCP 762 may perform retransmissions of undelivered packets, in-sequence delivery and reordering of packets, duplication of packets, and / or identification and removal of duplicate packets. In a dual connectivity scenario, PDCP 761 and PDCP 762 may perform mapping between a split radio bearer and RLC channels.

[0110] RLC 751 and RLC 752 may perform segmentation, retransmission through Automatic Repeat Request (ARQ). The RLC 751 and RLC 752 may perform removal of duplicate data units received from MAC 741 and MAC 742, respectively. The RLCs 213 and 223 may provide RLC channels as a service to PDCPs 214 and 224, respectively.

[0111] MAC 741 and MAC 742 may perform multiplexing and / or demultiplexing of logical channels. MAC 741 and MAC 742 may map logical channels to transport channels. In an example, UE 701 may, in MAC 741 , multiplex data units of one or more logical channels into a transport block. The UE 701 may transmit the transport block to the gNB 702 using PHY 731 . The gNB 702 may receive the transport block using PHY 732 and demultiplex data units of the transport blocks back into logical channels. MAC 741 and MACDocket No.: 24-1271 PCT742 may perform error correction through Hybrid Automatic Repeat Request (HARQ), logical channel prioritization, and / or padding.

[0112] PHY 731 and PHY 732 may perform mapping of transport channels to physical channels. PHY 731 and PHY 732 may perform digital and analog signal processing functions (e.g., coding / decoding and modulation / demodulation) for sending and receiving information (e.g., transmission via an air interface). PHY 731 and PHY 732 may perform multi-antenna mapping.

[0113] FIG. 8 illustrates an example of a quality of service (QoS) model for differentiated data exchange. In the QoS model of FIG. 8, there are a UE 801 , a AN 802, and a UPF 805. The QoS model facilitates prioritization of certain packet or protocol data units (PDUs), also referred to as packets. For example, higher-priority packets may be exchanged faster and / or more reliably than lower-priority packets. The network may devote more resources to exchange of high-QoS packets.

[0114] In the example of FIG. 8, a PDU session 810 is established between UE 801 and UPF 805. The PDU session 810 may be a logical connection enabling the UE 801 to exchange data with a particular data network (for example, the Internet). The UE 801 may request establishment of the PDU session 810. At the time that the PDU session 810 is established, the UE 801 may, for example, identify the targeted data network based on its data network name (DNN). The PDU session 810 may be managed, for example, by a session management function (SMF, not shown). In order to facilitate exchange of data associated with the PDU session 810, between the UE 801 and the data network, the SMF may select the UPF 805 (and optionally, one or more other UPFs, not shown).

[0115] One or more applications associated with UE 801 may generate uplink packets 812A-812E associated with the PDU session 810. In order to work within the QoS model, UE 801 may apply QoS rules 814 to uplink packets 812A-812E. The QoS rules 814 may be associated with PDU session 810 and may be determined and / or provided to the UE 801 when PDU session 810 is established and / or modified. Based on QoS rules 814, UE 801 may classify uplink packets 812A-812E, map each of the uplink packets 812A-812E to a QoS flow, and / or mark uplink packets 812A-812E with a QoS flow indicator (QFI). As a packet travels through the network, and potentially mixes with other packets from other UEs having potentially different priorities, the QFI indicates how the packet should be handled in accordance with the QoS model. In the present illustration, uplink packets 812A, 812B are mapped to QoS flow 816A, uplink packet 812C is mapped to QoS flow 816B, and the remaining packets are mapped to QoS flow 816C.

[0116] The QoS flows may be the finest granularity of QoS differentiation in a PDU session. In the figure, three QoS flows 816A-816C are illustrated. However, it will be understood that there may be any number of QoS flows. Some QoS flows may be associated with a guaranteed bit rate (GBR QoS flows) and others may have bit rates that are not guaranteed (non-GBR QoS flows). QoS flows may also be subject to per- UE and per-session aggregate bit rates. One of the QoS flows may be a default QoS flow. The QoS flows may have different priorities. For example, QoS flow 816A may have a higher priority than QoS flow 816B,Docket No.: 24-1271 PCT which may have a higher priority than QoS flow 816C. Different priorities may be reflected by different QoS flow characteristics. For example, QoS flows may be associated with flow bit rates. A particular QoS flow may be associated with a guaranteed flow bit rate (GFBR) and / or a maximum flow bit rate (MFBR). QoS flows may be associated with specific packet delay budgets (PDBs), packet error rates (PERs), and / or maximum packet loss rates. QoS flows may also be subject to per-UE and per-session aggregate bit rates.

[0117] In order to work within the QoS model, UE 801 may apply resource mapping rules 818 to the QoS flows 816A-816C. The air interface between UE 801 and AN 802 may be associated with resources 820. In the present illustration, QoS flow 816A is mapped to resource 820A, whereas QoS flows 816B, 816C are mapped to resource 820B. The resource mapping rules 818 may be provided by the AN 802. In order to meet QoS requirements, the resource mapping rules 818 may designate more resources for relatively high- priority QoS flows. With more resources, a high-priority QoS flow such as QoS flow 816A may be more likely to obtain the high flow bit rate, low packet delay budget, or other characteristic associated with QoS rules 814. The resources 820 may comprise, for example, radio bearers. The radio bearers (e.g., data radio bearers) may be established between the UE 801 and the AN 802. The radio bearers in 5G, between the UE 801 and the AN 802, may be distinct from bearers in LTE, for example, Evolved Packet System (EPS) bearers between a UE and a packet data network gateway (PGW), S1 bearers between an eNB and a serving gateway (SGW), and / or an S5 / S8 bearer between an SGW and a PGW.

[0118] Once a packet associated with a particular QoS flow is received at AN 802 via resource 820A or resource 820B, AN 802 may separate packets into respective QoS flows 856A-856C based on QoS profiles 828 The QoS profiles 828 may be received from an SMF Each QoS profile may correspond to a QFI, for example, the QFI marked on the uplink packets 812A-812E. Each QoS profile may include QoS parameters such as 5G QoS identifier (5QI) and an allocation and retention priority (ARP). The QoS profile for non-GBR QoS flows may further include additional QoS parameters such as a reflective QoS attribute (RQA).The QoS profile for GBR QoS flows may further include additional QoS parameters such as a guaranteed flow bit rate (GFBR), a maximum flow bit rate (MFBR), and / or a maximum packet loss rate. The 5QI may be a standardized 5QI which has one-to-one mapping to a standardized combination of 5G QoS characteristics per well-known services. The 5QI may be a dynamically assigned 5QI which the standardized 5QI values are not defined. The 5QI may represent 5G QoS characteristics. The 5QI may comprise a resource type, a default priority level, a packet delay budget (PDB), a packet error rate (PER), a maximum data burst volume, and / or an averaging window. The resource type may indicate a non-GBR QoS flow, a GBR QoS flow or a delay-critical GBR QoS flow. The averaging window may represent a duration over which the GFBR and / or MFBR is calculated. ARP may be a priority level comprising preemption capability and a pre-emption vulnerability. Based on the ARP, the AN 802 may apply admission control for the QoS flows in a case of resource limitations.

[0119] The AN 802 may select one or more N3 tunnels 850 for transmission of the QoS flows 856A-856C.Docket No.: 24-1271 PCTAfter the packets are divided into QoS flows 856A-856C, the packet may be sent to UPF 805 (e.g., towards a DN) via the selected one or more N3 tunnels 850 The UPF 805 may verify that the QFIs of the uplink packets 812A-812E are aligned with the QoS rules 814 provided to the UE 801. The UPF 805 may measure and / or count packets and / or provide packet metrics to, for example, a PCF.

[0120] The figure also illustrates a process for downlink. In particular, one or more applications may generate downlink packets 852A-852E. The UPF 805 may receive downlink packets 852A-852E from one or more DNs and / or one or more other UPFs. As per the QoS model, UPF 805 may apply packet detection rules (PDRs) 854 to downlink packets 852A-852E. Based on PDRs 854, UPF 805 may map packets 852A- 852E into QoS flows. In the present illustration, downlink packets 852A, 852B are mapped to QoS flow 856A, downlink packet 852C is mapped to QoS flow 856B, and the remaining packets are mapped to QoS flow 856C.

[0121] The QoS flows 856A-856C may be sent to AN 802. The AN 802 may apply resource mapping rules to the QoS flows 856A-856C. In the present illustration, QoS flow 856A is mapped to resource 820A, whereas QoS flows 856B, 856C are mapped to resource 820B. In order to meet QoS requirements, the resource mapping rules may designate more resources to high-priority QoS flows.

[0122] FIGS. 9A- 9D illustrate example states and state transitions of a wireless device (e.g., a UE). At any given time, the wireless device may have a radio resource control (RRC) state, a registration management (RM) state, and a connection management (CM) state.

[0123] FIG. 9A is an example diagram showing RRC state transitions of a wireless device (e.g., a UE).The UE may be in one of three RRC states: RRC idle 910, (e.g., RRC _IDLE), RRC inactive 920 (e.g., RRC INACTIVE), or RRC connected 930 (e.g., RRC -CONNECTED). The UE may implement different RAN- related control-plane procedures depending on its RRC state. Other elements of the network, for example, a base station, may track the RRC state of one or more UEs and implement RAN-related control-plane procedures appropriate to the RRC state of each.

[0124] In RRC connected 930, it may be possible for the UE to exchange data with the network (for example, the base station). The parameters necessary for exchange of data may be established and known to both the UE and the network. The parameters may be referred to and / or included in an RRC context of the UE (sometimes referred to as a UE context). These parameters may include, for example: one or more AS contexts; one or more radio link configuration parameters; bearer configuration information (e.g., relating to a data radio bearer, signaling radio bearer, logical channel, QoS flow, and / or PDU session); security information; and / or PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information. The base station with which the UE is connected may store the RRC context of the UE.

[0125] While in RRC connected 930, mobility of the UE may be managed by the access network, whereas the UE itself may manage mobility while in RRC idle 910 and / or RRC inactive 920. While in RRC connected 930, the UE may manage mobility by measuring signal levels (e.g., reference signal levels) fromDocket No.: 24-1271 PCT a serving cell and neighboring cells and reporting these measurements to the base station currently serving the UE. The network may initiate handover based on the reported measurements. The RRC state may transition from RRC connected 930 to RRC idle 910 through a connection release procedure 930 or to RRC inactive 920 through a connection inactivation procedure 932.

[0126] In RRC idle 910, an RRC context may not be established for the UE. In RRC idle 910, the UE may not have an RRC connection with a base station. While in RRC idle 910, the UE may be in a sleep state for a majority of the time (e.g., to conserve battery power). The UE may wake up periodically (e.g., once in every discontinuous reception cycle) to monitor for paging messages from the access network. Mobility of the UE may be managed by the UE through a procedure known as cell reselection. The RRC state may transition from RRC idle 910 to RRC connected 930 through a connection establishment procedure 913, which may involve a random access procedure, as discussed in greater detail below.

[0127] In RRC inactive 920, the RRC context previously established is maintained in the UE and the base station. This may allow for a fast transition to RRC connected 930 with reduced signaling overhead as compared to the transition from RRC idle 910 to RRC connected 930. The RRC state may transition to RRC connected 930 through a connection resume procedure 923. The RRC state may transition to RRC idle 910 though a connection release procedure 921 that may be the same as or similar to connection release procedure 931.

[0128] An RRC state may be associated with a mobility management mechanism. In RRC idle 910 and RRC inactive 920, mobility may be managed by the UE through cell reselection. The purpose of mobility management in RRC idle 910 and / or RRC inactive 920 is to allow the network to be able to notify the UE of an event via a paging message without having to broadcast the paging message over the entire mobile communications network. The mobility management mechanism used in RRC idle 910 and / or RRC inactive 920 may allow the network to track the UE on a cell-group level so that the paging message may be broadcast over the cells of the cell group that the UE currently resides within instead of the entire communication network. Tracking may be based on different granularities of grouping. For example, there may be three levels of cell-grouping granularity: individual cells; cells within a RAN area identified by a RAN area identifier (RAI); and cells within a group of RAN areas, referred to as a tracking area and identified by a tracking area identifier (TAI).

[0129] Tracking areas may be used to track the UE at the CN level. The CN may provide the UE with a list of TAIs associated with a UE registration area. If the UE moves, through cell reselection, to a cell associated with a TAI not included in the list of TAIs associated with the UE registration area, the UE may perform a registration update with the CN to allow the CN to update the UE’s location and provide the UE with a new the UE registration area.

[0130] RAN areas may be used to track the UE at the RAN level. For a UE in RRC inactive 920 state, the UE may be assigned a RAN notification area. A RAN notification area may comprise one or more cellDocket No.: 24-1271 PCT identities, a list of RAIs, and / or a list of TAIs. In an example, a base station may belong to one or more RAN notification areas. In an example, a cell may belong to one or more RAN notification areas. If the UE moves, through cell reselection, to a cell not included in the RAN notification area assigned to the UE, the UE may perform a notification area update with the RAN to update the UE’s RAN notification area.

[0131] A base station storing an RRC context for a UE or a last serving base station of the UE may be referred to as an anchor base station. An anchor base station may maintain an RRC context for the UE at least during a period of time that the UE stays in a RAN notification area of the anchor base station and / or during a period of time that the UE stays in RRC inactive 920.

[0132] FIG. 9B is an example diagram showing registration management (RM) state transitions of a wireless device (e.g., a UE). The states are RM deregistered 940, (e.g. , RM-DEREGISTERED) and RM registered 950 (e.g., RM-REGISTERED).

[0133] In RM deregistered 940, the UE is not registered with the network, and the UE is not reachable by the network. In order to be reachable by the network, the UE must perform an initial registration. As an example, the UE may register with an AMF of the network. If registration is rejected (registration reject 944), then the UE remains in RM deregistered 940. If registration is accepted (registration accept 945), then the UE transitions to RM registered 950. While the UE is RM registered 950, the network may store, keep, and / or maintain a UE context for the UE. The UE context may be referred to as wireless device context. The UE context corresponding to network registration (maintained by the core network) may be different from the RRC context corresponding to RRC state (maintained by an access network, .e.g., a base station). The UE context may comprise a UE identifier and a record of various information relating to the UE, for example, UE capability information, policy information for access and mobility management of the UE, lists of allowed or established slices or PDU sessions, and / or a registration area of the UE (i.e., a list of tracking areas covering the geographical area where the wireless device is likely to be found).

[0134] While the UE is RM registered 950, the network may store the UE context of the UE, and if necessary, use the UE context to reach the UE. Moreover, some services may not be provided by the network unless the UE is registered. The UE may update its UE context while remaining in RM registered 950 (registration update accept 955). For example, if the UE leaves one tracking area and enters another tracking area, the UE may provide a tracking area identifier to the network. The network may deregister the UE, or the UE may deregister itself (deregistration 954). For example, the network may automatically deregister the wireless device if the wireless device is inactive for a certain amount of time. Upon deregistration, the UE may transition to RM deregistered 940.

[0135] FIG. 90 is an example diagram showing connection management (CM) state transitions of a wireless device (e.g., a UE), shown from a perspective of the wireless device. The UE may be in CM idle 960 (e.g., CM-IDLE) or CM connected 970 (e.g., CM-CONNECTED).

[0136] In CM idle 960, the UE does not have a non-access stratum (NAS) signaling connection with theDocket No.: 24-1271 PCT network. As a result, the UE cannot communicate with core network functions. The UE may transition to CM connected 970 by establishing an AN signaling connection (AN signaling connection establishment 967). This transition may be initiated by sending an initial NAS message. The initial NAS message may be a registration request (e.g., if the UE is RM deregistered 940) or a service request (e.g., if the UE is RM registered 950). If the UE is RM registered 950, then the UE may initiate the AN signaling connection establishment by sending a service request, or the network may send a page, thereby triggering the UE to send the service request.

[0137] In CM connected 970, the UE can communicate with core network functions using NAS signaling. As an example, the UE may exchange NAS signaling with an AMF for registration management purposes, service request procedures, and / or authentication procedures. As another example, the UE may exchange NAS signaling, with an SMF, to establish and / or modify a PDU session. The network may disconnect the UE, or the UE may disconnect itself (AN signaling connection release 976). For example, if the UE transitions to RM deregistered 940, then the UE may also transition to CM idle 960. When the UE transitions to CM idle 960, the network may deactivate a user plane connection of a PDU session of the UE.

[0138] FIG. 9D is an example diagram showing CM state transitions of the wireless device (e.g., a UE), shown from a network perspective (e.g., an AMF). The CM state of the UE, as tracked by the AMF, may be in CM idle 980 (e.g., CM-IDLE) or CM connected 990 (e.g., CM-CONNECTED). When the UE transitions from CM idle 980 to CM connected 990, the AMF may establish an N2 context of the UE (N2 context establishment 989). When the UE transitions from CM connected 990 to CM idle 980, the AMF may release the N2 context of the UE (N2 context release 998).

[0139] FIGS. 10 - 12 illustrate example procedures for registering, service request, and PDU session establishment of a UE.

[0140] FIG. 10 illustrates an example of a registration procedure for a wireless device (e.g., a UE). Based on the registration procedure, the UE may transition from, for example, RM deregistered 940 to RM registered 950.

[0141] Registration may be initiated by a UE for the purposes of obtaining authorization to receive services, enabling mobility tracking, enabling reachability, or other purposes. The UE may perform an initial registration as a first step toward connection to the network (for example, if the UE is powered on, airplane mode is turned off, etc.). Registration may also be performed periodically to keep the network informed of the UE's presence (for example, while in CM-IDLE state), or in response to a change in UE capability or registration area. Deregistration (not shown in FIG. 10) may be performed to stop network access.

[0142] At 1010, the UE transmits a registration request to an AN. As an example, the UE may have moved from a coverage area of a previous AMF (illustrated as AMF#1) into a coverage area of a new AMF (illustrated as AMF#2). The registration request may be a NAS message. The registration request mayDocket No.: 24-1271 PCT include a UE identifier. The AN may select an AMF for registration of the UE. For example, the AN may select a default AMF. For example, the AN may select an AMF that is already mapped to the UE (e.g., a previous AMF). The NAS registration request may include a network slice identifier and the AN may select an AMF based on the requested slice. After the AMF is selected, the AN may send the registration request to the selected AMF.

[0143] At 1020, the AMF that receives the registration request (AMF#2) performs a context transfer. The context may be a UE context, for example, an RRC context for the UE. As an example, AMF#2 may send AMF#1 a message requesting a context of the UE. The message may include the UE identifier. The message may be a Namf_ Communication- UEContextTransfer message. AMF#1 may send to AMF#2 a message that includes the requested UE context. This message may be a Namf_ Communication- UEContextTransfer message. After the UE context is received, the AMF#2 may coordinate authentication of the UE. After authentication is complete, AMF#2 may send to AMF#1 a message indicating that the UE context transfer is complete. This message may be a Namf_ Communication- UEContextTransfer Response message.

[0144] Authentication may require participation of the UE, an AUSF, a UDM and / or a UDR (not shown). For example, the AMF may request that the AUSF authenticate the UE. For example, the AUSF may execute authentication of the UE. For example, the AUSF may get authentication data from UDM. For example, the AUSF may send a subscription permanent identifier (SUPI) to the AMF based on the authentication being successful. For example, the AUSF may provide an intermediate key to the AMF. The intermediate key may be used to derive an access-specific security key for the UE, enabling the AMF to perform security context management (SCM). The AUSF may obtain subscription data from the UDM. The subscription data may be based on information obtained from the UDM (and / or the UDR). The subscription data may include subscription identifiers, security credentials, access and mobility related subscription data and / or session related data.

[0145] At 1030, the new AMF, AMF#2, registers and / or subscribes with the UDM. AMF#2 may perform registration using a UE context management service of the UDM (Nudm_ UECM). AMF#2 may obtain subscription information of the UE using a subscriber data management service of the UDM (Nudm_ SDM). AMF#2 may further request that the UDM notify AMF#2 if the subscription information of the UE changes. As the new AMF registers and subscribes, the old AMF, AMF#1 , may deregister and unsubscribe. After deregistration, AMF#1 is free of responsibility for mobility management of the UE.

[0146] At 1040, AMF#2 retrieves access and mobility (AM) policies from the PCF. As an example, the AMF#2 may provide subscription data of the UE to the PCF. The PCF may determine access and mobility policies for the UE based on the subscription data, network operator data, current network conditions, and / or other suitable information. For example, the owner of a first UE may purchase a higher level of service than the owner of a second UE. The PCF may provide the rules associated with the different levelsDocket No.: 24-1271 PCT of service. Based on the subscription data of the respective UEs, the network may apply different policies which facilitate different levels of service

[0147] For example, access and mobility policies may relate to service area restrictions, RAT / frequency selection priority (RFSP, where RAT stands for radio access technology), authorization and prioritization of access type (e.g., LTE versus NR), and / or selection of non-3GPP access (e.g., Access Network Discovery and Selection Policy (ANDSP)). The service area restrictions may comprise a list of tracking areas where the UE is allowed to be served (or forbidden from being served). The access and mobility policies may include a UE route selection policy (URSP)) that influences routing to an established PDU session or a new PDU session. As noted above, different policies may be obtained and / or enforced based on subscription data of the UE, location of the UE (i.e., location of the AN and / or AMF), or other suitable factors.

[0148] At 1050, AMF#2 may update a context of a PDU session. For example, if the UE has an existing PDU session, the AMF#2 may coordinate with an SMF to activate a user plane connection associated with the existing PDU session. The SMF may update and / or release a session management context of the PDU session (Nsmf_PDUSession_UpdateSMContext, Nsmf_ PDUSession_ ReleaseSM Context).

[0149] At 1060, AMF#2 sends a registration accept message to the AN, which forwards the registration accept message to the UE. The registration accept message may include a new UE identifier and / or a new configured slice identifier. The UE may transmit a registration complete message to the AN, which forwards the registration complete message to the AMF#2. The registration complete message may acknowledge receipt of the new UE identifier and / or new configured slice identifier.

[0150] At 1070, AMF#2 may obtain UE policy control information from the PCF. The PCF may provide an access network discovery and selection policy (ANDSP) to facilitate non-3GPP access. The PCF may provide a UE route selection policy (URSP) to facilitate mapping of particular data traffic to particular PDU session connectivity parameters. As an example, the URSP may indicate that data traffic associated with a particular application should be mapped to a particular SSC mode, network slice, PDU session type, or preferred access type (3GPP or non-3GPP).

[0151] FIG. 11 illustrates an example of a service request procedure for a wireless device (e.g., a UE). The service request procedure depicted in FIG. 11 is a network-triggered service request procedure for a UE in a CM-IDLE state. However, other service request procedures (e.g., a UE-triggered service request procedure) may also be understood by reference to FIG. 11 , as will be discussed in greater detail below.

[0152] At 1110, a UPF receives data. The data may be downlink data for transmission to a UE. The data may be associated with an existing PDU session between the UE and a DN. The data may be received, for example, from a DN and / or another UPF. The UPF may buffer the received data. In response to the receiving of the data, the UPF may notify an SMF of the received data. The identity of the SMF to be notified may be determined based on the received data The notification may be, for example, an N4 session report. The notification may indicate that the UPF has received data associated with the UE and / orDocket No.: 24-1271 PCT a particular PDU session associated with the UE. In response to receiving the notification, the SMF may send PDU session information to an AMP. The PDU session information may be sent in an N1 N2 message transfer for forwarding to an AN. The PDU session information may include, for example, UPF tunnel endpoint information and / or QoS information.

[0153] At 1120, the AMF determines that the UE is in a CM-IDLE state. The determining at 1120 may be in response to the receiving of the PDU session information. Based on the determination that the UE is CM- IDLE, the service request procedure may proceed to 1130 and 1140, as depicted in FIG. 11 . However, if the UE is not CM-IDLE (e.g ., the UE is CM-CONNECTED), then 1130 and 1140 may be skipped, and the service request procedure may proceed directly to 1150.

[0154] At 1130, the AMF pages the UE. The paging at 1130 may be performed based on the UE being CM-IDLE. To perform the paging, the AMF may send a page to the AN. The page may be referred to as a paging or a paging message. The page may be an N2 request message. The AN may be one of a plurality of ANs in a RAN notification area of the UE. The AN may send a page to the UE. The UE may be in a coverage area of the AN and may receive the page.

[0155] At 1140, the UE may request service. The UE may transmit a service request to the AMF via the AN. As depicted in FIG. 11 , the UE may request service at 1140 in response to receiving the paging at 1130. However, as noted above, this is for the specific case of a network-triggered service request procedure. In some scenarios (for example, if uplink data becomes available at the UE), then the UE may commence a UE-triggered service request procedure. The UE-triggered service request procedure may commence starting at 1140.

[0156] At 1150, the network may authenticate the UE. Authentication may require participation of the UE, an AUSF, and / or a UDM, for example, similar to authentication described elsewhere in the present disclosure. In some cases (for example, if the UE has recently been authenticated), the authentication at 1150 may be skipped.

[0157] At 1160, the AMF and SMF may perform a PDU session update. As part of the PDU session update, the SMF may provide the AMF with one or more UPF tunnel endpoint identifiers. In some cases (not shown in FIG. 11), it may be necessary for the SMF to coordinate with one or more other SMFs and / or one or more other UPFs to set up a user plane.

[0158] At 1170, the AMF may send PDU session information to the AN. The PDU session information may be included in an N2 request message. Based on the PDU session information, the AN may configure a user plane resource for the UE. To configure the user plane resource, the AN may, for example, perform an RRC reconfiguration of the UE. The AN may acknowledge to the AMF that the PDU session information has been received. The AN may notify the AMF that the user plane resource has been configured, and / or provide information relating to the user plane resource configuration.

[0159] In the case of a UE-triggered service request procedure, the UE may receive, at 1170, a NASDocket No.: 24-1271 PCT service accept message from the AMF via the AN. After the user plane resource is configured, the UE may transmit uplink data (for example, the uplink data that caused the UE to trigger the service request procedure).

[0160] At 1180, the AMF may update a session management (SM) context of the PDU session. For example, the AMF may notify the SMF (and / or one or more other associated SMFs) that the user plane resource has been configured, and / or provide information relating to the user plane resource configuration. The AMF may provide the SMF (and / or one or more other associated SMFs) with one or more AN tunnel endpoint identifiers of the AN. After the SM context update is complete, the SMF may send an update SM context response message to the AMF.

[0161] Based on the update of the session management context, the SMF may update a PCF for purposes of policy control. For example, if a location of the UE has changed, the SMF may notify the PCF of the UE's a new location.

[0162] Based on the update of the session management context, the SMF and UPF may perform a session modification. The session modification may be performed using N4 session modification messages. After the session modification is complete, the UPF may transmit downlink data (for example, the downlink data that caused the UPF to trigger the network-triggered service request procedure) to the UE. The transmitting of the downlink data may be based on the one or more AN tunnel endpoint identifiers of the AN.

[0163] FIG. 12 illustrates an example of a protocol data unit (PDU) session establishment procedure for a wireless device (e.g., a UE). The UE may determine to transmit the PDU session establishment request to create a new PDU session, to hand over an existing PDU session to a 3GPP network, or for any other suitable reason.

[0164] At 1210, the UE initiates PDU session establishment. The UE may transmit a PDU session establishment request to an AMF via an AN. The PDU session establishment request may be a NAS message. The PDU session establishment request may indicate: a PDU session ID; a requested PDU session type (new or existing); a requested DN (DNN); a requested network slice (S-NSSAI); a requested SSC mode; and / or any other suitable information. The PDU session ID may be generated by the UE. The PDU session type may be, for example, an Internet Protocol (IP)-based type (e.g., IPv4, IPv6, or dual stack IPv4 / IPv6), an Ethernet type, or an unstructured type.

[0165] The AMF may select an SMF based on the PDU session establishment request. In some scenarios, the requested PDU session may already be associated with a particular SMF. For example, the AMF may store a UE context of the UE, and the UE context may indicate that the PDU session ID of the requested PDU session is already associated with the particular SMF. In some scenarios, the AMF may select the SMF based on a determination that the SMF is prepared to handle the requested PDU session. For example, the requested PDU session may be associated with a particular DNN and / or S-NSSAI, andDocket No.: 24-1271 PCT the SMF may be selected based on a determination that the SMF can manage a PDU session associated with the particular DNN and / or S-NSSAI.

[0166] At 1220, the network manages a context of the PDU session. After selecting the SMF at 1210, the AMF sends a PDU session context request to the SMF. The PDU session context request may include the PDU session establishment request received from the UE at 1210. The PDU session context request may be a Nsmf_ PDUSession_CreateSMContext Request and / or a Nsmf_PDUSession_UpdateSMContext Request. The PDU session context request may indicate identifiers of the UE; the requested DN; and / or the requested network slice. Based on the PDU session context request, the SMF may retrieve subscription data from a UDM. The subscription data may be session management subscription data of the UE. The SMF may subscribe for updates to the subscription data, so that the PCF will send new information if the subscription data of the UE changes. After the subscription data of the UE is obtained, the SMF may transmit a PDU session context response to the AMG. The PDU session context response may be a Nsmf_ PDUSession_ Creates M Context Response and / or a Nsmf_PDUSession_UpdateSMContext Response. The PDU session context response may include a session management context ID.

[0167] At 1230, secondary authorization / authentication may be performed, if necessary. The secondary authorization / authentication may involve the UE, the AMF, the SMF, and the DN. The SMF may access the DN via a Data Network Authentication, Authorization and Accounting (DN AAA) server.

[0168] At 1240, the network sets up a data path for uplink data associated with the PDU session. The SMF may select a PCF and establish a session management policy association. Based on the association, the PCF may provide an initial set of policy control and charging rules (PCC rules) for the PDU session. When targeting a particular PDU session, the PCF may indicate, to the SMF, a method for allocating an IP address to the PDU Session, a default charging method for the PDU session, an address of the corresponding charging entity, triggers for requesting new policies, etc. The PCF may also target a service data flow (SDF) comprising one or more PDU sessions. When targeting an SDF, the PCF may indicate, to the SMF, policies for applying QoS requirements, monitoring traffic (e.g., for charging purposes), and / or steering traffic (e.g., by using one or more particular N6 interfaces).

[0169] The SMF may determine and / or allocate an IP address for the PDU session. The SMF may select one or more UPFs (a single UPF in the example of FIG. 12) to handle the PDU session. The SMF may send an N4 session message to the selected UPF. The N4 session message may be an N4 Session Establishment Request and / or an N4 Session Modification Request. The N4 session message may include packet detection, enforcement, and reporting rules associated with the PDU session. In response, the UPF may acknowledge by sending an N4 session establishment response and / or an N4 session modification response.

[0170] The SMF may send PDU session management information to the AMF. The PDU session management information may be a session service request (e.g.,Docket No.: 24-1271 PCTNamf_Communication_N1 N2MessageTransfer) message. The PDU session management information may include the PDU session ID. The PDU session management information may be a NAS message. The PDU session management information may include N1 session management information and / or N2 session management information. The N1 session management information may include a PDU session establishment accept message. The PDU session establishment accept message may include tunneling endpoint information of the UPF and quality of service (QoS) information associated with the PDU session.

[0171] The AMP may send an N2 request to the AN. The N2 request may include the PDU session establishment accept message. Based on the N2 request, the AN may determine AN resources for the UE. The AN resources may be used by the UE to establish the PDU session, via the AN, with the DN. The AN may determine resources to be used for the PDU session and indicate the determined resources to the UE. The AN may send the PDU session establishment accept message to the UE. For example, the AN may perform an RRC reconfiguration of the UE. After the AN resources are set up, the AN may send an N2 request acknowledge to the AMF. The N2 request acknowledge may include N2 session management information, for example, the PDU session ID and tunneling endpoint information of the AN.

[0172] After the data path for uplink data is set up at 1240, the UE may optionally send uplink data associated with the PDU session. As shown in FIG. 12, the uplink data may be sent to a DN associated with the PDU session via the AN and the UPF.

[0173] At 1250, the network may update the PDU session context. The AMF may transmit a PDU session context update request to the SMF. The PDU session context update request may be a Nsmf_PDUSession_UpdateSMContext Request. The PDU session context update request may include the N2 session management information received from the AN. The SMF may acknowledge the PDU session context update. The acknowledgement may be a Nsmf_PDUSession_UpdateSMContext Response. The acknowledgement may include a subscription requesting that the SMF be notified of any UE mobility event. Based on the PDU session context update request, the SMF may send an N4 session message to the UPF. The N4 session message may be an N4 Session Modification Request. The N4 session message may include tunneling endpoint information of the AN. The N4 session message may include forwarding rules associated with the PDU session. In response, the UPF may acknowledge by sending an N4 session modification response.

[0174] After the UPF receives the tunneling endpoint information of the AN, the UPF may relay downlink data associated with the PDU session. As shown in FIG. 12, the downlink data may be received from a DN associated with the PDU session via the AN and the UPF.

[0175] FIG. 13 illustrates examples of components of the elements in a communications network. FIG. 13 includes a wireless device 1310, a base station 1320, and a physical deployment of one or more network functions 1330 (henceforth “deployment 1330”). Any wireless device described in the present disclosure may have similar components and may be implemented in a similar manner as the wireless device 1310.Docket No.: 24-1271 PCTAny other base station described in the present disclosure (or any portion thereof, depending on the architecture of the base station) may have similar components and may be implemented in a similar manner as the base station 1320. Any physical core network deployment in the present disclosure (or any portion thereof, depending on the architecture of the base station) may have similar components and may be implemented in a similar manner as the deployment 1330.

[0176] The wireless device 1310 may communicate with base station 1320 over an air interface 1370. The communication direction from wireless device 1310 to base station 1320 over air interface 1370 is known as uplink, and the communication direction from base station 1320 to wireless device 1310 over air interface 1370 is known as downlink. Downlink transmissions may be separated from uplink transmissions using FDD, TDD, and / or some combination of duplexing techniques. FIG. 13 shows a single wireless device 1310 and a single base station 1320, but it will be understood that wireless device 1310 may communicate with any number of base stations or other access network components over air interface 1370, and that base station 1320 may communicate with any number of wireless devices over air interface 1370.

[0177] The wireless device 1310 may comprise a processing system 1311 and a memory 1312. The memory 1312 may comprise one or more computer-readable media, for example, one or more non- transitory computer readable media. The memory 1312 may include instructions 1313. The processing system 1311 may process and / or execute instructions 1313. Processing and / or execution of instructions1313 may cause wireless device 1310 and / or processing system 1311 to perform one or more functions or activities. The memory 1312 may include data (not shown). One of the functions or activities performed by processing system 1311 may be to store data in memory 1312 and / or retrieve previously-stored data from memory 1312. In an example, downlink data received from base station 1320 may be stored in memory 1312, and uplink data for transmission to base station 1320 may be retrieved from memory 1312. As illustrated in FIG. 13, the wireless device 1310 may communicate with base station 1320 using a transmission processing system 1314 and / or a reception processing system 1315. Alternatively, transmission processing system 1314 and reception processing system 1315 may be implemented as a single processing system, or both may be omitted and all processing in the wireless device 1310 may be performed by the processing system 1311. Although not shown in FIG. 13, transmission processing system1314 and / or reception processing system 1315 may be coupled to a dedicated memory that is analogous to but separate from memory 1312, and comprises instructions that may be processed and / or executed to carry out one or more of their respective functionalities. The wireless device 1310 may comprise one or more antennas 1316 to access air interface 1370.

[0178] The wireless device 1310 may comprise one or more other elements 1319. The one or more other elements 1319 may comprise software and / or hardware that provide features and / or functionalities, for example, a speaker, a microphone, a keypad, a display, a touchpad, a satellite transceiver, a universalDocket No.: 24-1271 PCT serial bus (USB) port, a hands-free headset, a frequency modulated (FM) radio unit, a media player, an Internet browser, an electronic control unit (e.g., for a motor vehicle), and / or one or more sensors (e.g an accelerometer, a gyroscope, a temperature sensor, a radar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, a camera, a global positioning sensor (GPS) and / or the like). The wireless device 1310 may receive user input data from and / or provide user output data to the one or more one or more other elements 1319. The one or more other elements 1319 may comprise a power source. The wireless device1310 may receive power from the power source and may be configured to distribute the power to the other components in wireless device 1310. The power source may comprise one or more sources of power, for example, a battery, a solar cell, a fuel cell, or any combination thereof.

[0179] The wireless device 1310 may transmit uplink data to and / or receive downlink data from base station 1320 via air interface 1370. To perform the transmission and / or reception, one or more of the processing system 1311 , transmission processing system 1314, and / or reception system 1315 may implement open systems interconnection (OSI) functionality. As an example, transmission processing system 1314 and / or reception system 1315 may perform layer 1 OSI functionality, and processing system1311 may perform higher layer functionality. The wireless device 1310 may transmit and / or receive data over air interface 1370 using one or more antennas 1316. For scenarios where the one or more antennas 1316 include multiple antennas, the multiple antennas may be used to perform one or more multi-antenna techniques, such as spatial multiplexing (e.g., single-user multiple-input multiple output (MIMO) or multiuser MIMO), transmit / receive diversity, and / or beamforming.

[0180] The base station 1320 may comprise a processing system 1321 and a memory 1322. The memory 1322 may comprise one or more computer-readable media, for example, one or more non-transitory computer readable media. The memory 1322 may include instructions 1323. The processing system 1321 may process and / or execute instructions 1323. Processing and / or execution of instructions 1323 may cause base station 1320 and / or processing system 1321 to perform one or more functions or activities. The memory 1322 may include data (not shown). One of the functions or activities performed by processing system 1321 may be to store data in memory 1322 and / or retrieve previously-stored data from memory 1322. The base station 1320 may communicate with wireless device 1310 using a transmission processing system 1324 and a reception processing system 1325. Although not shown in FIG. 13, transmission processing system 1324 and / or reception processing system 1325 may be coupled to a dedicated memory that is analogous to but separate from memory 1322, and comprises instructions that may be processed and / or executed to carry out one or more of their respective functionalities. The wireless device 1320 may comprise one or more antennas 1326 to access air interface 1370.

[0181] The base station 1320 may transmit downlink data to and / or receive uplink data from wireless device 1310 via air interface 1370 To perform the transmission and / or reception, one or more of the processing system 1321 , transmission processing system 1324, and / or reception system 1325 mayDocket No.: 24-1271 PCT implement OSI functionality. As an example, transmission processing system 1324 and / or reception system 1325 may perform layer 1 OSI functionality, and processing system 1321 may perform higher layer functionality. The base station 1320 may transmit and / or receive data over air interface 1370 using one or more antennas 1326. For scenarios where the one or more antennas 1326 include multiple antennas, the multiple antennas may be used to perform one or more multi-antenna techniques, such as spatial multiplexing (e.g., single-user multiple-input multiple output (MIMO) or multi-user MIMO) , transmit / receive diversity, and / or beamforming.

[0182] The base station 1320 may comprise an interface system 1327. The interface system 1327 may communicate with one or more base stations and / or one or more elements of the core network via an interface 1380. The interface 1380 may be wired and / or wireless and interface system 1327 may include one or more components suitable for communicating via interface 1380. In FIG 13, interface 1380 connects base station 1320 to a single deployment 1330, but it will be understood that wireless device 1310 may communicate with any number of base stations and / or CN deployments over interface 1380, and that deployment 1330 may communicate with any number of base stations and / or other CN deployments over interface 1380. The base station 1320 may comprise one or more other elements 1329 analogous to one or more of the one or more other elements 1319.

[0183] The deployment 1330 may comprise any number of portions of any number of instances of one or more network functions (NFs). The deployment 1330 may comprise a processing system 1331 and a memory 1332. The memory 1332 may comprise one or more computer-readable media, for example, one or more non-transitory computer readable media. The memory 1332 may include instructions 1333. The processing system 1331 may process and / or execute instructions 1333. Processing and / or execution of instructions 1333 may cause the deployment 1330 and / or processing system 1331 to perform one or more functions or activities. The memory 1332 may include data (not shown). One of the functions or activities performed by processing system 1331 may be to store data in memory 1332 and / or retrieve previously- stored data from memory 1332. The deployment 1330 may access the interface 1380 using an interface system 1337. The deployment 1330 may comprise one or more other elements 1339 analogous to one or more of the one or more other elements 1319.

[0184] One or more of the systems 1311 , 1314, 1315, 1321 , 1324, 1325, and / or 1331 may comprise one or more controllers and / or one or more processors. The one or more controllers and / or one or more processors may comprise, for example, a general-purpose processor, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) and / or other programmable logic device, discrete gate and / or transistor logic, discrete hardware components, an on-board unit, or any combination thereof. One or more of the systems 1311 , 1314, 1315, 1321 , 1324, 1325, and / or 1331 may perform signal coding / processing, data processing, power control, input / output processing, and / or any other functionality that may enable wireless device 1310, base stationDocket No.: 24-1271 PCT1320, and / or deployment 1330 to operate in a mobile communications system.

[0185] Many of the elements described in the disclosed embodiments may be implemented as modules. A module is defined here as an element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (e.g. hardware with a biological element) or a combination thereof, which may be behaviorally equivalent. For example, modules may be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab and / or the like) or a modeling / simulation program such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript. It may be possible to implement modules using physical hardware that incorporates discrete or programmable analog, digital and / or quantum hardware. Examples of programmable hardware comprise computers, microcontrollers, microprocessors, DSPs, ASICs, FPGAs, and complex programmable logic devices (CPLDs). Computers, microcontrollers and microprocessors may be programmed using languages such as assembly, C, C++ and / or the like. FPGAs, ASICs and CPLDs are often programmed using hardware description languages (HDL) such as VHSIC hardware description language (VHDL) or Verilog that configure connections between internal hardware modules with lesser functionality on a programmable device. The mentioned technologies are often used in combination to achieve the result of a functional module.

[0186] The wireless device 1310, base station 1320, and / or deployment 1330 may implement timers and / or counters. A timer / counter may start at an initial value. As used herein, starting may comprise restarting. Once started, the timer / counter may run. Running of the timer / counter may be associated with an occurrence. When the occurrence occurs, the value of the timer / counter may change (for example, increment or decrement). The occurrence may be, for example, an exogenous event (for example, a reception of a signal, a measurement of a condition, etc.), an endogenous event (for example, a transmission of a signal, a calculation, a comparison, a performance of an action or a decision to so perform, etc.), or any combination thereof. In the case of a timer, the occurrence may be the passage of a particular amount of time. However, it will be understood that a timer may be described and / or implemented as a counter that counts the passage of a particular unit of time. A timer / counter may run in a direction of a final value until it reaches the final value. The reaching of the final value may be referred to as expiration of the timer / counter. The final value may be referred to as a threshold. A timer / counter may be paused, wherein the present value of the timer / counter is held, maintained, and / or carried over, even upon the occurrence of one or more occurrences that would otherwise cause the value of the timer / counter to change. The timer / counter may be un-paused or continued, wherein the value that was held, maintained, and / or carried over begins changing again when the one or more occurrence occur. A timer / counter may be set and / or reset. As used herein, setting may comprise resetting. When the timer / counter sets and / or resets, the value of the timer / counter may be set to the initial value. A timer / counter may be started and / orDocket No.: 24-1271 PCT restarted. As used herein, starting may comprise restarting. In some embodiments, when the timer / counter restarts, the value of the timer / counter may be set to the initial value and the timer / counter may begin to run.

[0187] FIGS. 14A, 14B, 14C, and 14D illustrate various example arrangements of physical core network deployments, each having one or more network functions or portions thereof. The core network deployments comprise a deployment 1410, a deployment 1420, a deployment 1430, a deployment 1440, and / or a deployment 1450. Each deployment may be analogous to, for example, the deployment 1330 depicted in FIG. 13. In particular, each deployment may comprise a processing system for performing one or more functions or activities, memory for storing data and / or instructions, and an interface system for communicating with other network elements (for example, other core network deployments). Each deployment may comprise one or more network functions (NFs) The term NF may refer to a particular set of functionalities and / or one or more physical elements configured to perform those functionalities (e.g., a processing system and memory comprising instructions that, when executed by the processing system, cause the processing system to perform the functionalities). For example, in the present disclosure, when a network function is described as performing X, Y, and Z, it will be understood that this refers to the one or more physical elements configured to perform X, Y, and Z, no matter how or where the one or more physical elements are deployed. The term NF may refer to a network node, network element, and / or network device.

[0188] As will be discussed in greater detail below, there are many different types of NF and each type of NF may be associated with a different set of functionalities. A plurality of different NFs may be flexibly deployed at different locations (for example, in different physical core network deployments) or in a same location (for example, co-located in a same deployment). A single NF may be flexibly deployed at different locations (implemented using different physical core network deployments) or in a same location. Moreover, physical core network deployments may also implement one or more base stations, application functions (AFs), data networks (DNs), or any portions thereof. NFs may be implemented in many ways, including as network elements on dedicated or shared hardware, as software instances running on dedicated or shared hardware, or as virtualized functions instantiated on a platform (e.g., a cloud-based platform).

[0189] FIG. 14A illustrates an example arrangement of core network deployments in which each deployment comprises one network function. A deployment 1410 comprises an NF 1411 , a deployment 1420 comprises an NF 1421 , and a deployment 1430 comprises an NF 1431. The deployments 1410, 1420, 1430 communicate via an interface 1490. The deployments 1410, 1420, 1430 may have different physical locations with different signal propagation delays relative to other network elements. The diversity of physical locations of deployments 1410, 1420, 1430 may enable provision of services to a wide area with improved speed, coverage, security, and / or efficiency.Docket No.: 24-1271 PCT

[0190] FIG. 14B illustrates an example arrangement wherein a single deployment comprises more than one NF. Unlike FIG. 14A, where each NF is deployed in a separate deployment, FIG. 14B illustrates multiple NFs in deployments 1410, 1420. In an example, deployments 1410, 1420 may implement a software-defined network (SDN) and / or a network function virtualization (NFV).

[0191] For example, deployment 1410 comprises an additional network function, NF 1411A. The NFs 1411 , 1411A may consist of multiple instances of the same NF type, co-located at a same physical location within the same deployment 1410. The NFs 1411 , 1411A may be implemented independently from one another (e.g., isolated and / or independently controlled). For example, the NFs 1411, 1411A may be associated with different network slices. A processing system and memory associated with the deployment 1410 may perform all of the functionalities associated with the NF 1411 in addition to all of the functionalities associated with the NF 1411A In an example, NFs 1411 , 1411A may be associated with different PLMNs, but deployment 1410, which implements NFs 1411 , 1411 A, may be owned and / or operated by a single entity.

[0192] Elsewhere in FIG. 14B, deployment 1420 comprises NF 1421 and an additional network function, NF 1422. The NFs 1421 , 1422 may be different NF types. Similar to NFs 1411 , 1411A, the NFs 1421 , 1422 may be co-located within the same deployment 1420, but separately implemented. As an example, a first PLMN may own and / or operate deployment 1420 having NFs 1421 , 1422. As another example, the first PLMN may implement NF 1421 and a second PLMN may obtain from the first PLMN (e.g., rent, lease, procure, etc.) at least a portion of the capabilities of deployment 1420 (e.g., processing power, data storage, etc.) in order to implement NF 1422 As yet another example, the deployment may be owned and / or operated by one or more third parties, and the first PLMN and / or second PLMN may procure respective portions of the capabilities of the deployment 1420. When multiple NFs are provided at a single deployment, networks may operate with greater speed, coverage, security, and / or efficiency.

[0193] FIG. 14C illustrates an example arrangement of core network deployments in which a single instance of an NF is implemented using a plurality of different deployments. In particular, a single instance of NF 1422 is implemented at deployments 1420, 1440. As an example, the functionality provided by NF 1422 may be implemented as a bundle or sequence of subservices. Each subservice may be implemented independently, for example, at a different deployment. Each subservices may be implemented in a different physical location By distributing implementation of subservices of a single NF across different physical locations, the mobile communications network may operate with greater speed, coverage, security, and / or efficiency.

[0194] FIG. 14D illustrates an example arrangement of core network deployments in which one or more network functions are implemented using a data processing service. In FIG. 14D, NFs 1411 , 1411 A, 1421 , 1422 are included in a deployment 1450 that is implemented as a data processing service. The deployment 1450 may comprise, for example, a cloud network and / or data center. The deployment 1450 may be ownedDocket No.: 24-1271 PCT and / or operated by a PLMN or by a non-PLMN third party. The NFs 1411 , 1411 A, 1421 , 1422 that are implemented using the deployment 1450 may belong to the same PLMN or to different PLMNs. The PLMN(s) may obtain (e.g . , rent, lease, procure, etc.) at least a portion of the capabilities of the deployment 1450 (e.g., processing power, data storage, etc.). By providing one or more NFs using a data processing service, the mobile communications network may operate with greater speed, coverage, security, and / or efficiency.

[0195] As shown in the figures, different network elements (e.g., NFs) may be located in different physical deployments, or co-located in a single physical deployment. It will be understood that in the present disclosure, the sending and receiving of messages among different network elements is not limited to interdeployment transmission or intra-deployment transmission, unless explicitly indicated.

[0196] In an example, a deployment may be a ‘black box' that is preconfigured with one or more NFs and preconfigured to communicate, in a prescribed manner, with other ‘black box’ deployments (e.g., via the interface 1490). Additionally, or alternatively, a deployment may be configured to operate in accordance with open-source instructions (e.g., software) designed to implement NFs and communicate with other deployments in a transparent manner. The deployment may operate in accordance with open RAN (O-RAN) standards.

[0197] FIG. 15 illustrates an example of ambient internet-of-thing (AloT) communications as per an aspect of an embodiment of the present disclosure. The AloT communications may comprise communication(s) between a reader and an AloT device. AloT may be interchangeable with A-loT.

[0198] The reader may comprise a base station (AN 102 in FIG. 1A, gNB 152A in FIG. 1 B) The reader may comprise a wireless device (e.g., Wireless device 101 in FIG. 1A, UE 151 in FIG. 1 B).

[0199] An AloT device may refer to a device (e.g., wireless device) and / or a thing with sensors, processing ability, software and other technologies that connect and exchange data with other devices and systems (e.g., reader) over communications networks (e.g., AN 102, CN 105). An AloT device may be low- cost and self-powered device.

[0200] An AloT device may be referred to as an ambient intelligence device, an ambient power-enabled loT device, an ambient computing device, and / or the like. The AloT device may comprise a hardware, e.g., a sensor, actuator, gadget, appliance, or machine, that may be programmed for certain applications. The AloT device may be a smart watch, smart eyewear, smart refrigerator, smart door lock, and so on. The AloT device may be battery-free based on energy harvested from ambient sources.

[0201] In the AloT communications, multiple readers may communicate with one or more AloT devices. For example, in FIG. 15, Reader 1 and Reader 2 communicate with AloT device 1. In the AloT communications, a reader may communicate with one or more AloT devices. For example, in FIG. 15, Reader 2 communicates with AloT device 1 and AloT device 2.

[0202] A communication channel from a reader to an AloT device may be referred to as a reader-to-Docket No.: 24-1271 PCT device channel (e.g., R2D channel), AloT downlink channel, a sidelink channel from a reader to an AloT device, a R2D sidelink channel, and / or the like. In the present disclosure, for a sake of simplicity, a communication channel from a reader to an AloT device may be referred to as an R2D channel.

[0203] A communication channel from an AloT device to a reader may be referred to as a device-to- reader channel (e.g., D2R channel), AloT uplink channel, a sidelink channel from an AloT device to a reader, a D2R channel, and / or the like. In the present disclosure, for a sake of simplicity, a communication channel from an AloT device to a reader may be referred to as a D2R channel.

[0204] An AloT device may refer to a device primarily or substantially powered by harvesting energy from one or more viable ambient loT energy sources. The AloT device may be battery-less or with limited energy storage capability (e.g., using a capacitor). The one or more viable ambient loT energy sources may comprise radio waves (e.g., radio frequency (RF) wave). The one or more viable ambient loT energy sources may comprise light, motion, heat, or any other suitable power sources.

[0205] An AloT device may harvest the energy from radio waves. The AloT device may receive, from a reader or energy source (e.g., RF emitter), a radio wave (e.g., carrier wave). The AloT device may store the harvested energy in an energy storage. The AloT device may use the harvested energy for transmitting a signal to the reader via D2R channel(s). For example, the AloT device may transmit, to the reader, a reflected (e.g., backscatter) signal using the power converted from the harvested energy.

[0206] An AloT device may employ, use, transmit, trigger, initiate, and / or perform a transmission of a backscatter signal. The backscatter signal or backscatter transmission may be referred to as ambient backscatter, bistatic communication, and / or the like. Transmitting a backscatter signal may comprise reflecting, by the AloT device, waves, particles, or signals back in the direction from which they were detected. The backscatter signal may be a backscatter (or backscattered) information signal and / or a backscatter (or backscattered) modulated information signal.

[0207] For example, the AloT device may modify and / or reflect the received signal with encoded data by using the power converted from the harvested energy. The encoded data may include a response to a command. Antennas on other devices (e.g., a reader) may, in turn, detect the signal reflected by the AloT device.

[0208] In an example, the backscatter may be a method of communication in which an AloT device with a limited capability (e.g., a device without a battery or without any internal power source) receives energy from a reader's (e.g., RF emitter's) transmission. The AloT device may use at least a portion of the received energy to send back a reply. The AloT device may receive the energy via electromagnetic waves propagated from an RF emitter (e.g., a reader, an intermediate wireless device, a continuous wave (CW) transmitter, and / or the like). Once the waves reach the AloT device, the energy may travel through the AloT device's internal antenna, and activates the chip, or integrated circuit (IC). The remaining energy may be modulated with the chip's data and flows back via the AloT device’s antenna to the reader's antenna in theDocket No.: 24-1271 PCT form of electromagnetic waves. For example, the remaining energy is used as and / or is converted to the transmission power of the backscatter signal transmitted by the AloT device to the reader.

[0209] Harvesting an energy from radio (e.g., RF) wave may be used for data decoding, signal filtering operation, data reception, data encoding, and / or data transmission. A purpose of harvesting the energy may be to energize the AloT device and / or to charge a battery of the AloT device. The AloT device may perform the one or more tasks using the harvested energy. The AloT device may perform the one or more tasks based at least in part on an accumulation of harvested energy over a period of time.

[0210] The harvested energy may be derived from a radio wave (e.g., RF signals) transmitted by a network (e.g., a reader, a base station and / or an RF emitter) and / or by a wireless device (e.g., an intermediate / assisting wireless device) connected to the network. The AloT device may communicate with the network using the harvested energy and / or power (e.g., transmitting and / or receiving power) converted from the harvested energy. For example, RF energy harvesting may lead to a longer battery lifespan of the AloT device with a battery. RF energy harvesting may lead to a battery-less loT device, such as a medical sensor or an implanted sensor.

[0211] An amount of energy that the AloT device harvests from the radio wave may depend on one or more parameters. For example, the one or more parameters comprise a frequency of the radio wave. For example, the one or more parameters comprise a distance (e.g., between an RF emitter and the AloT device) traveled by the radio wave. For example, the one or more parameters comprise a transmission power of the radio wave. For example, the one or more parameters comprise a received power (e.g., received signal strength, RSRP, and / or the like), of the radio wave, measured by the AloT device. The signal source (e.g., transmitter) of the radio wave may be a network entity (or node) such as a base station (e.g., AN 102) in FIG. 1A (and / or gNB 152A, ng-eNB 152B, and / or NG-RAN 152 in FIG. 1 B) and / or another device, such as a wireless device (e.g., an intermediate / assisting wireless device) connected to the wireless device 101 in FIG. 1A (and / or UE 151 in FIG. 1B).

[0212] The AloT device may perform the energy harvesting from various energy sources, such as solar, vibration, thermal, laser or light, and / or RF. Energy harvesting from a solar source may use photovoltaic cells, may provide a relatively high power density, and / or may require exposure to light (not implantable). Energy harvesting from a vibration source may use piezoelectric, electrostatic, and / or electromagnetic techniques. Energy harvesting from a vibration source may be implantable and / or may suffer from material physical limitations. Energy harvesting from a thermal source may use thermoelectric or pyroelectric techniques. Energy harvesting from a thermal source may provide a relatively high power density. Energy harvesting from a thermal source may be implantable, and / or may produce excess heat. Energy harvesting from RF (a radio wave) may use an antenna may be implantable. Energy harvesting from RF (a radio wave) may provide a relatively low power density where an efficiency is inversely proportional to a distance.

[0213] Referring to FIG. 15, a transmitter of an energy signal may transmit, to an AloT device, an energyDocket No.: 24-1271 PCT signal to energize the AloT device.

[0214] The transmitter may be a reader. For example, the reader comprises the transmitter.

[0215] The transmitter may not be a reader. For example, the transmitter may be a network entity or node deployed separately from the reader. For example, the transmitter may be an RF emitter.

[0216] The energy signal may be a continuous waveform and / or continuous wave. The energy signal may be an unmodulated signal. The reader may transmit, to an AloT device, one or more AloT commands. For example, the transmitter may transmit the energy signal prior to the one or more AloT commands. For example, a channel via which the transmitter transmits the energy signal may be referred to as a CW-to- Device (CW2D) channel.

[0217] For example, a channel (e.g., CW2D channel) via which the transmitter transmits the energy signal may be a R2D channel For example, the R2D channel may comprise the CW2D channel, e.g , if the reader comprises the transmitter transmitting the energy signal. For example, the CW2D channel may comprise the R2D channel.

[0218] For example, a channel (e.g., CW2D channel) via which the transmitter transmits the energy signal may be different from the R2D channel. For example, the CW2D channel is different from the R2D channel, e.g., if the reader does not comprise the transmitter transmitting the energy signal.

[0219] Referring to FIG. 15, an AloT device may receive, from the transmitter (e.g., reader) and via CW2D channel, an energy signal. The AloT device may comprise an RF energy harvester. For example, the RF energy harvester may comprise a rectifier performing RF signal alternating current (AC) to direct current (DC) conversion. The AloT device may comprise an energy storage (e.g., capacitor). The energy storage may store harvested energy from the RF energy harvester. The AloT device may supply the harvested energy to active component blocks (e.g., decoder, encoder, backscatter modulator, and / or the like) of the AloT device.

[0220] Referring to FIG. 15, an AloT device may receive, from the reader and via R2D channel, one or more AloT commands. The AloT device may transmit, to the reader and via D2R channel, a backscatter modulated information signal using the transmit power. The backscatter modulated information signal may comprise one or more responses respective to the one or more AloT commands. The backscatter modulated information signal may be referred to as a backscatter signal, a backscattering signal, and / or the like.

[0221] The AloT device may determine the transmit power based on an amount of harvested energy and / or an amount of stored energy. For example, the AloT device may couple its transmitter to its receiver with either load modulation or backscatter, e.g., depending on whether the AloT device is operating in the near-field or far-field of the reader. The coupling (e.g., its transmitter to its receiver) may be the transfer of energy from one medium to another medium. For example, the AloT device uses it to obtain power and transfer data. For example, the type of coupling used, e.g., inductive coupling or backscatter coupling (alsoDocket No.: 24-1271 PCT known as radiative coupling), depends on the frequency and the distance between the AloT device and the reader's antenna. For example, the inductive coupling uses near-field effects For example, the backscatter coupling uses far-field effects.

[0222] In the present embodiments, for example, the backscatter signal refers to a signal using the transmit power that the wireless device determines based on an amount of harvested energy and / or an amount of stored energy. For example, the AloT device obtains and / or determines the transmit power, used for the backscatter signal, using inductive coupling and / or backscatter coupling.

[0223] For example, the transmit power based on the amount of harvested (and / or stored) energy that the AloT device obtained from a signal (e.g., RF signal) received from the reader may be referred to as a backscattered power. For example, the backscattered power may be referred to as the backscattered power of the signal (e.g., RF signal) received from the reader. For example, the backscattered power may be referred to as the backscattered power of the received energy (and / or power) of the signal (e.g., RF signal) received from the reader.

[0224] The AloT device may comprise an antenna shared for the RF energy harvester and receiver / transmitter of the AloT device. The AloT device may comprise at least one first antenna and / or at least one second antenna. The at least one first antenna may be dedicated for the RF energy harvester. The at least one second antenna may be dedicated for the receiver to receiving the energy signal and / or AloT commands. The at least one second antenna may be dedicated for the transmitter to transmit the backscatter modulated information signal.

[0225] An AloT device may be categorized based on its capability of energy storage, a transmitting signal generation, and / or amplification of transmitting signal.

[0226] For example, an AloT device may be referred to as Device 1 (or Device A). The AloT device categorized as Device 1 may have (or support) peak power consumption less than or equal to 1 piW peak power consumption. The AloT device categorized as Device 1 may have energy storage. The AloT device categorized as Device 1 may have initial sampling frequency offset (SFO) up to 10X ppm. The AloT device categorized as Device 1 may have neither DL nor UL amplification in the device. The UL transmission of the AloT device categorized as Device 1 may be backscattered on a carrier wave provided externally.

[0227] For example, an AloT device may be referred to as Device 2a (or Device B). The AloT device categorized as Device 2a may have (or support) peak power consumption less than or equal to a few hundred W peak power consumption. The AloT device categorized as Device 2a may have (or support) energy storage. The AloT device categorized as Device 2a may have (or support) initial sampling frequency offset (SFO) up to 10X ppm. The AloT device categorized as Device 2a may have (or support) both DL and / or UL amplification in the device. The UL transmission of the AloT device categorized as Device 2a may be backscattered on a carrier wave provided externally.

[0228] For example, an AloT device may be referred to as Device 2b (or Device C). The AloT deviceDocket No.: 24-1271 PCT categorized as Device 2b may have (or support) peak power consumption less than or equal to a few hundred W peak power consumption. The AloT device categorized as Device 2b may have (or support) energy storage. The AloT device categorized as Device 2b may have (or support) initial sampling frequency offset (SFO) up to 10X ppm. The AloT device categorized as Device 2b may have (or support) both DL and / or UL amplification in the device. The UL transmission of the AloT device categorized as Device 2b may be generated internally by the AloT device.

[0229] A (e.g., maximum) message size of the AloT device may be approximately 1000 bits to be received by the AloT device. A (e.g., maximum) message size of the AloT device may be approximately 1000 bits to be transmitted from the AloT device. The one-way end-to-end (e.g., maximum) latency (e.g., including query / triggering time) of the AloT device may be from 1 second to 10 seconds. The (e.g., maximum) connection density of the AloT communications may be about 150 AloT devices per 100 m2 for indoor scenarios. The (e.g., maximum) connection density of the AloT communications may be about 20 AloT devices per 100 m2 for outdoor scenarios. The AloT device may be a fixed or static (not moving) device. The AloT device may have a moving speed of 10 km / h, e.g., at least for indoor scenarios.

[0230] IG. 16 illustrates an example of AloT device architecture as per an aspect of an embodiment of the present disclosure. The block diagrams in FIG. 16 may be an example AloT device architecture of Device 1 . For example, the AloT device may comprise one or more antennas. The one or more antenna may be either shared or separate for RF energy harvester and receiver / transmitter. For example, the AloT device may comprise a block for a matching network. The matching network may be to match impedance between antenna and other components (including RF energy harvester and receiver related blocks). For example, the AloT device may comprise an RF energy harvester. The RF energy harvester may comprise rectifier performing RF signal (AC) to DC conversion. For example, the AloT device may comprise an energy storage (e.g., capacitor). The energy storage may store harvested energy from RF energy harvester. For example, the AloT device may comprise a power management unit (PMU). The PMU may manage storing energy to energy storage from energy harvester and supplying power to active component blocks which needs power supply.

[0231] In FIG. 16, the AloT device may comprise a digital baseband (BB) logic. The digital BB logic may include functional blocks like encoder, decoder, controller, etc. For example, the AloT device may comprise a memory. The memory may comprise at least one of Non-Volatile Memory (NVM) and / or registers. For example, the NVM may comprise an Erasable Programmable Read-Only Memory (EEPROM), e.g., for permanently storing device ID, etc. For example, the registers may be for temporarily keeping information for its operation, e.g., while energy is available for the operation in energy storage. For example, the AloT device may comprise a clock generator. The clock generator may provide clock signal(s).

[0232] In FIG 16, the AloT device may comprise an RF signal (e g., AloT signal) reception related blocks. For example, the AloT device may comprise RF band-pass filter (BPF), e.g., for improving selectivity. TheDocket No.: 24-1271 PCTRF BPF may be optional to be implemented in the AloT device. For example, the AloT device may comprise an RF envelope detector. The RF envelop detector may convert RF signal to baseband. For example, the AloT device may comprise a BB low-pass filter (LPF). The BB LPF may filter out harmonics and high frequency components to improve input signal quality to comparator. The BB LPF may be optional to be implemented in the AloT device. For example, the AloT device may comprise a comparator that determines high / low of input signal.

[0233] In FIG. 16, the AloT device may comprise transmission related blocks. For example, the AloT device may comprise a backscatter modulator. The backscatter modulator may switch impedance to modulate backscattered signal with Tx signal (e.g., an AloT signal transmitted via a D2R channel) from BB logics.

[0234] FIG. 17 illustrates an example of AloT device architecture as per an aspect of an embodiment of the present disclosure. The block diagrams in FIG. 17 may be an example AloT device architecture of Device 2a. Comparing with the AloT device architecture in FIG. 16, the AloT device architecture in FIG. 17 may further comprise one or more additional blocks. The one or more additional blocks may comprise a low-noise amplifier (LNA). The LNA may improve a signal strength and sensitivity of receiver. The one or more additional blocks may comprise a BB amplifier. The BB amplifier may amplify a BB signal to improve signal strength. The one or more additional blocks may comprise a reflection amplifier. The reflection amplifier may amplify reflected backscattered signal. The one or more additional blocks may comprise a large frequency shifter. The large frequency shifter (e.g., tens of MHz) may shift a backscattered signal from one frequency (e.g., FDD-DL frequency) to another frequency (e.g., FDD-UL frequency).Docket No.: 24-1271 PCT

[0235] In FIG. 17, the AloT device may comprise an N-bit analog-to-digital converter (ADC), e.g., instead of the comparator. The AloT device may have one or more energy source. For example, the AloT device may comprise an RF energy harvester for harvesting an energy from an RF signal (e.g., radio wave). The RF energy harvester may include a rectifier performing RF signal (AC) to DC conversion. The AloT device may comprise an energy harvester (other than the RF energy harvester) for energy harvesting from energy source(s) other than the RF signal.

[0236] FIG. 18 illustrates an example of AloT device architecture as per an aspect of an embodiment of the present disclosure. The block diagrams in FIG. 18 may be an example AloT device architecture of Device 2b. Comparing with the AloT device architectures in FIG. 16 and / or FIG. 17, the AloT device architecture in FIG. 18 may further comprise one or more additional blocks. The one or more additional blocks may comprise a Tx modulator, e.g., where baseband bits are modulated according to modulation scheme. The Tx modulator block may be a part of BB logic. The one or more additional blocks may comprise a digital to analog converter (DAC) that converts digital signal to analog signal. The one or more additional blocks may comprise a low pass filter (LPF) for filtering out undesired signal. The one or more additional blocks may comprise a mixer that performs up-converting baseband signal to RF range. The one or more additional blocks may comprise a local oscillator (LO) for carrier frequency generation. The block diagrams in FIG. 18 may comprise a phase locked loop (PLL) and / or a frequency locked loop (FLL) that are used to generate frequencies suitable for the LO in a respective frequency range. The one or more additional blocks may comprise a power amplifier (PA) that amplifies TX signal, if present.

[0237] In FIG 15, FIG. 16, FIG. 17, and / or FIG. 18, the RF energy harvester and the reception related blocks may operate in a simultaneous manner with. For example, an RF energy harvester of the AloT device may receive RF signals from a first set of antennas. For example, a reception related blocks of the AloT device may receive RF signals from a second set of antennas.

[0238] In FIG. 15, FIG. 16, FIG. 17, and / or FIG. 18, the AloT device may comprise common antenna(s) shared between the energy harvester and the reception related blocks. For example, the common antenna(s) between the energy harvester and the reception related blocks may receive RF signals. The received RF signals may be split into two streams for the energy harvester and the reception related blocks. For example, a power of the received RF signals may be split between the energy harvester and the reception related blocks. For example, the AloT device may switch the antenna(s) between the RF energy harvester and the reception related blocks using time switching. For example, RF signals received at the antenna(s) may be directed to the energy harvester when a path is switched to be directed to the energy harvester. The RF signals received at the antenna(s) may be directed to the reception related blocks, e.g., when a path is switched to be directed to the reception related blocks.

[0239] The AloT communications may comprise one or more topologies. The one or more topologies may comprise at least one of: a topology for an AloT direct network communication, a topology for an AloTDocket No.: 24-1271 PCTIndirect network communication, and / or a topology for an AloT device to UE direct communication.

[0240] FIG. 19A illustrates an aspect of an example embodiment according to the present disclosure. The topology in FIG. 19A may be an example of an AloT direct network communication. For example, the AloT direct network communication comprises an AloT device and a network node (Network or reader in FIG. 19A). The topology for the AloT direct network communication may comprise a direct link between the network node and the AloT device.

[0241] In an AloT direct network communication, the AloT device may directly and / or bidirectionally communicates, via the direct link, with the network node. The communication between the network node and the AloT device may include AloT data and / or signaling.

[0242] The topology in FIG. 19A may comprise a second direct link between the AloT device and a second network node. For example, the network node transmits, to the AloT device and via a first direct link, one or more signal and / or AloT data. The AloT device may transmit, to the second network node and via the second direct link, one or more second signals and / or a second AloT data. For example, the network node transmitting to the AloT device may be a different from the second network node receiving from the AloT device.

[0243] In the AloT direct network communication, the direct link may comprise and / or referred to as a downlink, an uplink, a sidelink, an AloT link, and / or the like. The direct link from the network node to the AloT device may comprise an R2D channel. The direct link from the AloT device to the network node may comprise a D2R channel.

[0244] FIG. 19B, FIG. 19C, and FIG. 19D illustrate an aspect of example embodiments according to the present disclosure. The topologies in FIG. 19B, FIG. 19C, and FIG. 19D may be examples of an AloT device communication comprising an indirect link. For example, a topology for an AloT indirect network communication comprises an AloT device, a network node (Network in FIG. 19A), and / or a wireless device. The wireless device may be Intermediate wireless device in FIG. 19B and / or Assisting wireless device in FIG. 19C and / or in FIG. 19D. The AloT indirect network communication may comprise communication(s) between the AloT device and the network. In the AloT indirect network communication, there is a wireless device that helps in conveying information between the AloT device and the network. For example, the wireless device may be referred to as an intermediate (wireless) device, an assisting (wireless) device, and / or the like. In FIG. 19B, FIG. 19C, and FIG. 19D, Network may comprise at least one of: a base station, a cell, a transmission-reception point (TRP), a repeater, a relay, and / or an integrated access and backhaul (IAB) node.

[0245] FIG. 19B illustrates an aspect of an example embodiment according to the present disclosure. The AloT indirect network communication in FIG. 19B may not comprise a direct link between the AloT device and the network. The communications between the AloT device and the network may be via a wireless device (e.g., Intermediate wireless device in FIG. 19B). The wireless device may relay and / or conveyDocket No.: 24-1271 PCT control information (AloT signaling) and / or AloT data generated / transmitted by the network to the AloT device. The wireless device may relay and / or convey control information and / or AloT data / signaling generated / transmitted by the AloT device to the network.

[0246] For example, the wireless device in FIG. 19B may be referred to as an intermediate wireless device (e.g., an intermediate device and / or an intermediate node). The intermediate wireless device may be referred to as a reader, an interrogator, and / or the like.

[0247] The intermediate wireless device may receive, from the network (e.g., base station) and via a downlink channel (e.g., PDCCH and / or PDSCH), AloT data and / or a control signal. For example, the intermediate wireless device may transmit, to the AloT device, the AloT data and / or a control signal.

[0248] The intermediate wireless device may receive, from the AloT device, AloT data / signaling. For example, the intermediate wireless device may transmit, e.g., via an uplink channel (e.g., PUCCH and / or PUSCH), to the network, the AloT device, AloT data / signaling. The link between the intermediate wireless device and the network may comprise an uplink (e.g., PUCCH and / or PUSCH). The link between the intermediate wireless device and the network may comprise downlink (e.g., PDCCH and / or PDSCH). The link between the intermediate wireless device and the AloT device may comprise a sidelink, AloT link and / or the like.

[0249] The intermediate wireless device may comprise a wireless device, relay, IAB node, a second cell, a second base station, a reader, an interrogator, an access point, and / or the like. The intermediate wireless device may transmit, to the AloT device, an RF signal (e.g., energy signal and / or wireless energy transmission). The AloT device may harvest, from the RF signal, an energy to be used for AloT communication(s).

[0250] FIG. 19C and FIG. 19D illustrate an aspect of example embodiments according to the present disclosure. The topologies in FIG. 19C and in FIG. 19D may comprise an AloT indirect network communication between the AloT device and the network node (Network in FIG. 19C and / or in FIG. 19D). The topologies in FIG. 19C and in FIG. 19D may comprise a direct link between the AloT device and the network node. The communications between the AloT device and the network may be via a wireless device (e.g., Assisting wireless device in FIG. 19C and / or in FIG. 19D). Between the AloT device and the network, there are a direct link (e.g., Uu link in FIG. 19C and / or FIG. 19D) and an indirect link.

[0251] For example, the direct link in FIG. 19C may be for transmission between the network and the AloT device. For example, the direct link may be for transmission from the AloT device to the network. For example, the indirect link may be for transmission from the network to the AloT device. For example, the direct link may comprise a link between Network and AloT device in FIG. 19C. For example, the indirect link (e.g., Uu link and / or downlink) may comprise a link between the network and Assisting wireless device in FIG. 19C. For example, the indirect link (e g., R2D link or channel) may comprise a link between AloT device and Assisting wireless device in FIG. 19C.Docket No.: 24-1271 PCT

[0252] In FIG. 19C, the network may transmit a control signal (e.g., AloT signaling) and / or AloT data to the wireless device via an Uu link. The Uu link may comprise a downlink, PDSCH, PBCH, PDCCH, and / or a sidelink. The wireless device may convey (relay, forward, and / or transmit), to the AloT device and via R2D channel, the control signal and / or the AloT data that the wireless device receives from the network. The AloT device may transmit a second control signal and / or second AloT data to the network via the direct link. The direct link may comprise a D2R link (or channel), uplink, and / or sidelink. The second control signal and / or second AloT data may comprise the response to the received control signal and / or AloT data from the wireless device.

[0253] For example, the direct link in FIG. 19D may be for transmission between the network and the AloT device. For example, the direct link may be for transmission from the network to the AloT device. For example, the indirect link may be for transmission from the AloT device to the network. For example, the direct link may comprise a link between Network and AloT device in FIG. 19D. For example, the indirect link (e.g., Uu link and / or uplink) may comprise a link between the network and Assisting wireless device in FIG. 19D. For example, the indirect link (e.g., D2R link or channel) may comprise a link between AloT device and Assisting wireless device in FIG. 19D.

[0254] In FIG. 19D, the network may transmit a control signal (e.g., AloT signaling) and / or AloT data to AloT device via a direct link. The direct link may comprise a downlink, PDSCH, PBCH, PDCCH, and / or an R2D link (or channel). The AloT device may transmit a second control signal and / or second AloT data to the network via the indirect link. For example, the AloT device may transmit the second control signal and / or second AloT data to the wireless device via a link between the AloT device and the wireless device. The link between the AloT device and the wireless device may comprise an uplink, a sidelink and / or a D2R link (or channel). The wireless device may convey (relay, forward, and / or transmit), to the network and via Uu link, the second control signal and / or second AloT data that the wireless device receives from the AloT device. The Uu link may comprise an uplink, PUCCH, PUSCH, and / or a sidelink

[0255] Referring to FIG. 19C and in FIG. 19D, the wireless device may be referred to as an assisting wireless device (e.g., an intermediate wireless device, an assisting device and / or an assisting node), a reader, an interrogator, and / or the like.

[0256] For example, the assisting wireless device may receive, from the network (e.g., base station) and via a Uu link comprising a downlink channel (e.g., PDCCH and / or PDSCH), AloT data and / or a control signal (AloT signaling). The assisting wireless device may convey (relay, forwards, and / or transmits), to the AloT device via an R2D link (or channel), the AloT data and / or the control signal.

[0257] For example, the assisting wireless device may receive, from the AloT device and via a D2R link (or channel), AloT data and / or a control signal. The assisting wireless device conveys (relays, forwards, and / or transmits), to the network (e.g., base station) and via a Uu link comprising an uplink channel (e.g., PUCCH and / or PUSCH), AloT data and / or a control signal.Docket No.: 24-1271 PCT

[0258] Referring to FIG. 19C and in FIG. 19D, the link (e.g . , Uu link) between the assisting wireless device and the network may comprise an uplink (e.g., PUCCH and / or PUSCH) and / or downlink (e.g., PDCCH and / or PDSCH). The link between the assisting wireless device and the AloT device may comprise an R2D link (or channel), a D2R link (or channel), a sidelink, AloT link, and / or the like. The assisting wireless device may comprise a wireless device, relay, IAB device, a second cell, a second base station, a reader, an interrogator, an access point, and / or the like. The assisting wireless device may transmit, to the AloT device, a signal (e.g., RF signal, energy signal, wireless energy transmission) from which the AloT device harvests an energy to be used for AloT communication(s).

[0259] FIG. 19E illustrate an aspect of example embodiments according to the present disclosure. The topology in FGI. 21E may be for an AloT device to a wireless device direct communication. The topology may comprise a communication between an AloT device and an Ambient capable wireless device (Wireless device in FIG. 19E) with no network node in the middle. The AloT device communicates bidirectionally with the wireless device. The communication between the wireless device and the AloT device may comprise the AloT data and / or signaling. The communication link between the wireless device and the AloT device may comprise a sidelink (e.g., comprising a sidelink channel such as PSFCH, PSSCH, PSCCH, PSDCH, and / or the like), AloT link, and / or the like. For example, a channel or link from the wireless device to the AloT device may comprise a R2D link or R2D channel. For example, a channel or link from the AloT device to the wireless device may comprise a D2R link or D2R channel.

[0260] The device-to-device (D2D) communication may comprise AloT communications and / or AloT topologies The D2D communication may comprise a communication between a network node and an AloT device. The D2D communication may comprise a communication between a wireless device and an AloT device.

[0261] A link defined, included, and used for the D2D communication may be referred to as a sidelink (SL). The link used for the D2D communication may be referred to as other terminologies, e.g., an loT link, an AloT link, a D2D link, and / or the like.

[0262] In the present disclosure, a reader may comprise a network node (e.g., a base station, a base station central unit, a base station distributed unit, a TRP, an IAB node, a cell, and / or a relay). In the present disclosure, a reader may comprise a wireless device (e.g., an assisting wireless device, and / or an intermediate wireless device) that a network assigns as a reader.

[0263] The AloT communications may comprise an inventory procedure. The inventory procedure may refer to a procedure, a process, and / or an operation by which a reader identifies one or more AloT devices. The inventory procedure may be referred to as an inventory process, an inventory operation, AloT device population, and / or the like.

[0264] The inventory procedure may comprise or be referred to as a random access procedure. For example, the inventory procedure may comprise a procedure, a process, and / or an operation that initiate aDocket No.: 24-1271 PCT random access of one or more AloT devices. For example, each AloT device accesses to a network (e.g. , reader) using a randomly selected radio resource (e.g., slot and / or frequency), e.g., in response to, during, or after the inventory procedure.

[0265] The inventory procedure may comprise or be referred to as a paging procedure. For example, the inventory procedure may comprise a procedure, a process, and / or an operation that initiate one or more AloT devices to perform one or more procedures (e.g., random access procedure). For example, an AloT device receives, from a reader, a paging message during the inventory procedure. For example, an AloT device initiates the inventory procedure, e.g., in response to or after receiving the paging message.

[0266] The paging message may initiate the one or more procedures (e.g., random access procedure and / or inventory procedure). The paging message may comprise a trigger indication that initiate the one or more procedures (e.g., random access procedure and / or inventory procedure). An AloT device may initiate the one or more procedures (e.g., random access procedure and / or inventory procedure) in response to receiving the paging message and / or the trigger indication.

[0267] The paging message may comprise one or more parameters for one or more procedures (e.g., random access procedure and / or inventory procedure). For example, the one or more parameters comprise an identifier of one or more AloT devices, a group identifier of one or more AloT devices, one or more bits (e.g., least significant bit (LSB) and / or most significant bit (MSB)) of an identifier of one or more AloT devices. The field containing (or carrying) the one or more bits may be referred to as a mask field. An AloT device that has a respective identifier matching to the one or more bits may initiate the one or more procedures. For example, an LSB of the identifier of the AloT device matches to the one or more bits. For example, an MSB of the identifier of the AloT device matches to the one or more bits.

[0268] AloT services may comprise an inventory service, an inventory & command service, a command (only) service. An AloT network / system may provide / support / operate the AloT services. FIG. 20 illustrates an example as per an aspect of an embodiment of the present disclosure, the basic AloT network nodes / functions / components (e.g., AloT device, AloT reader, AloT Function (AloTF), AF (application function)) for the AloT services. In an example, the AF may be an application function / server which is owned by cellular operators or 3’ rd party service provider. The owner of the AF may own one or more AloT devices for the AloT service. The AF may request and provide the inventory and command service. In an example, the AF may be owned / operated by a warehouse operator (e.g., Walmart, Amazon). The AloTF (AloT Function) may be a core network node and acts as a coordinator or bridge point between one or more AFs and one or more AloT readers. The AloTF may be owned / operated by a cellular operator and provide interfaces with the AFs and one or more AloT readers. The AloT reader may interact with one or more AloT devices via the AloT radio interface. The AloT radio may comprise and / or refer to a radio interface between AloT device and AloT reader. AloT reader may comprise RAN reader (for topology 1 , FIG. 19A, AloT RAN reader) and UE reader (for topology 2, FIG. 19B, AloT UE reader). In an example, theDocket No.: 24-1271 PCTAloT reader may support two different reader type. The reader type may comprise a RAN reader and a UE reader. The reader type may comprise a RAN type and UE type For the RAN reader, a base station (gNB) may act as an AloT reader (RAN reader) and may cover larger area (e.g ., a coverage of a warehouse). The RAN reader may be located in one place and does not move. The RAN reader may do the AloT reader operation based on a request from the AF and AloTF. The RAN reader (base station) may do the inventory and / or command operations with AloT devices. For the UE reader, a wireless device (UE) may act as an AloT reader (and do the AloT reader operation). The UE reader may cover relatively smaller area (smaller coverage area) compared to the RAN reader. The UE reader may comprise a wireless device (Wireless device 101 in FIG. 1A, UE 151 in FIG. 1 B) and an AloT reader function. The UE reader may moves from / to different area and may be implemented as a handheld device. The RAN reader may comprise a RAN / AN / base station (AN 102 in FIG. 1A, NG-RAN 152 in FIG. 1 B) and the AloT reader function. In an example, the AloT reader function may comprise sending AloT paging messages and receiving response for the paging messages from the AloT device, interacting with AloTF for AloT services. AloT Function, AloTF and AIOTF is interchangeable each other.

[0269] In an example, the AloT reader operation / AloT service / reader function may comprise an inventory and a command operation / service. The AloT inventory may be to identify (e.g., existence, location, tracking) one or more AloT devices. The AloT command may comprise read, write, enable, disable. The reading command (e.g., command type: read) may comprise reading of a specific memory field of one or more AloT devices. The writing command (e.g., command type: write) may comprise writing to a specific memory filed of one or more AloT devices. The disabling command (e.g., command type: disable) may comprise disabling (e.g., turn off the RF transmission of the AloT device) of one or more AloT devices. The enabling command (e.g., command type: enable) may comprise enabling (e.g., turn on the RF transmission of the AloT device) of one or more AloT devices and indicating do the AloT service.

[0270] In an example, the command operation / service may be standalone operation or performed with the inventory operation / service (e.g., performing command procedure after the inventory) together.

[0271] As illustrated in FIG. 20, the AF 1 may request to AloTF 1 , an AloT inventory service for all AloT devices located in the Area 1 . The AF 1 may send an AloT message, to the AloTF 1 , requesting an AloT inventory service for the Area 1 . In response to receiving the AloT message, the AloTF 1 may select AloT reader A which covers the Area 1 . The AloTF 1 may request the AloT inventory service (e.g., identify the AloT devices in the Area 1) to the AloT reader by sending an AloT inventory service request. In response to receiving the request from the AloTF 1 , the AloT reader A may send AloT paging messages for the inventory. In an example, the paging messages may be for all AloT devices. In Area 1 , there may be the AloT device 1 and the AloT device 2. In response to receiving the AloT paging messages, the AloT device 1 and the AloT device 2 may respond to the AloT reader A. The AloT device 1 and AloT device 2 may send AloT identifies of the AloT device 1 and AloT device 2 to AloT reader A, respectfully. In response toDocket No.: 24-1271 PCT receiving the response messages from the AloT device 1 and AloT device 2, the AloT reader A may indicate to the AloTF 1 , the successful inventory result. The successful inventory result may comprise the AloT identifies of the AloT device 1 and AloT device 2. The AloT 1 may respond to the AF 1 with the inventory result. Accordingly, the AF 1 recognize that the AloT device 1 and AloT device 2 are located inside the Area 1.

[0272] FIG. 21 A illustrates the interface of the AloT RAN reader and FIG. 21 B illustrates the interface of the AloT UE reader. The AloT UE reader (FIG .21 B) may comprise AloT enabled wireless device and AloT reader function (e.g., capability of the reader operation). The AloT UE reader may connect to the AloT CN (e.g., AloTF, AMF, SMF, UPF) via base station (AloT enabled base station) and the interface between the AloT UE reader and the base station may be Uu interface. The AloT UE reader may be a wireless device and capable of the reader function to communicate with the AloT device. Wireless device may be installed in the AloT UE reader.

[0273] FIG. 22 illustrates an example as per an aspect of an embodiment of the present disclosure. FIG.22 depicts an AloT system / network architecture for the AloT UE reader case (topology 2). The AloT system / network architecture may be based on the cellular network architecture (e.g., 5G system, 6G system) as illustrated in FIG. 3. In an example, the UE reader may be a wireless device. The UE reader may comprise the wireless device. The UE reader may comprise the wireless device and a reader function (e.g., capability for the reader operation). Network functions (e.g., AMF, SMF, UPF, UDM, UPF) may be used to provide connectivity / mobility of the UE reader to a data network (e.g., internet, application service, application function, application provider). The connectivity to the AloTF may be provided by the cellular network. Connectivity, for transmitting and receiving data, between the UE reader and the AloTF may be realized via control plane path or user plane path.

[0274] In an example, the UE reader and the AloTF may communicate / connect via control plane path (CP path / solution). The control plane path may be via AMF using the SRB (signaling radio bearer). The control plane path may comprise an RRC signaling / message, NG interface (e.g., N2 interface) and SBI (service based interface). The RRC signaling / message may be between the UE reader and the AN (g NB, base station, AloT enabled base station). The NG interface (e.g., N2 interface) may be between the AN and the AMF. The SBI (service based interface) may be between the AMF and the AloTF. AloTF may invoke AMF service (e.g., AMF N1 N2 message transfer service) to send an AloT message to the UE reader via the SBI. AMF may invoke AloTF service to subscribe / register a newly detected UE reader.

[0275] The UE reader and the AloTF may communicate via user plane path (UP path / solution). As described in FIG. 22, the user plan path may comprise the Uu interface (DRB / data radio bearer), the N3 interface (e.g., NG-U interface) between the AN and the UPF, the N6 interface between the UPF and the AloTF. The user plane path may be access agnostic and provide scalability for larger data compared to the control plane path. The user plane path may be available via the 3GPP access radio or the non-3GPPDocket No.: 24-1271 PCT access radio. The user plane path / solution may be used for large data transmission. In an example, aggregated data from AloT devices may be large for the control plane path, then the user plane path / solution may be used for larger data transmission / reception between the UE reader and the AloTF.

[0276] FIG. 23 illustrates a protocol stack for the user plane (path / solution) architecture for AloT (topology 2). A protocol stack of the AloT device may comprise the AloT AS layer, the AloT non-access stratum (NAS) layer and the AloT data layer. From the UE reader side (e.g., AloT enabled wireless device), the interface between the UE reader and the AloT device may be the AloT AS layer. For the UE reader side, the protocol stack, interacting with the network (NG-RAN / AN, UPF, AloTF), may comprise the Uu AS layer (Uu interface), the PDU layer, the IP transport layer and the AloT UE reader control layer. In an example, the UE reader and the AloTF may interact using AloT application protocol (AP) (AloT-AP) via the AloT UE reader control layer. The AloT AP will be established above the PDU session via UPF. An AloT NAS layer may be terminated in the AloTF and the AloT device and used to communicate between the AloTF and AloT device. The AloT AP layer may encapsulate the AloT NAS layer. The AloT NAS layer may encapsulate the AloT Data.

[0277] FIG. 24 illustrates an example as per an aspect of an embodiment of the present disclosure. A wireless device may be a UE reader (AloT UE reader) and may register to the network (e.g., AloT system / network in FIG. 22). The wireless device may send a registration request message to an AMF via a base station (gNB). In an example, the base station may support the AloT UE reader operation. The base station may indicate, in SIB (system information block) message, the AloT UE reader operation to the wireless device. The registration message may comprise a AloT (UE) reader capability. The AloT reader capability may indicate the intention / request to act as a AloT reader of the wireless device. In response to receiving the registration request message, the registration procedure will be executed by the AMF and with other network functions (e.g., UDM, AloTF, AUSF) as illustrated in FIG. 10. During the registration procedure (FIG. 10), the AMF may query subscription information from UDM / UDR for the AloT UE reader operation. If the subscription information of the wireless device in the UDM / UDR indicates that the wireless device is authorized for the AloT UE reader, the AMF may store the authorization information in the UE context of the wireless device. After a successful registration procedure (and authorized for the AloT UE reader), the AMF may send a registration accept message to the wireless device indicating the AloT authorization information. The registration accept message may comprise the AloT authorization information, an indicator indicating successful registration of the wireless device to the network. The AloT authorization information may indicate whether the wireless device is authorized / allowed for the AloT UE reader operation. The AloT authorization information may further indicate a time period and / or a serving area for the AloT UE reader operation. The AMF may indicate to the base station, the AloT authorization information of the wireless device. The base station may use the authorization information for AloT (radio) resource allocation. In an example, the base station may reject an AloT resource request from the wirelessDocket No.: 24-1271 PCT device or the AloTF, if the wireless device is not authorized to act as a AloT UE reader.

[0278] In an example, the wireless device may be successfully registered and authorized for the AloT UE reader operation. The AMF may indicate to the AloTF, the wireless device is ready for the AloT reader operation by sending an AloT reader registration request message to the AloTF. The AMF may indicate to the AloTF, the wireless device is a new AloT UE reader candidate.

[0279] In an example, the AloTF may have a list of AloT UE readers (AloT UE reader information). In response to receiving the AloT reader registration request message, the AloTF may add the wireless device to the list of the AloT UE readers. The list of the AloT UE readers may comprise an identity of the wireless device, location / position of the wireless device, serving AMF of the wireless device, user plane path / association for the wireless device, connection status of the wireless device, load information of the wireless device, availability of the wireless device for the AloT UE reader operation. In an example, the identity of the wireless device may comprise SUPI, I MSI , IMEI, GPSI. The location / position of the wireless device may comprise a tracking area (TA) identity, registration area (one or more Tas), cell identity, GPS coordination of the wireless device. The serving AMF of the wireless device may comprise the address of the AMF (e.g., IPv4, IPV6, IPv4v6) . The user plane path / association may indicate an existence of a secure user plane association between the wireless device and the AloTF. Connection status of the wireless device may comprise CM-CONNECTED, CM-IDLE. Connection status of the wireless device may comprise RRC-CONNECTED, RRC-INACTIVE, RRC-IDLE.

[0280] In an example, AloTF may determine to select the wireless device as a UE reader. If there is no secure user plane association with the wireless device, the AloTF may trigger a user plane connection establishment with the wireless device. If there is no secure user plane connection path / association, the AloTF may trigger establishing a secure user plane path / association to the wireless device via a control plane path (CP path, in FIG. 22). The AloTF may request an AMF service by sending a Namf_communication_N1 N2 service request to the AMF (serving AMF). Namf_commnication_N1 N2 service may comprise a user plane connection establishment command for the AloT UE reader operation, an identify of the wireless device. The user plane connection establishment command (message) may comprise a DNN, S-NSSAI, an address of the AloTF. In an example, the AMF may receive the Namf_communication_N1 N2 service request from the AloTF. In response to receiving the Namf_communication_N1 N2 service request, the AMF may send a DL NAS Transport message to the wireless device. DL NAS Transport message may be a downlink non-access stratum (NAS) Transport message. The DL NAS Transport message may be a NAS message and used to transfer signaling message and / or small data packet between the AMF and the wireless device. The DL NAS Transport message may comprise the user plane connection establishment command for the AloT UE reader operation. In an example, user plane connection establishment command for the AloT UE reader operation may be piggybacked into the DL NAS Transport message. The user plane connection establishmentDocket No.: 24-1271 PCT command may comprise the DNN, S-NSSAI and the address of the AloTF. In response to receiving the DL NAS Transport message, comprising the user plane connection establishment command, the wireless device may determine if there is any appropriate PDU session for the user plane connection. In an example, if there is a PDU session for AloT UE reader operation, the PDU session establishment procedure will be skipped. In an example, if there is any established PDU session associated with the DNN and / or S-NSSAI in the user plane connection establishment command message, the PDU session establishment procedure will be skipped. In an example, there is no established PDU session for the AloT UE reader operation. In an example, there is no established PDU session for the DNN and / or the S-NSSAI. The wireless device may trigger a PDU session establishment procedure as illustrated in the FIG. 12 by sending a PDU session establishment request message. The wireless device may send a PDU session establishment request message to the AMF / SMF indicating the DNN and / or S-NSSAI provided in the user plane connection establishment command message (if provided). The DNN and S-NSSAI may be used to identify a UPF providing a connectivity to the AloTF. The wireless device may receive a PDU session establishment accept message from the AMF / SMF. The PDU session establishment accept message may indicate a successful PDU session establishment for the wireless device.

[0281] If there is an established PDU session for the AloT UE reader operation or, the PDU session establishment procedure is successfully completed, the wireless device may request a secure user plane connection association with the AloTF with the address of the AloTF via the PDU session. In response to establishing the secure user plane connection association with the AloTF, the wireless device may send a UL NAS transport (uplink non-access stratum transport) message comprising a user plane establishment complete message to the AMF. The user plane establishment complete message indicate a successful user plane establishment with the AloTF. In response to receiving the UL NAS transport message from the wireless device, the AMF may send the user plane establishment complete message to the AloTF. AloTF may receive the user plane establishment complete message from the wireless device via the AMF. AloTF may update the list of the AloT UE readers. In an example, AloTF may update that the wireless device has (secure) user plane path / association with the wireless device. In an example, the AloTF may receive a AloT service request message from an AF (application Function). The AloTF may select the wireless device as an AloT user reader for the AloT service request. The AloT service request may comprise service type, target AloT devices, service area. The AloTF may select the wireless device if the wireless device can cover the service area of the AloT service request. The AMF may indicate the location / position of the wireless device during the AloT reader registration procedure.

[0282] The AloT device may be battery-less or with limited energy storage. The AloT device may use backscatter technology to reflect radio waves from an loT reader back to the AloT reader, and communicate with the AloT reader. In the existing technology, an AloTF (AloT Function) may select one or more AloT UE readers based on information (e.g., service area, potential location of the AloT devices)Docket No.: 24-1271 PCT provided by the application function. However, the information may not reflect real time information / events from the AloT UE reader and AloT devices. This may decrease the accuracy of AloT service and increase the service time.

[0283] Example embodiments of the present disclosure provide way to improve current and future AloT UE reader selection by providing information of a specific reason / cause of a failure of the AloT service. In response to receiving an AloT service request, the selected AloT UE reader may accept or reject the AloT service request. The decision to reject the AloT service request may be based on ongoing task of the AloT UE reader (e.g., congestion situation). The AloT UE reader (selected AloT UE reader) may indicate, to the AloTF, the cause of rejection. The AloTF may select another AloT UE reader based on the cause of rejection. If the AloT UE accept the AloT service request, the AloTF will wait for the AloT service result of the AloT service request. The AloT UE reader may detect AloT service failure for various reasons (e.g , lack of AloT resources, target AloT device does not have enough energy / battery, and so on) and inform the cause of the failure to the AloTF. Based on the cause of the failure, the AloTF may determine to select another AloT UE reader, or to pause the AloT service. Based on the various reasons provided in the example embodiments, the AloTF may determine to remove or keep the AloT UE reader for the next AloT reader selection.

[0284] FIG. 25 illustrates an example as per an aspect of an embodiment of the present disclosure. In an example, a wireless device may be a AloT UE reader (AloT reader). An AloT UE reader may implement or comprise a wireless device. The wireless device may register with the AloT network / system as illustrated in FIG 24. If the wireless device successfully register with the AloT network / system and is authorized for the AloT UE reader, the wireless device may establish a PDU session with a UPF which support connectivity to a AloTF. The wireless device may establish a secure user plane connection (association) with the AloTF via the PDU session. In an example, AloTF may add the wireless device to a list of AloT UE readers.

[0285] In an example, an application function (AF) may send a AloT service request message to the AloTF. The AloT service request message may comprise an AloT service type, identities of target AloT devices, a service area of the AloT service, number of AloT devices. In an example, the AloT service type may be inventory and command. The command of the AloT service type may comprise read, write, enable and disable. In an example, the identities of target AloT devices may indicate one or more identifiers of one or more AloT devices. In an example, the identities of target AloT devices may indicate a group identifier of a group of AloT devices The identities of target loT devices may indicate any or all AloT devices. In an example, the service area may indicate a region (e.g., tracking area, regional area (e.g., warehouse room number), cell identity of a base station) in which the target AloT devices may be located.

[0286] In response to receiving the AloT service request message from the AF, the AloTF may select a AloT UE reader. This may be a first AloT UE selection for the AloT service request. The AloTF may select the wireless device as the AloT UE reader for the AloT service request. The AloTF may send a firstDocket No.: 24-1271 PCT message to the wireless device for the AloT service request. The AloTF may send the first message to the wireless device using the secure user plane connection with the wireless device via the PDU session (in FIG 24). In an example, the AloTF may send the first message via a UPF. The first message may be an AloT service request message. The first message may be an AloT AP (application protocol) message. The AloTF may determine the first message based on the AloT service request message received from the AF. The first message may comprise AloT service type, a count number of trial / attempt of the AloT service, the target AloT service area, a priority of the AloT service, identifiers of target AloT device(s), an application provider of the AloT service, AloT non-access stratum (NAS) PDU (data unit). In an example, the AloT service type may comprise inventory and command. The command of the AloT service type may comprise read, write, enable and disable. The service area may indicate a region (e.g., tracking area, regional area (e.g , warehouse room number), cell identity of a base station) in which the target AloT devices may be located. In an example, the identifiers of target AloT devices may indicate one or more identifiers of one or more AloT devices or group identifier of a ground of AloT devices. The identifiers of target AloT devices may indicate the target AloT devices for the AloT service by the AF. In an example, the application provider of the AloT service may indicate the identifier of the AF. The application provider of the AloT service may indicate the 3'rd party or ownership of the AloT service (e.g., who requested the AloT service).

[0287] In an example, the count number of trial / attempt of the AloT service may indicate if the AloT service request from the AloTF is first trial / attempt, second trial / attempt or third trial / attempt, and so on. The AloTF may send the first message to a “wireless device 1” for the first trial / attempt (e.g., the first AloT service request) and it may turn out unsuccessful. The AloTF may select a “wireless device 2” for the same AloT service request and send the first message to the “wireless device 2” again. The first message may comprise the count number of trial / attempt of the AloT service indicating 2 if the AloT service request from the AloTF is the second trial / try / attempt. The count number of trial / attempt of the AloT service may be used by the wireless device, prioritizing the incoming AloT service if the count number of trial / attempt is higher number. The wireless device apply different policy based on the count number of trial / attempt. If the count number of trial / attempt is not a 1 'st, the wireless device may prioritize the corresponding AloT service than other AloT services (with the trail / attempt is 1 ’st).

[0288] In response to receiving the first message, the wireless device may determine whether to accept or reject the first message. In an example, the wireless device may determine whether to accept or reject the AloT service request of the first message. The wireless device may determine whether to accept or reject the AloT service based on various factors. The various factors may comprise the first message (based on the contents of the first message), an existence of an ongoing AloT service in the wireless device, load / amount of ongoing AloT service in the wireless device, load / amount of ongoing AloT services in the wireless device, an existence or amounts of computational load in the wireless device, remaining battery of the wireless device, an existence of congestion for AloT service, an existence of congestion for UuDocket No.: 24-1271 PCT service / interface. In an example, the wireless device may reject the AloT service request (the first message) from the AloTF based on the amount of task / work (e.g., ongoing tasks, the amount of the ongoing tasks) of the wireless device. In an example, the wireless device may be busy with ongoing AloT services for previously assigned AloT service from the same AloTF or different AloTF. The wireless device may be busy (or congested) by actively engaged AloT radio and service with ongoing task. In an example, the computing resource of wireless device may be busy and / or congested and can’t receive further task.

[0289] In an example, the wireless device may determine to reject the AloT service. The wireless device may determine to reject the first message. The wireless device may determine that the wireless device can’t execute / perform the AloT request received in the first message. In response to the determination, the wireless device may send a second message to the AloTF indicating the determination / rejection (determination to reject). Based on the determination to reject the AloT service, the wireless device may send the second message indicating a rejection for the AloT service. In an example, the second message may be an AloT service reject message. The second message may comprise a cause value of the rejection, a time period, load information, a location / position of the wireless device, a removal request. In an example, the cause value for the rejection may comprise congestion situations, lack of resources for AloT services, not authorized application provider / application function, authentication failure, integrity failure, not allowed service, there is no secure connection (TLS error), an indicator indicating that the wireless device is not in the AloT service area. In an example, the time period may indicate a time period of the rejection. The time period may indicate a back off time period for the rejection. The time period may indicate how long the wireless device can't accept further AloT services.

[0290] In response to receiving the second message (e.g., AloT service reject message), the AloTF may determine whether to remove the wireless device from the list of the AloT UE readers. The AloTF may determine whether to remove the wireless device from the list of the AloT UE readers temporarily or permanently. The AloTF may determine to remove the wireless device from the list of the AloT UE readers based on the second message. In an example, the AloTF may temporarily remove the wireless device from the list of the AloT UE readers based on the time period. The AloTF may not select the wireless device for a AloT UE reader for the timer period. In an example, the AloTF may select a second wireless device as a AloT UE reader for the same AloT service (rejected AloT service by the wireless device) in the first message. The AloTF may send a second AloT service request to the second wireless device. The second AloT service request message may be same to the first message. The count number of the trail / attempt of the AloT service may be 2'nd.

[0291] FIG. 26 illustrates an example as per an aspect of an embodiment of the present disclosure. The example in FIG. 26 may be similar to the example in FIG. 25. The example embodiments of FIG. 26 shows the case that the wireless device accepts the AloT service request based on the priority and / or application provider of the AloT service. In an example, after successful secure user plane connection establishmentDocket No.: 24-1271 PCT the AloTF may add the wireless device to the list of AloT UE readers. The AloTF may receive the AloT service request message from the AF. In response to receive the AloT service request message from the AF, the AloTF may select AloT UE reader for the AloT service. The wireless device may select the wireless device as a AloT UE reader for the incoming / received AloT service. The AloTF may send the first message (AloT service request message). In response to receiving the first message (AloT service request message) from the AloTF, the wireless device may determine whether to accept or reject the AloT service request / the first message. In an example, the wireless device may experience congestion situations. The wireless device may be busy with ongoing AloT service (e.g., previously assigned AloT services). The wireless device may decide / determine to accept the AloT service, if the priority of the AloT service in the first message (the AloT service request message) is higher priority than the priority of the previously assigned AloT service. The wireless device may pause the existing task (e.g., previously assigned AloT service) and may accept the AloT service request of the first message. In response to determining to accept the AloT service request / first message, the wireless device may send a second message (AloT service accept) message to the AloTF. The second message (AloT service accept) message may indicate an acceptance of the AloT service request. The second message may comprise a time period, a removal request, load information. In response to receiving the second message, the AloTF may understand / recognize that the AloT service is accepted. The AloTF may not select a second wireless device for the second trail / attempt for the AloT service request. The AloT device may determine whether to remove the wireless device from the list of AloT UE readers. In an example, the wireless device may accept the AloT service (from the first message) but does not want to receive second / third AloT service request for the time period. The removal request may explicitly indicate that the wireless device does not (can't) accept additional AloT service request. The AloTF may determine whether to remove the wireless device temporarily or permanently based on the second message.

[0292] FIG. 27 illustrates an example as per an aspect of an embodiment of the present disclosure. The example embodiment of the FIG. 27 may be the case where the wireless device accepts the AloT service request and detect a failure while executing / performing the AloT service request. Similarly described in FIG. 25 and FIG. 26, the wireless device may receive the first message. The first message may comprise AloT service type, a count number of trial / attempt of the AloT service, target AloT service area, priority of the AloT service, identifier of target AloT device(s), application provider of the AloT service, AloT non- access stratum (NAS) PDU (data unit).

[0293] In an example, the wireless device may not busy (e.g., there is no ongoing AloT service). In an example, the wireless device may be busy and the priority of the AloT service request (in the first message) may be higher / better priority than the ongoing AloT service (previously assigned AloT service). The wireless device may accept the AloT service request / the first message. In response to determination to accept the AloT service request, the wireless device may send a second message (AloT service accept) toDocket No.: 24-1271 PCT the AloTF via a UPF. The second message may be an AloT AP message. The wireless device may send the second message via the secure user plane connection above the PDU session with the UPF. The second message may comprise an assistance information. The assistance information may comprise load of AloT service, location / position of the wireless device, an indication indicating whether AloT resource is allocated or not, battery level of the wireless device, service area of the AloT service by the wireless device. In response to receiving the second message, the AloTF may wait for a AloT service result. The AloTF may use the assistance information for the further AloT UE reader selection. The AloT resource may be AloT radio resource.

[0294] In an example, the wireless device may determine to accept the AloT service. The wireless device may request AloT (radio) resources to the base station. The wireless device may send a first radio resource configuration (RRC) message to a base station (serving base station), requesting AloT resources for the AloT service. The first RRC message may comprise a number of AloT devices for the AloT service, size of data, AloT service type, a priority of the AloT service, an AloT service area. The RRC message may be a user equipment information (response) message. The wireless device may be in a CM- CONNECTED / RRC-CONNECTED state. The base station may receive the first RRC message. The base station may determine whether to allocate / assign or how much resource should be allocated / assigned for the AloT service of the wireless device based on the first RRC message and authorization information of the wireless device for the AloT UE reader operation. In an example, the base station may not have the authorization information of the wireless device for the AloT UE reader operation. In an example, the base station may not have enough AloT resource. The base station may experience AloT resource congestion in the AloT service area requested by the wireless device. In an example, the base station may determine not to allocate / assign AloT resources for the wireless device. In an example, the base station may determine not to allocate / assign enough AloT resources for the wireless device. In response to the determination, the base station may send a second RRC message to the wireless device. The second RRC message may be a RRC reconfiguration message. In response to receiving the second RRC message, the wireless device may determine if the wireless device can perform the AloT service with one or more AloT devices or not.

[0295] In an example, the second RRC message may indicate that no AloT resources being allocated for the wireless device. In an example, the second RRC message may indicate that not enough AloT resources being allocated for the wireless device In an example, the second RRC message may indicate that the wireless device is not authorized for the AloT UE reader operation. The wireless device may determine a failure of the AloT service based on the second RRC message. The wireless device may determine the failure of the AloT service based on lack of resources (lack of AloT resources) for the AloT service. In response to the determination, the wireless device may send to the AloTF, a third message (an AloT service failure message) indicating the failure of the AloT service The third message may comprise a cause value of the failure indicating that lack of resources for the AloT service.Docket No.: 24-1271 PCT

[0296] In an example, the base station may allocate AloT (radio) resources for the AloT service. The base station may have valid authorization information of the wireless device for the AloT UE reader operation. The base station does not experience any congestion for AloT resource in the AloT service area. The base station may send a second RRC message indicating the AloT resources for the AloT service. In response to receiving the second RRC message, the wireless device may start / trigger the AloT operation based on the AloT resources. In an example, the wireless device may send AloT paging messages to the target AloT devices. The paging messages may comprise the identifiers / identities of the target AloT devices. The paging messages may further indicate the AloT service type. The AloT device may respond to the AloT paging messages and can successfully complete the AloT service.

[0297] In an example, the wireless device may detect / determine a failure or the AloT services for various reasons The failure may not be based on the issues / problems of the wireless device (AloT UE reader). The failure may be based on the issues / problems of the AloT devices or AloT radio resources during performing / executing the AloT service / operation. In an example, one or more AloT devices may respond to the paging messages and indicate that the AloT device does not have enough energy / battery to complete the AloT service / command (e.g ., write operation). In an example, the command may be a writing operation. In an example, the AloT service type may be an inventory & command. The AloT device may complete the inventory (e.g., response to the paging message) but may not complete the command operation due to lack of battery / energy. In an example, the wireless device may receive an error message / error code from the AloT devices and determines the failure of the AloT service. In an example, the error message / error code may indicate other errors (catch-all for errors not covered by other codes), not supported (the tag does not support the specified parameters of feature), Insufficient privileges, Memory overrun, Memory locked, Cryptographic suite error, Command not encapsulated, Responsebufferoverflow, Security timeout;, insufficient power, and so ne.

[0298] If the wireless device determine the failure of the AloT service, the wireless device may send the third message (AloT service failure) indicating the failure of the AloT service. In an example, the wireless device may not receive any response message from AloT devices. The wireless device may receive error message / error code from the one or more AloT devices. The third message may comprise a cause value for the failure. The cause value (cause value for the failure) may comprise other errors (catch-all for errors not covered by other codes), not supported (the tag does not support the specified parameters of feature), Insufficient privileges, Memory overrun, Memory locked, Cryptographic suite error, Command not encapsulated, Responsebufferoverflow, Security timeout;, insufficient power, lack of AloT resource, congestion of the wireless device, congestion of the AloT resource, not enough energy for the AloT service, time out, out of AloT service area, no response from a AloT device, or no detected AloT device. The wireless device may determine the cause value (cause of the failure) based on the error message / error code received from the AloT devices.Docket No.: 24-1271 PCT

[0299] In an example, the AloTF may receive the third message (AloT service failure message) indicating the failure of the AloT service In response to receiving the third message, the AloTF may determine whether to remove the wireless device from the list of the AloT UE readers. The AloTF may determine whether to remove the wireless device from the list of the AloT UE readers temporarily or permanently. The AloTF may determine to remove the wireless device from the list of the AloT UE readers based on the third message.

[0300] In response to receiving the third message, the AloTF may determine not to remove the AloT UE reader from the list of the AloT UE readers. In an example, the cause value (of the failure) in the third message may indicate that the failure is based on error codes (e.g., insufficient power, memory overrun, other errors) from the one or more AloT devices. The AloTF may determine that the wireless device is possible to accept another AloT service request. Based on the third message, the AloTF may determine whether to perform the AloT service again or not. If the cause value of the third message (AloT service failure message) indicates that “insufficient power (in AloT device)” or “the AloT device does not have enough battery / energy / power (in AloT device)”, the AloTF may wait until the target AloT device recharges the battery / power / energy. AloTF may not start second trial / attempt for the AloT service based on the power / energy / batter recharge time of the AloT devices.

[0301] FIG. 28 illustrates an example as per an aspect of an embodiment of the present disclosure. At 2801 , a reader (e.g., AloT enabled wireless device) may receive an AloT service request. At 2802, the reader may determine whether to accept or reject the AloT service request based on local information (e.g., congestion, ongoing AloT service). The reader may accept the AloT service request. At 2803, the reader may detect / determine a failure of the AloT service. The reader may detect / determines a failure of the AloT service for lack of AloT radio resource. The reader may detect / determines a failure of the AloT service for lack of response from the AloT devices or receives error code indicating “insufficient power / energy / battery”. At 2803, the reader may send an AloT service failure message comprising a cause value of the failure.

Claims

1. Docket No.: 24-1271 PCTCLAIMSWhat is claimed is:

1. A method comprising: sending, by a wireless device to an access and mobility management function (AMF), a registration request message indicating an ambient internet of things (AloT) reader capability; receiving, by the wireless device from the AMF, a registration accept message; receiving, by the wireless device from an AloT device, a failure message comprising a cause value indicating insufficient energy to complete a writing command; and sending, by the wireless device to an AloT function (AIOTF) the cause value.

2. The method of claim 1 , further comprising sending, by the wireless device to the AloT device, a paging message for an AloT inventory.

3. The method of claim 2, wherein the AloT inventory is followed by a command message.

4. The method of claim 2, wherein the AloT inventory is sent by the AIOTF.

5. The method of claim 2, further comprising receiving, by the wireless device from the AloT device, a response message for the paging message.

6. The method of claim 5, further comprising performing, by the wireless device, an AloT service for the writing command with the AloT device, wherein the writing command comprises writing to a memory field of the AloT device.

7. The method of claim 2, wherein the paging message comprises an identifier of the AloT device.

8. A method comprising: receiving, by a wireless device from an ambient internet of thing (AloT) function (AloTF), a first message requesting an AloT service; and sending, by the wireless device to the AloTF, a second message comprising a cause of failure of the AloT service.

9. The method of claim 8, wherein the first message comprises at least one of:AloT service type; a count number of trial of the AloT service; target AloT service area; priority of the AloT service; one or more identifiers of one or more AloT devices; or application provider for the AloT service.

10. The method of claim 9, wherein the AloT service type comprise at least one of: inventory; read; write;Docket No.: 24-1271 PCT enable; or disable.11 . The method of any of claims 8 to 9, further comprising, determining, by the wireless device, whether to accept or reject the AloT service, wherein the determining is based on at least one of: the first message; an existence of an ongoing AloT service in the wireless device; load / amount of ongoing AloT services in the wireless device; an existence or amounts of computational load in the wireless device; remaining battery of the wireless device; an existence of congestion for AloT service; or an existence of congestion for Uu service / interface12. The method of claim 11 , further comprising, sending, by the wireless device to the AloTF, a third message indicating an acceptance of the AloT service, wherein the sending is based on the determining to accept the AloT service.

13. The method of claim 12, wherein the third message may comprise at least one of: load of AloT service; location / position of wireless device; an indication indicating that AloT resource is allocated or not; battery level of the wireless device; or service area of the AloT service by the wireless device.

14. The method of claim 11 , further comprising, sending, by the wireless device to the AloTF, a fourth message indicating a rejection for the AloT service, wherein the sending is based on the determination to reject the AloT service.

15. The method of claim 14, wherein the fourth message comprises at least one of: a cause value for the rejection; time period for the rejection; back off time period for the rejection; or location / position of the wireless device.

16. The method of claim 15, wherein the cause value for the rejection indicates at least one of: congestion situations: lack of resources for AloT services; not authorized application provider / application function; authentication failure; integrity failure; not allowed service;Docket No.: 24-1271 PCT there is no secure connection (TLS error); or that the wireless device is not in an AloT service area.

17. The method of any of claims 8 to 16, further comprising: sending, by the wireless device to a base station, a first radio resource configuration (RRC) message requesting AloT resources for the AloT service; receiving, by the wireless device from the base station, a second RRC message indicating allowed AloT resources; and determining, by the wireless device and based on the second RRC message, the failure of the AloT service.

18. The method of claim 17, wherein the wireless device is in RRC-connected state.

19. The method of claim 17, wherein the wireless device is not authorized for the AloT service.

20. The method of claim 17, the cause of the failure indicates that lack of resources for the AloT service.21 . The method of claim 17, wherein the first RRC message is a user equipment information message.

22. The method of claim 17, wherein the second RRC message is a RRC reconfiguration message.

23. The method of claim 17, wherein the RRC message is a UE information message.

24. The method of claim 17, wherein the base station does not have authorization information of the wireless device for AloT reader operation.

25. The method of any of claims 8 to 24, further comprising: sending, by the wireless device to the AloTF, a third message indicating an acceptance of the AloT service; sending, by the wireless device to an AloT device, one or more AloT page messages comprising at least one or: an identifier of the AloT device; or command type; and receiving, by the wireless device from the AloT device, a AloT response message indicating that the AloT device does not have enough energy to complete the AloT service; and determining, by the wireless device, that the AloT device does not have enough energy to complete the AloT service.

26. The method of claim 25, wherein the cause of the failure indicates that the AloT device does not have enough energy to complete the AloT service.

27. The method of claim 25, wherein the command type is a writing operation.

28. The method of any of claims 8 to 27, wherein the cause of failure may indicates at least one of: other errors; not supported; insufficient privileges;Docket No.: 24-1271 PCT memory overrun; memory locked; cryptographic suite error; command not encapsulated; responsebufferoverflow; security timeout; insufficient power; lack of AloT resource; congestion of the wireless device; congestion of the AloT resource; not enough energy for the AloT service; time out; out of AloT service area; no response from a AloT device; signal strength is below a threshold; or no detected AloT device.

29. The method of any of claims 8 to 28, further comprising: sending, by the wireless device to an access and mobility management function (AMF), a registration request message; and receiving, by a wireless device from the AMF, an accept message for the registration request, indicating: successful registration of the wireless device; and authorization for an ambient loT (AloT) reader operation.

30. The method of claim 29, further comprising: sending, by the wireless device to a session management function (SMF) and based on the authorization, a session establishment request message for a packet data unit (PDU) session for the AloT reader operation; and receiving, by the wireless device from the SMF, a session establishment accept message indicating a successful establishment of the PDU session.31 . The method of claim 30, further comprising: receiving, by the wireless device from the AMF, a first non-access stratum (NAS) message requesting a user plane session for the AloT service (for AloT reader operation), wherein the first NAS message comprises, at least one of: an S-NSSAI;DNN; andDocket No.: 24-1271 PCT an address of the AloTF.

32. The method of claim 31 , wherein the session establishment request message comprise at least one of: the S-NSSAI; and the DNN.

33. The method of claim 31 , wherein the address of the AloTF comprises: fully qualified domain name (FQDN);IPv4;IPv6; orIPv4v6.

34. The method of claim 31 , wherein the NAS message is a user plane connection establishment command message which is encapsulated in a downlink NAS transport message.

35. A method comprising: sending, by an ambient internet of things (AloT) reader to an AloT device, a paging message for an AloT inventory; receiving, by the AloT reader from the AloT device, a response message for the paging; performing, by the AloT reader an AloT service for a writing command with the AloT device, wherein the writing command comprises writing to a memory field of the AloT device; receiving, by the AloT reader from the AloT device, a failure message comprising a cause value indicating insufficient energy to complete the writing command; and sending, by the AloT reader to an AloT function (AIOTF) the cause value.

36. The method of claim 35, wherein the AloT reader is a wireless device.

37. The method of claim 35, further comprising sending, by the AloT reader, a registration request message indicating an AloT reader capability.

38. The method of claim 37, wherein the registration request message is sent to an access and mobility management function (AMF).

39. The method of claim 38, further comprising receiving, by the AloT reader from the AMF, a registration accept message.

40. The method of claim 35, wherein the AloT reader is a base station.41 . An apparatus comprising one or more processors and memory storing instructions that, when executed by the one or more processors, cause the apparatus at least to perform the method according to any one of claims 1-40.

42. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors of a device, cause the device to perform the method according to any one of claims

Images