WO2019220234A1 - Détermination d'une catégorie d'accès défini par un opérateur dans une commande d'accès unifiée - Google Patents

Détermination d'une catégorie d'accès défini par un opérateur dans une commande d'accès unifiée Download PDF

Info

Publication number
WO2019220234A1
WO2019220234A1 PCT/IB2019/053311 IB2019053311W WO2019220234A1 WO 2019220234 A1 WO2019220234 A1 WO 2019220234A1 IB 2019053311 W IB2019053311 W IB 2019053311W WO 2019220234 A1 WO2019220234 A1 WO 2019220234A1
Authority
WO
WIPO (PCT)
Prior art keywords
access
access category
operator
wireless device
network
Prior art date
Application number
PCT/IB2019/053311
Other languages
English (en)
Inventor
Pontus Wallentin
Jens Bergqvist
Ivo Sedlacek
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2019220234A1 publication Critical patent/WO2019220234A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H04W48/06—Access restriction performed under specific conditions based on traffic conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/10—Access restriction or access information delivery, e.g. discovery data delivery using broadcasted information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices

Definitions

  • a user equipment When performing access to a wireless communication system, a user equipment (UE) must signal to the network that it wants to acquire communication opportunities. There are many schemes for how this can be done. For example, a UE can utilize air-interface resources (e.g., times, frequencies) to send a short message that would indicate to the network that a UE wants to communicate. Further details about a certain communication need can then occur in subsequent communication.
  • air-interface resources e.g., times, frequencies
  • the event which triggers a UE to perform a request to access a wireless communication system may for example be a need for an application, such as a software module in the UE, to transmit uplink user data, and/or receive downlink user data.
  • the triggering event may be a need to exchange signaling messages with a network node.
  • the triggering event may be a combination of both.
  • FIGURE 1 illustrates a simplified wireless network 100.
  • a UE 102 communicates with an access node 104, which in turn is connected to a network node 106.
  • the access node 104 corresponds typically to an Evolved NodeB (eNB) and the network node 106 corresponds typically to either a Mobility Management Entity (MME) and/or a Serving Gateway (SGW).
  • eNB Evolved NodeB
  • MME Mobility Management Entity
  • SGW Serving Gateway
  • a request for communication when the UE is in idle mode, also known as RRC IDLE state, is performed by initiating a random access procedure followed by a Radio Resource Control (RRC) Connection Establishment procedure.
  • RRC Radio Resource Control
  • FIGURE 2 illustrates a random access and RRC connection establishment procedure according to 3 GPP LTE.
  • the sequence starts with a transmission of a Random Access Preamble 201, also known as“msgl”, on specifically allocated channels or resources.
  • a Random Access Preamble 201 also known as“msgl”
  • this random access preamble is followed by a random access response 202, also known as“msg2”, that includes an allocation of resources for continued signaling, in this case the RRC Connection Request 203, also known as“msg3” which is the first message in the RRC Connection Establishment procedure.
  • a network may wish to reduce overload by denying access to a cell.
  • the network may also need to prioritize between specific users and/or services during overload situations. For example, to give priority to emergency calls compared to ordinary calls.
  • the network may employ what is in 3GPP referred to as access control.
  • Access Class Barring is an example of one such control.
  • ACB is about preventing or making it less likely that a UE will attempt to send an access request (e.g., to initiate the sequence above by sending a preamble 201).
  • the network may, for example, divide UEs or different reasons for why a UE want access into different classes or categories. Dependent on this, the network can differentiate and make it less likely that certain UE’s and/or certain events trigger access requests.
  • a given UE may belong to a certain access class and the network may communicate, via broadcasted system information, that certain classes at certain instances are barred and, thus, not allowed to make access or, if not barred altogether, allowed to make access with a lower probability.
  • broadcasted system information if it belongs to a barred access class, it may result in that a UE will not send an access request.
  • SSAC Service Specific Access Control
  • the mechanism allows a network to prohibit Multi-Media Telephony (MMTel) - voice and MMTel-video accesses from a UE.
  • the network broadcasts barring parameters (parameters similar to ACB) and a barring algorithm that is similar to ACB (barring factor and random timer).
  • An actual decision if access is allowed is done in the IP Multi-Media Subsystem (IMS) layer ofa UE.
  • IMS IP Multi-Media Subsystem
  • CSFB mechanism allows a network to prohibit CSFB users.
  • a barring algorithm used in this case is similar to ACB.
  • EAB Extended Access Barring
  • ACDC allows barring of traffic from/to certain application.
  • applications are categorized based on global application identification (ID)
  • the network broadcasts barring parameters (barring factor and timer) for each category.)
  • SSAC additionally can be applied also for connected mode UEs, i.e. UEs in RRC CONNECTED state in LTE.
  • LTE Long Term Evolution
  • system information describe how access should be performed to initiate communication between the UE 102 and the access node 104.
  • Part of this system information may be information related to access barring.
  • This barring information is usually broadcasted in the access network 100 and there can be different barring information in different cells or areas.
  • one access node 104 will transmit its own barring information.
  • the barring information may be arranged in a way such that it includes a set of access categories (i.e., l ..m) and, for each category, information elements containing a barring factor and a barring time, for example as specified in 3 GPP TS 36.331 n.14.1.0, 2016-12.
  • a set of access categories i.e., l ..m
  • information elements containing a barring factor and a barring time for example as specified in 3 GPP TS 36.331 n.14.1.0, 2016-12.
  • FIGURE 3 illustrates an example of ACDC access barring information for UTE. This barring information per access category will be used by the UE attempting access and it is a way for the access node to limit and prioritize certain accesses over other.
  • FIGURE 4 illustrates example planes in a 3GPP system.
  • a communication system such as a 3GPP system, is normally functionally divided vertically into User Plane 401, Control Plane 402 and Management Plane 403. This division allows independent scalability, evolution, and flexible deployments.
  • the user plane 401 which carries the user data traffic, contains functions and protocols related to user data transfer such as segmentation, reassembly, retransmission, multiplexing, ciphering, and so forth.
  • the control plane 402 which carries signaling traffic, the protocols and functions that are needed to setup, release, control and configure the user plane are provided.
  • the control plane 402 also contains functions and protocols related to for example UE mobility, UE authentication, control of user sessions and bearers (also known as service data flows or QoS flows).
  • Management plane 403 which carries administrative traffic, operations and maintenance (O&M) and provisioning functions may be provided, for example.
  • O&M operations and maintenance
  • FIGURE 5 illustrates another division of the 3 GPP system into domains and strata. There are a number of domains. Most important are the User Equipment (UE) 102, the Access Network (AN) 502 and the Core Network (CN) 503. It may be understood that typically the UE 102 , AN 502 and CN 503 all contain User Plane 401, Control Plane 402 and Management Plane 403 functions.
  • UE 102 is a device allowing a user access to network services. It is typically a wireless terminal, such as a smartphone, equipped with a User Services Identity Module (USIM). The latter contains the credentials in order to unambiguously and securely identify itself.
  • the functions of the USIM may be embedded in a stand-alone smart card, but could also be realized, e.g., as software in a software module.
  • USIM User Services Identity Module
  • the Access Network (AN) 502 (also known as the Radio Access Network, RAN) contains access nodes, or base stations, also known as eNBs, gNBs, which manage the radio resources of the access network and provides the UE 102 with a mechanism to access the core network 503.
  • the Access Network 502 is dependent of the radio access technology used in the wireless interface between the UE 102 and Access Network 502. Thus, we have different flavors of access network 502 for different radio access technologies, such as E-UTRAN supporting LTE or E-UTRA radio access technology and NG-RAN supporting New Radio (or 5G) type of radio access technology.
  • the Core Network (CN) 503 consists of network nodes which provide support for the network features and telecommunication services, such as the management of user location information, control of network features and services, the switching and transmission of signaling and user data.
  • the core network 503 also provides the interface towards the External Network 507.
  • EPS Evolved Packet System
  • EPC Evolved Packet Core
  • 5GS 5G Core
  • the core network 503 is access-agnostic and the interface between the access network 502 and core network 503 enables integration of different 3GPP and non-3GPP access types.
  • an Access Network 502 also known as E- UTRAN
  • an access network also known as NG-RAN
  • New Radio type of radio access technology can both be connected to a 5G type of core network 503 (also known as 5GC).
  • the External Network 507 represents here a network outside of the 3GPP domain, such as the public Internet.
  • 3GPP system is also horizontally divided into the access Stratum (AS) 504 and Non-Access Stratum (NAS) 505 reflecting a protocol layering hierarchy.
  • AS 504 includes functions that are related to the wireless portion of the system such as transport of data over the wireless connection and managing radio resources.
  • the AS 504 typically contains functions in the access network 502 and the dialogue (using corresponding protocols) between the UE 102 and the access network 502.
  • NAS 505 which can be seen as higher in the protocol layering hierarchy than AS 504, we find the functions which are not directly dependent on the radio access technology and typically the functions in the core network and the dialogue (using corresponding protocols) between the UE 102 and the core network 503.
  • Application 506 is illustrated above NAS 505.
  • the Application 506 may contain parts in the UE 102, the core network 503 and the External network 507.
  • FIGURE 6 illustrates protocol layers in the user plane and control plane of a 3GPP system.
  • control plane 402 and User Plane 401 of the Access Stratum 504 and Non-Access Stratum 505 are further divided into protocol layers.
  • AS Access Stratum
  • RRC Radio Resource Control
  • RRC 601 for different radio access technologies, e.g. one type of RRC layer 601 for each of UTRA, E-UTRA and New Radio type of radio access technologies.
  • the Access Stratum 504 there are also a number of protocol layers in the user plane 401, such as the Physical (PHY) layer 611, Medium Access Control (MAC) layer 612, Radio Link Control (RLC) layer 613 and Packet Data Convergence Control (PDCP) layer 614.
  • PHY Physical
  • MAC Medium Access Control
  • RLC Radio Link Control
  • PDCP Packet Data Convergence Control
  • SDAP Service Data Adaptation Protocol
  • All protocol layers, both in the User Plane 401 and Control Plane 402 of the Access Stratum 504 are terminated in the Access Network 502 in the network side, such as the eNB or the gNB.
  • Non-Access Stratum NAS 505
  • EPS Evolved Packet System
  • 4G or LTE 4G or LTE
  • EMM EPS Mobility Management
  • ESM EPS Session Management
  • 5G 5G system, as illustrated in Error! Reference source not found.
  • 5GMM 5G Mobility Management
  • 5GSM 5G Session Management
  • Non-Access Stratum NAS 505
  • IP Internet Protocol
  • the Application 506 resides above the NAS 505, and interacts with the user plane 401 and in some cases also the control plane 402.
  • Network slicing is a form of virtual network architecture.
  • a network slice is defined within a PLMN and shall include control plane and user plane functions in the core network as well as in the radio access network.
  • a Network Slice provides a set of supported features and network functions optimizations.
  • a Network Slice is from the UE point of view identified with S-NSSAI (Single Network Slice Selection Assistance Information). UE states and state transitions.
  • S-NSSAI Single Network Slice Selection Assistance Information
  • FIGURE 7 illustrates RRC states for NR. Specifically, in the state machine of the RRC layer 601 for NR radio access technology, according to 3GPP TS 38.804 vl4.0.0 (2017-03), three states are specified as illustrated: RRC IDLE 701, RRC INACTIVE 702 and RRC CONNECTED 703.
  • the RRC states reflect the UE's activity level where RRC IDLE 701 is typically used when the UE has no ongoing data traffic (thus no activity) and RRC_CONNECTED 703 when the UE needs to send and/or receive data.
  • RRC INACTIVE 702 may be used as an alternative state instead of RRC IDLE 701 when the UE’s activity pattern would add significant signaling overhead using RRC IDLE state.
  • RRC connection establishment The procedure to enter RRC CONNECTED 703 from RRC IDLE 701 is known as the“RRC connection establishment” procedure. Before the RRC connection establishment, this access attempt will be typically subject to Access control, including an access barring check.
  • a UE in RRC CONNECTED 703 will typically after a while, typically by order of a network node (such as the gNB), transit to RRC_INACTIVE 702, due to inactivity, using what is known as the “RRC Inactivation” procedure.
  • a UE in RRC_INACTIVE 702 needs to again enter RRC CONNECTED 703 in order to transmit or receive data.
  • the UE may remain in Inactive for as long as it remains in a certain network area, or it may be paged by the network to transition from RRC INACTIVE 702 to RRC IDLE 701 or enter RRC IDLE due to other reasons, e.g. procedural errors or failures.
  • the procedure for entering RRC CONNECTED 703 from RRC INACTIVE 702 is sometimes referred to as an“RRC Resume” (or“Activation”) procedure.
  • the RRC Resume procedure is currently being standardized and details are yet to be set, but it is expected to require much less signaling than the RRC connection establishment procedure, since e.g. processing resources, transport resources and security association in the network are preserved in RRC_INACTIVE 702 and thus there is typically no need to establish those in the RRC Resume procedure. Therefore, the latency before user data can be exchanged between the UE and the network is typically much shorter for a UE in RRC INACTIVE 702 than for a UE in RRC IDLE 701. On the other hand, a UE in RRC INACTIVE 702 consumes a little more power as well as resources (e.g. memory) than a UE in RRC IDLE 701.
  • 5G An ongoing evolution of the access control mechanisms, in particular for 5th generation cellular standards according to 3GPP, is to gather the existing access control mechanisms into one single mechanism that can be configurable and adaptable to various network operator preferences. It has thus been agreed that 5G will include a single access control framework, what is known as Unified access control.
  • Unified access control will apply to UEs accessing 5G Core via NR (New Radio) or E-UTRA/LTE. Moreover, Unified access control is applied in all UE states, whereas for LTE, with one exception (SSAC), the access control mechanisms only apply for idle mode UEs.
  • NR New Radio
  • E-UTRA/LTE E-UTRA/LTE
  • Unified access control is currently being specified in 3GPP TS 22.261 (5G service requirements), 3GPP TS 24.501 (5G NAS protocols), 3GPP TS 38.331 (NR RRC Protocol) and 3 GPP TS 36.331 (LTE RRC Protocol).
  • the access node e.g. gNB or eNB
  • the access node indicates barring condition for each cell using access barring parameters to UEs by system information broadcast in the RRC layer within the access stratum (AS).
  • AS access stratum
  • an access attempt is a request to setup a new session, such as a new PDU session or an MMTEL Voice call. For each detected access attempt one or more Access Identities and only one Access Category are selected.
  • Access Identities are configured at the UE and are typically used for“special” UEs, such as UEs for mission-critical services or for operator use.
  • FIGURE 8 illustrates the access identities specified in TS 22.261.
  • Access Categories are defined by the combination of conditions related to UE and the type of access attempt.
  • FIGURE 9 illustrates the access categories specified in TS 22.261.
  • the rules for how to select the operator-defined access categories is configured by the network. Each of these configured rules will be used as one criteria for selecting a particular operator-defined access category.
  • An example of a criteria is that an access attempt associated with a PDU session for a certain value of DNN (Data Network Node) is mapped to a certain operator-defined access category.
  • DNN Data Network Node
  • Each rule is associated with a precedence, used to prioritize in which order the UE evaluates the rules.
  • the UE selects either an standardized access category or an operator- defined access category, in a deterministic way based on specified and configurable rules.
  • access attempts for each access category, is now being done by 3GPP working groups, mainly CT1 and RAN2). It is understood that access attempts may be detected and identified in several layers in the UE, including 5GSM, 5GMM, SMSoIP, MMTEL (Multimedia Telephony) and RRC. But“double barring” should be avoided and therefore a given access attempt should only detected at one place in the protocol stack, and only once.
  • the layer which detects the access attempt performs the mapping to access category, triggers access barring check and performs enforcement of blocking the attempt if not authorized.
  • FIGURE 10 illustrates the overall procedure for unified access control.
  • a network node optionally provides rules for the operator-specific access categories.
  • this information is illustrated as originating from the network node 106, such as the AMF, but may very well also originate from other network nodes and be transmitted to the UE via network node 106 or possibly via other node (e.g. an operator's policy functionality configuring the UE 102 via WLAN access network).
  • the network includes a higher-level controller or policy functionality it may originate from another node hosting such controller or policy functionality.
  • the higher layer rules may be signaled to the UE via Non- Access-Stratum (NAS) signaling, or it may be signaled using other protocols.
  • NAS Non- Access-Stratum
  • the UE 102 may include an entity that can be configured with and host access category rules signaled using an OMA-DM device management protocol. It is currently assumed in 3GPP CT1 that operator-defined access categories can be signaled to the UE using NAS signaling.
  • the UE is configured with a list of tuples, where each tuple consists of the following parameters:
  • the access category criteria type can be set to one of the following:
  • step 1001 may also include signaling from the access node, in particular when it comes to access category selection for accesses that are triggered by, e.g., signaling with the access node.
  • the UE 102 When an event occurs triggering a need for the UE 102 to request an access to the network, such as a need to transmit uplink data when the UE 102 is in idle mode, or to setup an MMTel Voice call when the UE 102 is in RRC CON ECTED state, the UE 102 first detects whether this event is an access attempt in step 1002. An access attempt would always undergo access barring check before it is allowed. Some events are not classified and detected as access attempts. For example, when uplink data is to be sent for an existing PDU session in RRC CONNECTED state.
  • the UE 102 determines the access category in step 1003, based on the standardized rules as well as any configured rules obtained in step 1001.
  • CT1 and RAN2 are currently specifying how the determination of an access category is performed.
  • FIGURE 11 illustrates a mapping table for the determination of access category as included in TS 24.501.
  • the UE 102 checks the rules in in FIGURE 11 and use the access category for which there is a match for barring check. If the access attempt matches more than one rule, the access category of the lowest rule number will be selected.
  • the rule#3 can be seen as a set of rules, because when determining access category for a given access attempt for any of the operator-defined access categories the configured tuples for operator-defined access categories are used. If the access attempt fulfills all the criteria in the list of criteria in a tuple, then the access attempt is categorized in the operator-defined access identity of the tuple. If there are several such tuples, the UE will use the tuple with the highest precedence value.
  • the UE 102 After determining the access category for this particular access attempt, the UE 102 then reads access barring information typically part of the broadcasted system information in step 1004. Typically, the UE 102 is required to maintain the latest version of the broadcasted system information which implies that the UE 102 in many cases does not actually have to re-read the system information and instead can use cached system information. The UE 102 then performs an access barring check for the access attempt in step 1005, using the determined access category and the access barring information as input.
  • the UE 102 will continue and perform the access in step 1006, resulting typically in an uplink signalling message such as an RRC connection request or a NAS message such as a PDU Session Request, depending on the UE state and the type of access attempt.
  • an uplink signalling message such as an RRC connection request or a NAS message such as a PDU Session Request, depending on the UE state and the type of access attempt.
  • the UE 102 will not perform an access and instead wait for a period, such as by starting a timer with a value indicated in the access barring information.
  • a method by a wireless device for performing an access barring check.
  • the method includes identifying an access attempt and determining at least one matching rule for a first access category.
  • a second access category is determined using criteria comprising at least the at least one matching rule for the first access category.
  • the access barring check is performed for said identified access attempt using said determined second access category.
  • a wireless device for performing an access barring check.
  • the wireless device includes memory operable to store instructions and processing circuitry operable to execute the instructions to cause the wireless device to: identify an access attempt; determine at least one matching rule for a first access category; determine a second access category using criteria comprising at least the at least one matching rule for the first access category; and perform the access barring check for said identified access attempt using said determined second access category.
  • a method by a wireless device for performing an access barring check.
  • the method includes identifying an access attempt.
  • a first access category is determined, and a second access category is determined using said determined first access category.
  • An access barring check is performed for said identified access attempt using said determined second access category.
  • a wireless device for performing an access barring check.
  • the wireless device includes memory operable to store instructions and processing circuitry operable to execute the instructions to cause the wireless device to: identifying an access attempt; determining a first access category; determining a second access category using said determined first access category; and performing an access barring check for said identified access attempt using said determined second access category.
  • one technical advantage may be that certain embodiments provide a possibility for finer granularity of access category determination when using operator-defined access categories. This means that it would, for example, be possible within one slice to allow a certain service (e.g. MMTel Voice) while blocking other traffic, such as other MO data, using access barring.
  • a certain service e.g. MMTel Voice
  • Another technical advantage may be that certain embodiments allow NAS signaling and user data packets sent towards a slice to be treated differently in unified access control.
  • an operator-specific access category X may be used for access attempts triggered by NAS signaling sent to S-NSSAI A
  • operator-specific access category Y may be used for access attempts triggered by uplink user data packet sent via a PDU session established with S-NSSAI A.
  • FIGURE 1 illustrates a simplified wireless network
  • FIGURE 2 illustrates a random access and RRC connection establishment procedure according to 3GPP LTE
  • FIGURE 3 illustrates an example of ACDC access barring information for
  • FIGURE 4 illustrates example planes in a 3GPP system
  • FIGURE 5 illustrates another division of the 3GPP system into domains and strata
  • FIGURE 6 illustrates protocol layers in the user plane and control plane of a 3GPP system
  • FIGURE 7 illustrates RRC states for N
  • FIGURE 8 illustrates the access identities specified in TS 22.26
  • FIGURE 9 illustrates the access categories specified in TS 22.261
  • FIGURE 10 illustrates the overall procedure for unified access control
  • FIGURE 11 illustrates a mapping table for the determination of access category as included in TS 24.501;
  • FIGURE 12 illustrates an example method performed by a user equipment (UE), according to certain embodiments
  • FIGURE 13 illustrates another example method by a UE, according to certain embodiments.
  • FIGURE 14 illustrates an example network, according to certain embodiments.
  • FIGURE 15 illustrate an example network node, according to certain embodiments.
  • FIGURE 16 illustrates an example wireless device, according to certain embodiments.
  • FIGURE 17 illustrates an example user equipment, according to certain embodiments.
  • FIGURE 18 illustrates a virtualization environment in which functions implemented by some embodiments may be virtualized, according to certain embodiments
  • FIGURE 19 illustrates a telecommunication network connected via an intermediate network to a host computer, according to certain embodiments
  • FIGURE 20 illustrates a generalized block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection, according to certain embodiments
  • FIGURE 21 illustrates a method implemented in a communication system, according to one embodiment
  • FIGURE 22 illustrates another method implemented in a communication system, according to one embodiment
  • FIGURE 23 illustrates another method implemented in a communication system, according to one embodiment
  • FIGURE 24 illustrates another method implemented in a communication system, according to one embodiment.
  • FIGURE 25 illustrates an example method by a wireless device for performing an access barring check, according to certain embodiments, according to certain embodiments
  • FIGURE 26 illustrates an example virtual apparatus for performing an access barring check, according to certain embodiments
  • FIGURE 27 illustrates another example method by a wireless device for performing an access barring check, according to certain embodiments, according to certain embodiments.
  • FIGURE 28 illustrates another example virtual apparatus for performing an access barring check, according to certain embodiments.
  • access category criteria may be added such that it is possible to combine the S-NSSAI with other rules in the mapping table illustrated in FIGURE 11, which is described above.
  • the UE may use as one additional criteria for those tuples, which of the rules in FIGURE 11, e.g. rules 1,2 and 4-9 that are fulfilled.
  • FIGURE 12 illustrates an example method performed by a UE 102, according to certain embodiments.
  • the method may begin at step 1201 when the UE 102 detects an access attempt, that is, an event which classifies into an access attempt according to the specification.
  • the UE 102 evaluates all rules to determine an access category in step 1202.
  • the UE 102 typically uses the mapping as illustrated in FIGURE 11.
  • the UE will use the rules (tuples) previously configured (as described in FIGURE 10, step 1001) for operator-defined access categories.
  • These tuples may each contain a number of criteria, such as S-NSSAI, DNN name and/or a rule number of the mapping table in FIGURE 11 for standardized access categories.
  • the latter criteria can alternatively be represented as e.g. "MO signaling", "MO data", "MMTEL voice”, “MMTEL video”.
  • the UE 102 will use the tuple with the highest precedence value and then select the operator-defined access category as part of that tuple.
  • This selected operator-defined access category is the result of rule#3. If neither rule#l nor rule#2 in the mapping table in FIGURE 11 are fulfilled, the UE 102 will then use this particular operator-defined access category as the determined access category for the access attempt.
  • step 1203 the UE 102 will use the determined access category for the access attempt to perform an access barring check.
  • FIGURE 13 illustrates another example method by a UE, according to certain embodiments.
  • the method may begin at step 1301 when the UE 102 detects an access attempt, that is, an event which classifies into an access attempt according to the specification.
  • the UE 102 For the detected access attempt, in step 1302, the UE 102 first evaluates the rules to determine a matching standardized access category. For example, it may evaluate rules 1-2 first in FIGURE 11 and then if there is no match for these rules, UE 102 may check which of the rules 4-9 that are applicable. The result of this step is the matching rule, represented by in one example the rule number (e.g. a number of 0, 1, 4-9) or, in another example, the standardized access category number (e.g. 0-7).
  • the rule number e.g. a number of 0, 1, 4-9
  • the standardized access category number e.g. 0-7
  • the UE 102 checks whether criteria for evaluating operator- defined access categories are met. For example, the UE 102 does not evaluate these in case of that in the previous step, an access category is selected that takes precedence over any operator-defined access categories, that is those categories that corresponds to the first two rules (response to paging and emergency). Another example when the criteria is not met is when the UE does not have any operator-defined access categories configured for the registered PLMN.
  • the UE 102 will use the previously determined standardized access category to perform an access barring check, in step 1304.
  • the UE in step 1305 evaluates the rules (or tuples) for operator-defined access categories, and using as one input, the determination performed previously (e.g. as described in step 1001 in FIGURE 10).
  • the rules for determining the operator-defined access category may each contain a number of criteria, such as S-NSSAI, DN name plus a standardized access category (or in another example the rule number used for determination of standardized access categories).
  • the rules are ordered relative to each other based on a precedence value part of each rule.
  • step 1306 the UE 102 will use the corresponding operator-defined access category to perform an access barring check in step 1307. Otherwise the UE 102 will use the previously determined standardized access category to perform an access barring check in step 1304.
  • FIGURE 14 illustrates a wireless network, in accordance with some embodiments.
  • a wireless network such as the example wireless network illustrated in FIGURE 14.
  • the wireless network of FIGURE 14 only depicts network 1406, network nodes 1460 and l460b, and WDs 1410, l4l0b, and l4l0c.
  • a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device.
  • the wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.
  • the wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system.
  • the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures.
  • wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Uong Term Evolution (UTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • UTE Universal Term Evolution
  • WLAN wireless local area network
  • WiMax Worldwide Interoperability for Microwave Access
  • Bluetooth Z-Wave and/or ZigBee standards.
  • Network 1406 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.
  • PSTNs public switched telephone networks
  • WANs wide-area networks
  • LANs local area networks
  • WLANs wireless local area networks
  • wired networks wireless networks, metropolitan area networks, and other networks to enable communication between devices.
  • Network node 1460 and WD 1410 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network.
  • the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • FIGURE 15 illustrates an example network node, according to certain embodiments.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network.
  • network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NRNodeBs (gNBs)).
  • APs access points
  • BSs base stations
  • eNBs evolved Node Bs
  • gNBs NRNodeBs
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • RRUs remote radio units
  • RRHs Remote Radio Heads
  • Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
  • DAS distributed antenna system
  • network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • transmission points transmission nodes
  • MCEs multi-cell/multicast coordination entities
  • core network nodes e.g., MSCs, MMEs
  • O&M nodes e.g., OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.
  • network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.
  • network node 1460 includes processing circuitry 1470, device readable medium 1480, interface 1490, auxiliary equipment 1484, power source 1486, power circuitry 1487, and antenna 1462.
  • network node 1460 illustrated in the example wireless network of Figure 14 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein.
  • network node 1460 may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 1480 may comprise multiple separate hard drives as well as multiple RAM modules).
  • network node 1460 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • network node 1460 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeB’s.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • network node 1460 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • some components may be duplicated (e.g., separate device readable medium 1480 for the different RATs) and some components may be reused (e.g., the same antenna 1462 may be shared by the RATs).
  • Network node 1460 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1460, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1460.
  • Processing circuitry 1470 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 1470 may include processing information obtained by processing circuitry 1470 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing information obtained by processing circuitry 1470 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • Processing circuitry 1470 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 1460 components, such as device readable medium 1480, network node 1460 functionality.
  • processing circuitry 1470 may execute instructions stored in device readable medium 1480 or in memory within processing circuitry 1470. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein.
  • processing circuitry 1470 may include a system on a chip (SOC).
  • SOC system on a chip
  • processing circuitry 1470 may include one or more of radio frequency (RF) transceiver circuitry 1472 and baseband processing circuitry 1474.
  • radio frequency (RF) transceiver circuitry 1472 and baseband processing circuitry 1474 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units.
  • part or all of RF transceiver circuitry 1472 and baseband processing circuitry 1474 may be on the same chip or set of chips, boards, or units.
  • processing circuitry 1470 executing instructions stored on device readable medium 1480 or memory within processing circuitry 1470.
  • some or all of the functionality may be provided by processing circuitry 1470 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner.
  • processing circuitry 1470 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 1470 alone or to other components of network node 1460, but are enjoyed by network node 1460 as a whole, and/or by end users and the wireless network generally.
  • Device readable medium 1480 may comprise any form of volatile or non volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 1470.
  • Device readable medium 1480 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc.
  • Device readable medium 1480 may be used to store any calculations made by processing circuitry 1470 and/or any data received via interface 1490. In some embodiments, processing circuitry 1470 and device readable medium 1480 may be considered to be integrated.
  • Interface 1490 is used in the wired or wireless communication of signalling and/or data between network node 1460, network 1406, and/or WDs 1410. As illustrated, interface 1490 comprises port(s)/terminal(s) 1494 to send and receive data, for example to and from network 1406 over a wired connection. Interface 1490 also includes radio front end circuitry 1492 that may be coupled to, or in certain embodiments a part of, antenna 1462. Radio front end circuitry 1492 comprises filters 1498 and amplifiers 1496. Radio front end circuitry 1492 may be connected to antenna 1462 and processing circuitry 1470. Radio front end circuitry may be configured to condition signals communicated between antenna 1462 and processing circuitry 1470.
  • Radio front end circuitry 1492 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 1492 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1498 and/or amplifiers 1496. The radio signal may then be transmitted via antenna 1462. Similarly, when receiving data, antenna 1462 may collect radio signals which are then converted into digital data by radio front end circuitry 1492. The digital data may be passed to processing circuitry 1470. In other embodiments, the interface may comprise different components and/or different combinations of components.
  • network node 1460 may not include separate radio front end circuitry 1492, instead, processing circuitry 1470 may comprise radio front end circuitry and may be connected to antenna 1462 without separate radio front end circuitry 1492.
  • processing circuitry 1470 may comprise radio front end circuitry and may be connected to antenna 1462 without separate radio front end circuitry 1492.
  • all or some of RF transceiver circuitry 1472 may be considered a part of interface 1490.
  • interface 1490 may include one or more ports or terminals 1494, radio front end circuitry 1492, and RF transceiver circuitry 1472, as part of a radio unit (not shown), and interface 1490 may communicate with baseband processing circuitry 1474, which is part of a digital unit (not shown).
  • Antenna 1462 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 1462 may be coupled to radio front end circuitry 1490 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 1462 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna 1462 may be separate from network node 1460 and may be connectable to network node 1460 through an interface or port.
  • Antenna 1462, interface 1490, and/or processing circuitry 1470 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 1462, interface 1490, and/or processing circuitry 1470 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.
  • Power circuitry 1487 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 1460 with power for performing the functionality described herein. Power circuitry 1487 may receive power from power source 1486. Power source 1486 and/or power circuitry 1487 may be configured to provide power to the various components of network node 1460 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 1486 may either be included in, or external to, power circuitry 1487 and/or network node 1460.
  • network node 1460 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 1487.
  • power source 1486 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 1487. The battery may provide backup power should the external power source fail.
  • Other types of power sources such as photovoltaic devices, may also be used.
  • network node 1460 may include additional components beyond those shown in FIGURE 15 that may be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein.
  • network node 1460 may include user interface equipment to allow input of information into network node 1460 and to allow output of information from network node 1460. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 1460.
  • FIGURE 16 illustrates an example wireless device (WD), according to certain embodiments.
  • WD refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices.
  • UE user equipment
  • Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air.
  • a WD may be configured to transmit and/or receive information without direct human interaction.
  • a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network.
  • Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop- mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE) a vehicle -mounted wireless terminal device, etc.
  • VoIP voice over IP
  • a WD may support device- to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device.
  • D2D device- to-device
  • V2V vehicle-to-vehicle
  • V2I vehicle-to-infrastructure
  • V2X vehicle-to-everything
  • a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node.
  • the WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device.
  • M2M machine-to-machine
  • the WD may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard.
  • NB-IoT narrow band internet of things
  • machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.).
  • a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • a WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.
  • wireless device 1410 includes antenna 1411, interface 1414, processing circuitry 1420, device readable medium 1430, user interface equipment 1432, auxiliary equipment 1434, power source 1436 and power circuitry 1437.
  • WD 1410 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 1410, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD 1410.
  • Antenna 1411 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 1414. In certain alternative embodiments, antenna 1411 may be separate from WD 1410 and be connectable to WD 1410 through an interface or port. Antenna 1411, interface 1414, and/or processing circuitry 1420 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna 1411 may be considered an interface. As illustrated, interface 1414 comprises radio front end circuitry 1412 and antenna 1411.
  • Radio front end circuitry 1412 comprise one or more filters 1418 and amplifiers 1416.
  • Radio front end circuitry 1414 is connected to antenna 1411 and processing circuitry 1420, and is configured to condition signals communicated between antenna 1411 and processing circuitry 1420.
  • Radio front end circuitry 1412 may be coupled to or a part of antenna 1411.
  • WD 1410 may not include separate radio front end circuitry 1412; rather, processing circuitry 1420 may comprise radio front end circuitry and may be connected to antenna 1411.
  • some or all of RF transceiver circuitry 1422 may be considered a part of interface 1414.
  • Radio front end circuitry 1412 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection.
  • Radio front end circuitry 1412 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1418 and/or amplifiers 1416. The radio signal may then be transmitted via antenna 1411. Similarly, when receiving data, antenna 1411 may collect radio signals which are then converted into digital data by radio front end circuitry 1412. The digital data may be passed to processing circuitry 1420. In other embodiments, the interface may comprise different components and/or different combinations of components.
  • Processing circuitry 1420 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD 1410 components, such as device readable medium 1430, WD 1410 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein.
  • processing circuitry 1420 may execute instructions stored in device readable medium 1430 or in memory within processing circuitry 1420 to provide the functionality disclosed herein.
  • processing circuitry 1420 includes one or more of RF transceiver circuitry 1422, baseband processing circuitry 1424, and application processing circuitry 1426.
  • the processing circuitry may comprise different components and/or different combinations of components.
  • processing circuitry 1420 of WD 1410 may comprise a SOC.
  • RF transceiver circuitry 1422, baseband processing circuitry 1424, and application processing circuitry 1426 may be on separate chips or sets of chips.
  • part or all of baseband processing circuitry 1424 and application processing circuitry 1426 may be combined into one chip or set of chips, and RF transceiver circuitry 1422 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry 1422 and baseband processing circuitry 1424 may be on the same chip or set of chips, and application processing circuitry 1426 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry 1422, baseband processing circuitry 1424, and application processing circuitry 1426 may be combined in the same chip or set of chips.
  • RF transceiver circuitry 1422 may be apart of interface 1414.
  • RF transceiver circuitry 1422 may condition RF signals for processing circuitry 1420.
  • processing circuitry 1420 executing instructions stored on device readable medium 1430, which in certain embodiments may be a computer-readable storage medium.
  • some or all of the functionality may be provided by processing circuitry 1420 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner.
  • processing circuitry 1420 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 1420 alone or to other components ofWD 1410, but are enjoyed by WD 1410 as a whole, and/or by end users and the wireless network generally.
  • Processing circuitry 1420 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 1420, may include processing information obtained by processing circuitry 1420 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 1410, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • Device readable medium 1430 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 1420.
  • Device readable medium 1430 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 1420.
  • processing circuitry 1420 and device readable medium 1430 may be considered to be integrated.
  • User interface equipment 1432 may provide components that allow for a human user to interact with WD 1410. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 1432 may be operable to produce output to the user and to allow the user to provide input to WD 1410. The type of interaction may vary depending on the type of user interface equipment 1432 installed in WD 1410. For example, ifWD 1410 is a smart phone, the interaction may be via a touch screen; if WD 1410 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected).
  • usage e.g., the number of gallons used
  • a speaker that provides an audible alert
  • User interface equipment 1432 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 1432 is configured to allow input of information into WD 1410, and is connected to processing circuitry 1420 to allow processing circuitry 1420 to process the input information. User interface equipment 1432 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 1432 is also configured to allow output of information from WD 1410, and to allow processing circuitry 1420 to output information from WD 1410. User interface equipment 1432 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry.
  • WD 1410 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.
  • Auxiliary equipment 1434 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 1434 may vary depending on the embodiment and/or scenario.
  • Power source 1436 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used.
  • WD 1410 may further comprise power circuitry 1437 for delivering power from power source 1436 to the various parts of WD 1410 which need power from power source 1436 to carry out any functionality described or indicated herein.
  • Power circuitry 1437 may in certain embodiments comprise power management circuitry.
  • Power circuitry 1437 may additionally or alternatively be operable to receive power from an external power source; in which case WD 1410 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable.
  • Power circuitry 1437 may also in certain embodiments be operable to deliver power from an external power source to power source 1436. This may be, for example, for the charging of power source 1436. Power circuitry 1437 may perform any formatting, converting, or other modification to the power from power source 1436 to make the power suitable for the respective components of WD 1410 to which power is supplied.
  • FIGURE 17 illustrates one embodiment of a UE, in accordance with various aspects described herein.
  • a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).
  • a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
  • UE 17200 may be any UE identified by the 3 rd Generation Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • UE 1700 as illustrated in FIGURE 17, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3 rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards.
  • 3GPP 3 rd Generation Partnership Project
  • UE 1700 includes processing circuitry 1701 that is operatively coupled to input/output interface 1705, radio frequency (RF) interface 1709, network connection interface 1711, memory 1715 including random access memory (RAM) 1717, read-only memory (ROM) 1719, and storage medium 1721 or the like, communication subsystem 1731, power source 1733, and/or any other component, or any combination thereof.
  • Storage medium 1721 includes operating system 1723, application program 1725, and data 1727. In other embodiments, storage medium 1721 may include other similar types of information.
  • Certain UEs may utilize all of the components shown in Figure 15, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • processing circuitry 1701 may be configured to process computer instructions and data.
  • Processing circuitry 1701 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine -readable computer programs in the memory, such as one or more hardware -implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above.
  • the processing circuitry 1701 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.
  • input/output interface 1705 may be configured to provide a communication interface to an input device, output device, or input and output device.
  • UE 1700 may be configured to use an output device via input/output interface 1705.
  • An output device may use the same type of interface port as an input device.
  • a USB port may be used to provide input to and output from UE 1700.
  • the output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • UE 1700 may be configured to use an input device via input/output interface 1705 to allow a user to capture information into UE 1700.
  • the input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like.
  • the presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof.
  • the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.
  • RF interface 1709 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna.
  • Network connection interface 1711 may be configured to provide a communication interface to network l743a.
  • Network l743a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • LAN local-area network
  • WAN wide-area network
  • network l743a may comprise a Wi-Fi network.
  • Network connection interface 1711 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like.
  • Network connection interface 1711 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like).
  • the transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.
  • RAM l7l7 may be configured to interface via bus 1702 to processing circuitry 1701 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers.
  • ROM 1719 may be configured to provide computer instructions or data to processing circuitry 1701.
  • ROM 1719 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory.
  • Storage medium 1721 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives.
  • storage medium 1721 may be configured to include operating system 1723, application program 1725 such as a web browser application, a widget or gadget engine or another application, and data file 1727.
  • Storage medium 1721 may store, for use by UE 1700, any of a variety of various operating systems or combinations of operating systems.
  • Storage medium 1721 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof.
  • RAID redundant array of independent disks
  • HD-DVD high-density digital versatile disc
  • HDDS holographic digital data storage
  • DIMM external mini-dual in-line memory module
  • SDRAM synchronous dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • smartcard memory such as a subscriber identity module or a removable user
  • Storage medium 1721 may allow UE 1700 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium 1721, which may comprise a device readable medium.
  • processing circuitry 1701 may be configured to communicate with network l743b using communication subsystem 1731.
  • Network l743a and network l743b may be the same network or networks or different network or networks.
  • Communication subsystem 1731 may be configured to include one or more transceivers used to communicate with network l743b.
  • communication subsystem 1731 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.17, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like.
  • RAN radio access network
  • Each transceiver may include transmitter 1733 and/or receiver 1735 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 1733 and receiver 1735 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.
  • the communication functions of communication subsystem 1731 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof.
  • communication subsystem 1731 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication.
  • Network l743b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • network l743b may be a cellular network, a Wi-Fi network, and/or a near-field network.
  • Power source 1713 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 1700.
  • communication subsystem 1731 may be configured to include any of the components described herein.
  • processing circuitry 1701 may be configured to communicate with any of such components over bus 1702.
  • any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 1701 perform the corresponding functions described herein.
  • the functionality of any of such components may be partitioned between processing circuitry 1701 and communication subsystem 1731.
  • the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.
  • FIGURE 18 is a schematic block diagram illustrating a virtualization environment 1800 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).
  • a node e.g., a virtualized base station or a virtualized radio access node
  • a device e.g., a UE, a wireless device or any other type of communication device
  • some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 1800 hosted by one or more of hardware nodes 1830. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.
  • the functions may be implemented by one or more applications 1820 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Applications 1820 are run in virtualization environment 1800 which provides hardware 1830 comprising processing circuitry 1860 and memory 1890.
  • Memory 1890 contains instructions 1895 executable by processing circuitry 1860 whereby application 1820 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.
  • Virtualization environment 1800 comprises general-purpose or special- purpose network hardware devices 1830 comprising a set of one or more processors or processing circuitry 1860, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors.
  • processors or processing circuitry 1860 may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors.
  • Each hardware device may comprise memory 1890-1 which may be non-persistent memory for temporarily storing instructions 1895 or software executed by processing circuitry 1860.
  • Each hardware device may comprise one or more network interface controllers (NICs) 1870, also known as network interface cards, which include physical network interface 1880.
  • NICs network interface controllers
  • Each hardware device may also include non-transitory, persistent, machine-readable storage media 1890-2 having stored therein software 1895 and/or instructions executable by processing circuitry 1860.
  • Software 1895 may include any type of software including software for instantiating one or more virtualization layers 1850 (also referred to as hypervisors), software to execute virtual machines 1840 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.
  • Virtual machines 1840 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1850 or hypervisor. Different embodiments of the instance of virtual appliance 1820 may be implemented on one or more of virtual machines 1840, and the implementations may be made in different ways.
  • processing circuitry 1860 executes software 1895 to instantiate the hypervisor or virtualization layer 1850, which may sometimes be referred to as a virtual machine monitor (VMM).
  • Virtualization layer 1850 may present a virtual operating platform that appears like networking hardware to virtual machine 1840.
  • hardware 1830 may be a standalone network node with generic or specific components. Hardware 1830 may comprise antenna 18225 and may implement some functions via virtualization. Alternatively, hardware 1830 may be part of a larger cluster of hardware (e .g . such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) 18100, which, among others, oversees lifecycle management of applications 1820.
  • CPE customer premise equipment
  • NFV network function virtualization
  • NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
  • virtual machine 1840 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non- virtualized machine.
  • Each of virtual machines 1840, and that part of hardware 1830 that executes that virtual machine be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 1840, forms a separate virtual network elements (VNE).
  • VNE virtual network elements
  • VNF Virtual Network Function
  • one or more radio units 18200 that each include one or more transmitters 18220 and one or more receivers 18210 may be coupled to one or more antennas 18225.
  • Radio units 18200 may communicate directly with hardware nodes 1830 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
  • control system 18230 which may alternatively be used for communication between the hardware nodes 1830 and radio units 18200.
  • FIGURE 19 illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments.
  • a communication system includes telecommunication network 1910, such as a 3GPP- type cellular network, which comprises access network 1911, such as a radio access network, and core network 1914.
  • Access network 1911 comprises a plurality of base stations l9l2a, l9l2b, l9l2c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area l9l3a, l9l3b, l9l3c.
  • Each base station l9l2a, l9l2b, l9l2c is connectable to core network 1914 over a wired or wireless connection 1915.
  • a first UE 1991 located in coverage area l9l3c is configured to wirelessly connect to, or be paged by, the corresponding base station !9l2c.
  • a second UE 1992 in coverage area !9l3a is wirelessly connectable to the corresponding base station l9l2a. While a plurality ofUEs 1991, 1992 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 1912.
  • Telecommunication network 1910 is itself connected to host computer 1930, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm.
  • Host computer 1930 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider.
  • Connections 1921 and 1922 between telecommunication network 1910 and host computer 1930 may extend directly from core network 1914 to host computer 1930 or may go via an optional intermediate network 1920.
  • Intermediate network 1920 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 1920, if any, may be a backbone network or the Internet; in particular, intermediate network 1920 may comprise two or more sub-networks (not shown).
  • the communication system of FIGURE 19 as a whole enables connectivity between the connected UEs 1991, 1992 and host computer 1930.
  • the connectivity may be described as an over-the-top (OTT) connection 1950.
  • Host computer 1930 and the connected UEs 1991, 1992 are configured to communicate data and/or signaling via OTT connection 1950, using access network 1911, core network 1914, any intermediate network 1920 and possible further infrastructure (not shown) as intermediaries.
  • OTT connection 1950 may be transparent in the sense that the participating communication devices through which OTT connection 1950 passes are unaware of routing of uplink and downlink communications.
  • base station 1912 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 1930 to be forwarded (e.g., handed over) to a connected UE 1991.
  • base station 1912 need not be aware of the future routing of an outgoing uplink communication originating from the UE 1991 towards the host computer 1930.
  • FIGURE 20 illustrates a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments.
  • host computer 2010 comprises hardware 2015 including communication interface 2016 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 2000.
  • Host computer 2010 further comprises processing circuitry 2018, which may have storage and/or processing capabilities.
  • processing circuitry 2018 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Host computer 2010 further comprises software 201 1, which is stored in or accessible by host computer 2010 and executable by processing circuitry 2018.
  • Software 2011 includes host application 2012.
  • Host application 2012 may be operable to provide a service to a remote user, such as UE 2030 connecting via OTT connection 2050 terminating at UE 2030 and host computer 2010. In providing the service to the remote user, host application 2012 may provide user data which is transmitted using OTT connection 2050.
  • Communication system 2000 further includes base station 2020 provided in a telecommunication system and comprising hardware 2025 enabling it to communicate with host computer 2010 and with UE 2030.
  • Hardware 2025 may include communication interface 2026 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 2000, as well as radio interface 2027 for setting up and maintaining at least wireless connection 2070 with UE 2030 located in a coverage area (not shown in Figure 18) served by base station 2020.
  • Communication interface 2026 may be configured to facilitate connection 2060 to host computer 2010. Connection 2060 may be direct or it may pass through a core network (not shown in Figure 18) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.
  • hardware 2025 of base station 2020 further includes processing circuitry 2028, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Base station 2020 further has software 2021 stored internally or accessible via an external connection.
  • Communication system 2000 further includes UE 2030 already referred to. Its hardware 2035 may include radio interface 2037 configured to set up and maintain wireless connection 2070 with a base station serving a coverage area in which UE 2030 is currently located. Hardware 2035 of UE 2030 further includes processing circuitry 2038, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • UE 2030 further comprises software 2031, which is stored in or accessible by UE 2030 and executable by processing circuitry 2038.
  • Software 2031 includes client application 2032. Client application 2032 may be operable to provide a service to a human or non-human user via UE 2030, with the support of host computer 2010.
  • an executing host application 2012 may communicate with the executing client application 2032 via OTT connection 2050 terminating at UE 2030 and host computer 2010.
  • client application 2032 may receive request data from host application 2012 and provide user data in response to the request data.
  • OTT connection 2050 may transfer both the request data and the user data.
  • Client application 2032 may interact with the user to generate the user data that it provides.
  • host computer 2010, base station 2020 and UE 2030 illustrated in FIGURE 20 may be similar or identical to host computer 1930, one of base stations l9l2a, l9l2b, l9l2c and one of UEs 1991, 1992 of FIGURE 19, respectively.
  • the inner workings of these entities may be as shown in FIGURE 20 and independently, the surrounding network topology may be that of FIGURE 19.
  • OTT connection 2050 has been drawn abstractly to illustrate the communication between host computer 2010 and UE 2030 via base station 2020, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from UE 2030 or from the service provider operating host computer 2010, or both. While OTT connection 2050 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • Wireless connection 2070 between UE 2030 and base station 2020 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to UE 2030 using OTT connection 2050, in which wireless connection 2070 forms the last segment. More precisely, the teachings of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, and/or extended battery lifetime.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring OTT connection 2050 may be implemented in software 2011 and hardware 2015 of host computer 2010 or in software 2031 and hardware 2035 of UE 2030, or both.
  • sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 2050 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 2011, 2031 may compute or estimate the monitored quantities.
  • the reconfiguring of OTT connection 2050 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 2020, and it may be unknown or imperceptible to base station 2020. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling facilitating host computer 2010’ s measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that software 2011 and 2031 causes messages to be transmitted, in particular empty or‘dummy’ messages, using OTT connection 2050 while it monitors propagation times, errors etc.
  • FIGURE 21 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 19 and 20. For simplicity of the present disclosure, only drawing references to FIGURE 21 will be included in this section.
  • the host computer provides user data.
  • substep 2111 (which may be optional) of step 2110, the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE.
  • step 2130 the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 2140 the UE executes a client application associated with the host application executed by the host computer.
  • FIGURE 22 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 19 and 20. For simplicity of the present disclosure, only drawing references to FIGURE 22 will be included in this section.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 2230 (which may be optional), the UE receives the user data carried in the transmission.
  • FIGURE 23 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 19 and 20. For simplicity of the present disclosure, only drawing references to FIGURE 23 will be included in this section.
  • step 2310 (which may be optional) the UE receives input data provided by the host computer. Additionally or alternatively, in step 2320, the UE provides user data.
  • substep 2321 (which may be optional) of step 2320, the UE provides the user data by executing a client application.
  • substep 2311 (which may be optional) of step 2310, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer.
  • the executed client application may further consider user input received from the user.
  • the UE initiates, in substep 2330 (which may be optional), transmission of the user data to the host computer.
  • step 2340 of the method the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.
  • FIGURE 24 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURS 19 and 20. For simplicity of the present disclosure, only drawing references to FIGURE 24 will be included in this section.
  • the base station receives user data from the UE.
  • the base station initiates transmission of the received user data to the host computer.
  • step 2430 (which may be optional)
  • the host computer receives the user data carried in the transmission initiated by the base station.
  • FIGURE 25 depicts a method 2500 by a wireless device for performing an access barring check, according to certain embodiments.
  • the wireless device is a UE.
  • the method begins at step 2505 when the wireless device identifies an access attempt. At least one matching rule tor a first access category' is determined at step 2510. At step 2515, a second access category is determined using criteria comprising at least the at least one matching rule for the first access category. At step 2520, the access barring check is performed for said identified access attempt using said determined second access category.
  • the criteria includes a list of matching rules for a tuple and the second access category is determined in response to determining that all of the matching rules in the list of matching rules for the tuple are fulfilled.
  • the criteria includes operator-defined criteria that are associated with a particular one of a plurality of tuples.
  • the method includes selecting a parti cul ar one of the plurality of tuples based on the particular one of the plurality of tuples having a highest precedence value of the plurality of tuples.
  • the particular one of the plurality of tupl es may be associated with a parameter comprising at least one of: o a precedence value indicating an order the wireless device shall evaluate a plurality of operator-defined access categories for determining the at least one matching rule;
  • an operator-defined access identity that uniquely identifies a particular one of a plurality of operator-defined access categories; and o a list of criteria comprising:
  • S- NSSAI single network slice selection assistance information
  • the method further includes receiving a plurality of operator-defined access categories from the network node.
  • the plurality of operator-defined access categories include at least the first access category in a further particular embodiment, the method may further include determining that a plurality of matching rales is satisfied and determining that the at least one matching rale for the first access category' has a highest priority .
  • determining the at least one matching rule for a first access category' may include evaluating a plurality of rules to determine the at least one matching rule for the first access category .
  • FIGURE 26 illustrates a schematic block diagram of an virtual apparatus 2600 in a wireless network (for example, the wireless network shown in FIGURE 14).
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device 1410 or network node 1460 shown in FIGURE 14).
  • Virtual apparatus 2600 is operable to carry out the example method described with reference to FIGURE 25 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 25 is not necessarily carried out solely by virtual apparatus 2600. At least some operations of the method can be performed by one or more other entities.
  • Virtual Apparatus 2600 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.
  • the processing circuitry may be used to cause identifying module 2610, first determining module 2620, second determining module 2630, performing module 2640, and any other suitable units of virtual apparatus 2600 to perform corresponding functions according one or more embodiments of the present disclosure.
  • identifying module 2610 may perform certain of the identifying functions of the virtual apparatus 2600. For example, identifying module 2610 may identify an access attempt.
  • first determining module 2620 may perform certain of the determining functions of virtual apparatus 2600. For example, first determining module 2620 may determine at least one matching rule for a first access category .
  • second determining module 2630 may perform certain other of the determining functions of virtual apparatus 2600. For example, second determining module 2630 may determine a second access category' using criteria comprising at least the at least one matching rule for the first access category .
  • performing module 2640 may perform certain of the performing functions of apparatus 2600.
  • performing module 2630 may perform the access barring check for said identified access attempt using said determined second access category .
  • FIGURE 27 depicts a method 2700 by a wireless device for performing an access barring check, according to certain embodiments.
  • the wireless device is a UE.
  • the method begins at step 2705 when the wireless device identifies an access attempt.
  • a first access category is determined at step 2710.
  • a second access category is determined using the first access categor .
  • the access barring check is performed for said identified access attempt using said determined second access category.
  • determining the first access category includes evaluating at least one rule to determine a match for the first access category’ and determining that criteria for the first access category is met
  • the first access category is a standardized access category and the second access category is an operator-defined access category’.
  • the second access category- is determined based on operator-defined criteria that is associated with a particular one of a plurality of tuples .
  • the method may further include selecting the particular one of tire plurality of tuples based on the particular one of the plurality of tuples having a highest precedence value of the plurality of tuples.
  • the particular one of the plurality of tuples is associatedsociated with a parameter comprising at least one of:
  • an operator-defined access identity that uniquely identifies a particular one of a plurality’ of operator-defined access categories; and o a list of criteria comprising:
  • the method may further include receiving a plurality of operator-defined access categories from the network node, the plurality of operator-defined access categories comprising at least the second access category.
  • the method may further include determining that a plurality of matching rules are satisfied and determining that the at least one matching rule for the first access category has a highest priority.
  • FIGURE 28 illustrates a schematic block diagram of a virtual apparatus 2800 in a wireless network (for example, the wireless network shown in FIGURE 14).
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device 1410 or network node 1460 shown in FIGURE 14).
  • Virtual apparatus 2800 is operable to carry out the example method described with reference to FIGURE 27 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 27 is not necessarily carried out solely by virtual apparatus 2800. At least some operations of the method can be performed by one or more other entities.
  • Virtual Apparatus 2800 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.
  • the processing circuitry may be used to cause identifying module 2810, first determining module 2820, second determining module 2830, performing module 2840, and any other suitable units of virtual apparatus 2800 to perform corresponding functions according one or more embodiments of the present disclosure.
  • identifying module 2810 may perform certain of the identifying functions of the virtual apparatus 2800. For example, identifying module 2810 may identify an access attempt.
  • first determining module 2820 may perform certain of the determining functions of apparatus 2800. For example, first determining module 282.0 may determine a first access category.
  • second determining module 2830 may perform certain other of the determining functions of apparatus 2800. For example, second determining module 2830 may determine a second access category using criteria comprising the first access category- .
  • performing module 2620 may perform certain of the performing functions of apparatus 2600. For example, performing module 2620 may perform the access barring check for said identified access attempt using said determined second access category .
  • the term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • Embodiment 1 A method by a wireless device for determining an operator-defined access category to perform an access barring check, the method comprising:
  • Embodiment 2 The method of embodiment I, wherein the criteria comprise a list of matching rules for a tuple and the first access category is determined in response to determining that ail of the matching rales in the list of matching rales for the tuple are fulfilled Embodiment 3.
  • Embodiment 4 The method of embodiment 3, selecting the particular one of the plurality of tuples based on the particular one of the plurality of tuples having a highest precedence value of the plurality of tuples.
  • Embodiment s The method of any of embodiments 1 to 4, wherein the particular one of the plurality of tuples is associatedsociated with a parameter comprising at least one of:
  • a precedence value indicating an order the wireless device shall evaluate a plurality of operator-defined access categories for determining the at least one matching rule
  • an operating system identifier or operating system application identifier an operating system identifier or operating system application identifier
  • S-NSSAI single network slice selection assistance information
  • Embodiment 6 The method of any of embodiments 1 to 5, further comprising receiving a plurality of operator-defined access categories from the network node, the plurality of operator-defined access categories comprising at least the first access category.
  • Embodiment 7 The method of any of embodiment 6. further comprising:
  • Embodiment 8 The method of any of embodiment 1 to 7, wherein determining the at least one matching rule for a first access category comprises evaluating a plurality of rales to determine the at least one matching rale for the first access category.
  • Embodiment 9 A computer program comprising instructions which when executed on a computer perform any of the methods of embodiments 1 to 8.
  • Embodiment 10 A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of embodiments 1 to 8.
  • Embodiment 11 A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of embodiments 1 to 8
  • a wireless device for determining an operator-defined access category to perform an access barring check comprising:
  • processing circuitry operable to execute the instructions to cause the network node to
  • Embodiment 13 The wireless device of embodiment 12, wherein the criteria comprise a list of matching rules for a tuple and the first access category is determined in response to determining that all of the matching rules in the list of matching rules for the tuple are fulfilled
  • Embodiment 14 The wireless device of any of embodiments 12 to 13, wherein the criteria are associated with a particular one of a plurality of tuples.
  • Embodiment 15 The wireless device of embodiment 14, wherein the processing circuitry ' i s operable to execute the instructions to cause the wireless device to select the particular one of the plurality of tuples based on the particular one of the plurality of tuples having a highest precedence value of the plurality of tuples.
  • Embodiment 16 The wireless device of any of embodiments 14 to 15, wherein the particular one of the plurality of tuples is associatedsociated with a parameter comprising at least one of:
  • a precedence value indicating an order the wireless device shall evaluate a plurality of operator-defined access categories for determining the at least one matching rule
  • an operating system identifier or operating system application identifier an operating system identifier or operating system application identifier
  • S-NSSAi single network slice selection assistance information
  • Embodiment 17 The wireless device of any of embodiments 12. to 16, wherein the processing circuitry is operable to execute the instructions to cause the wireless device to receive a plurality of operator-defined access categories from a network node, the plurality of operator-defined access categories comprising at least the first access category.
  • Embodiment 18 The wireless device of embodiment 17, wherein the processing circuitry is operable to execute the instructions to cause the wireless device to:
  • Embodiment 19 The wireless device of any of embodiment. 12 to 18, wherein determining the at least one matching rule for a first access category comprises evaluating a plurality of rules to determine the at least one matching ride for the first access category.
  • Embodiment 20 A communication system including a host computer comprising:
  • UE user equipment
  • the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of embodiments 1 to 8.
  • Embodiment 21 The communication system of embodiment 20, wherein the cellular network further includes a base station configured to communicate with the UE.
  • Embodiment 22 The communication system of any of embodiments 20 to 21, wherein:
  • the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data
  • the UE’s processing circuitry is configured to execute a client application associated with the host application.
  • Embodiment 23 A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:
  • Embodiment 24 At the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of embodiments 1 to 8.
  • Embodiment 24 The method of embodiment 23, further comprising at the UE, receiving the user data from the base station.
  • Embodiment 25 A communication system including a host computer comprising:
  • a - communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station
  • the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of embodiments 1 to 8.
  • Embodiment 26 The communication system of the embodiment 25, further including the UE.
  • Embodiment 27 The communication system of any of embodiments 25 to 26, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.
  • the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.
  • Embodiment 28 The communication system of any of embodiments 25 to 27, wherein:
  • the processing circuitry of the host computer is configured to execute a host application
  • the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.
  • Embodiment 29 The communication system of any of embodiments 25 to 28, wherein:
  • processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and - the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.
  • Embodiment 30 A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:
  • the host computer receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of embodiments 1 to 8.
  • Embodiment 31 The method of embodiment 30, further comprising, at the UE, providing the user data to the base station.
  • Embodiment 32 The method of the any of embodiments 30 to 31, further comprising:
  • Embodiment 33 The method of any one of embodiments 30 to 32, further comprising:
  • the user data to be transmitted is provided by the client application in response to the input data.
  • Embodiment 34 A method by a wireless device for determining operator-defined access category to perform access barring check, the method comprising:
  • Embodiment 35 The method of embodiment 34, wherein determining the first access category comprises:
  • Embodiment 36 The method of embodiments 34 to 35, wherein the first access category is an standardized access category and the second access category is an operator-defined access category'.
  • Embodiment 37 The method of embodiment 35, wherein the criteria are associated with a particular one of a plurality of tuples.
  • Embodiment 38 The method of embodiment 37, selecting the particular one of the plurality' of tuples based on the particular one of the plurality of tuples having a highest precedence value of the plurality of tuples.
  • Embodiment 39 The method of any of embodiments 37 to 38, wherein the particular one of the plurality of tuples is associatedsociated with a parameter comprising at least one of:
  • a precedence value indicating an order die wireless device shall evaluate a plurality of operator-defined access categories for determining the at least one matching rule
  • an operating system identifier or operating system application identifier an operating system identifier or operating system application identifier
  • S-NSSAI single network slice selection assistance information
  • Embodiment 40 The method of any of embodiments 34 to 39, further comprising receiving a plurality of operator-defined access categories from the network node, the plurality of operator-defined access categories comprising at least the second access category.
  • Embodiment 41 The method of any of embodiment 34, further comprising:
  • Embodiment 42 A computer program comprising instructions which when executed on a computer perform any of the methods of embodiments 34 to 41.
  • Embodiment 43 A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of embodiments 34 to 41.
  • Embodiment 44 A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of embodiments 34 to 41.
  • Embodiment 45 A wireless device for determining an operator-defined access category to perform an access barring check, the wireless device comprising:
  • processing circuitry operable to execute the instructions to cause the network node to
  • Embodiment 46 The wireless device of embodiment 45, wherein determining the first access category comprises:
  • Embodiment 47 The wireless device of embodiments 45 to 46, wherein the first access category is an standardized access category and the second access category is an operator-defined access category.
  • Embodiment 48 The wireless device of embodiment 47, wherein the criteria are associated with a particular one of a plurality of tuples.
  • Embodiment 49 Hie wireless device of embodiment 48, wherein the processing circuitry ' is operable to execute the instructions to cause the wireless device to select the particular one of the plurality of tuples based on the particular one of the plurality of tuples having a highest precedence value of the plurality of tuples.
  • Embodiment 50 The wireless device of any of embodiments 48 to 49, wherein the particular one of the plurality of tuples is associatedsociated with a parameter comprising at least one of:
  • a precedence value indicating an order the wireless device shall evaluate a plurality of operator-defined access categories for determining the at least one matching rule
  • S-NSSAI single network slice selection assistance information
  • Embodiment s ! The wireless device of any of embodiments 45 to 50, wherein the processing circuitry is operable to execute the instructions to cause the wireless device to receive a plurality of operator-defined access categories from the network node, the plurality of operator-defined access categories comprising at least the second access category.
  • Embodiment 52 The wireless device of embodiment 51, wherein the processing circuitry is operable to execute the instructions to cause the wireless device to:
  • Embodiment 53 A communication system including a host computer comprising:
  • UE user equipment
  • the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of embodiments 34 to 41.
  • Embodiment 54 The communication system of embodiment 53, wherein the cellular network further includes a base station configured to communicate with the UE.
  • Embodiment 55 The communication system of any of embodiments 53 to 54, wherein:
  • the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data
  • Embodiment 56 A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:
  • Embodiment 57 The method of embodiment 56, further comprising at the UE, receiving the user data from the base station.
  • Embodiment 58 A communication system including a host computer comprising:
  • a - communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station
  • the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of embodiments 34 to 41.
  • Embodiment 59 The communication system of the embodiment 58, further including the UE.
  • Embodiment 60 The communication system of any of embodiments 58 to 59, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.
  • the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.
  • Embodiment 61 The communication system of any of embodiments 58 to 60, wherein:
  • the processing circuitry of the host computer is configured to execute a host application
  • Embodiment 62 The communication system of any of embodiments 58 to 61, wherein:
  • the processing circuitry of the host computer is configured to execute a host application, thereby providing request data
  • the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.
  • Embodiment 63 A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:
  • the host computer receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of embodiments 34 to 41.
  • Embodiment 64 The method of embodiment 64, further comprising, at the UE, providing the user data to the base station.
  • Embodiment 65 The method of the any of embodiments 63 to 64, further comprising:
  • Embodiment 66 The method of any one of embodiments 63 to 65, further comprising:
  • the user data to be transmitted is provided by the client application in response to the input data.
  • RNC Radio Network Controller RNTI Radio Network Temporary Identifier

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé de réalisation d'un contrôle avec interdiction d'accès par un dispositif sans fil. Le procédé comprend l'identification d'une tentative d'accès et la détermination d'au moins une règle d'appariement pour une première catégorie d'accès. Une seconde catégorie d'accès est déterminée à l'aide de critères comportant au moins la ou les règles d'appariement pour la première catégorie d'accès. Le contrôle avec interdiction d'accès est effectué pour ladite tentative d'accès identifiée à l'aide de ladite seconde catégorie d'accès déterminée.
PCT/IB2019/053311 2018-05-14 2019-04-22 Détermination d'une catégorie d'accès défini par un opérateur dans une commande d'accès unifiée WO2019220234A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201862670953P 2018-05-14 2018-05-14
US62/670,953 2018-05-14

Publications (1)

Publication Number Publication Date
WO2019220234A1 true WO2019220234A1 (fr) 2019-11-21

Family

ID=66690722

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2019/053311 WO2019220234A1 (fr) 2018-05-14 2019-04-22 Détermination d'une catégorie d'accès défini par un opérateur dans une commande d'accès unifiée

Country Status (1)

Country Link
WO (1) WO2019220234A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210185590A1 (en) * 2018-06-18 2021-06-17 Nokia Technologies Oy Method and apparatus for controlling access to hosted virtual network using network identifiers
WO2022120544A1 (fr) * 2020-12-07 2022-06-16 北京小米移动软件有限公司 Procédé et dispositif de communication, et réseau d'accès sans fil, terminal et support de stockage
WO2022120751A1 (fr) * 2020-12-10 2022-06-16 北京小米移动软件有限公司 Procédé et appareil de communication, dispositif d'accès, terminal et support de stockage

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150036489A1 (en) * 2012-03-21 2015-02-05 Samsung-ro, Yeongtong-gu Granular network access control and methods thereof
WO2016118104A1 (fr) * 2015-01-22 2016-07-28 Intel IP Corporation Communication d'informations de régulation de congestion

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150036489A1 (en) * 2012-03-21 2015-02-05 Samsung-ro, Yeongtong-gu Granular network access control and methods thereof
WO2016118104A1 (fr) * 2015-01-22 2016-07-28 Intel IP Corporation Communication d'informations de régulation de congestion

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "5G UAC: establishment cause", vol. CT WG1, no. Kunming (P. R. China); 20180416 - 20180420, 20 April 2018 (2018-04-20), XP051425226, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings%5F3GPP%5FSYNC/CT1/updates/update11/> [retrieved on 20180420] *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210185590A1 (en) * 2018-06-18 2021-06-17 Nokia Technologies Oy Method and apparatus for controlling access to hosted virtual network using network identifiers
WO2022120544A1 (fr) * 2020-12-07 2022-06-16 北京小米移动软件有限公司 Procédé et dispositif de communication, et réseau d'accès sans fil, terminal et support de stockage
WO2022120751A1 (fr) * 2020-12-10 2022-06-16 北京小米移动软件有限公司 Procédé et appareil de communication, dispositif d'accès, terminal et support de stockage
CN114916251A (zh) * 2020-12-10 2022-08-16 北京小米移动软件有限公司 通信方法及装置、接入设备、终端及存储介质
CN114916251B (zh) * 2020-12-10 2023-10-31 北京小米移动软件有限公司 通信方法及装置、接入设备、终端及存储介质

Similar Documents

Publication Publication Date Title
US11412439B2 (en) Stop of barring timers
US20230262581A1 (en) Methods of determining access categories and/or establishment causes and related devices
CN111801981B (zh) 用于高效早期数据的传感器数据批处理
US11140617B2 (en) Method for access barring
US20210266932A1 (en) Methods, Apparatus and Computer-Readable Media Related to Semi-Persistent Scheduling Configuration
US11917695B2 (en) Early mobile-terminated data transmission
US20230362676A1 (en) Open radio access networks near-real time radio access network intelligent controller
WO2019220234A1 (fr) Détermination d&#39;une catégorie d&#39;accès défini par un opérateur dans une commande d&#39;accès unifiée
US20230254680A1 (en) Methods providing flexible communication between radio access and core networks and related nodes
EP4154666B1 (fr) Indiquer l&#39;état d&#39;indisponibilité d&#39;un dispositif de communication
US20230269640A1 (en) System and method for steering a wireless device to a network slice
US20230247525A1 (en) Association of network identities and unified access control parameters
US20220264518A1 (en) Resume in Paging
US20210409992A1 (en) Enhancements to MDT
WO2021076030A1 (fr) Sélection et consentement pour une activation de mdt
EP4042766A1 (fr) Distribution d&#39;informations se terminant sur un mobile pour un ue à plusieurs usim
US20220015038A1 (en) Mobile Terminated Early Data Transmission Reachability for RAN Context
WO2020148727A1 (fr) Interaction nas-as pour transmission de données précoce
US20220346021A1 (en) PSM and ANR Handling for Power Limited Devices
US20220131774A1 (en) Data volume reporting in 5gs
WO2021066699A1 (fr) Aspects de signalisation de groupe pour une connectivité double nr-nr (nr-dc) et une reconfiguration

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19728118

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19728118

Country of ref document: EP

Kind code of ref document: A1