• 专利附录
  • 专利说明
  • 权利要求
  • 类似技术
  • 同族专利
  • 引用文献
  • 法律状态
  • 优先权
    • 专利摘要:
      USE OF AN OMA MANAGEMENT OBJECT TO SUPPORT THE SATURATION CONTROL OF THE SPECIFIC APPLICATION ON MOBILE NETWORKS.The present invention relates to a technology for using an open mobile alliance (OMA) management object (MO) for saturation control in mobile networks. A new type of MO OMA for application specific access control (ASAC) can include internet protocol (IP) flow descriptions that can be used to characterize fine-grained applications. Priorities can be assigned to IP flows based on IP flow descriptions. A user device (EU) can receive such a MO OMA and also receive application bus information regarding a saturation level on a mobile network with which an application in the EU wishes to connect. The UE may have a connectivity manager (CM) that determines whether to allow the application to establish a connection to the mobile network based on the priority level of the application's associated IP flow and the application's bus information.
    公开号:BR112016017706A2
    申请号:R112016017706-1
    申请日:2015-02-18
    公开日:2020-10-27
    发明作者:Robert Zaus；Candy Yiu；Martin KOLDE；Jerome Parron；Ana Lucia A. Pinheiro；Marta Martinez Tarradell；Hyung-Nam Choi；Vivek Gupta；Chen-Ho Chin；Richard C. Burbidge
    申请人:Intel IP Corporation；
    IPC主号:
    专利说明:

    [001] [001] Saturation control of the specific data communication application (ACDC) is an ongoing 3GPP study in which service requirements are specified, in order to allow or prohibit certain applications from starting or maintaining communications on mobile networks. These service requirements may be defined by operators and / or be subject to regional regulations. ACDC is particularly interesting when traffic saturation on the network needs to prioritize some transmissions over others. Saturation control is typically performed at the mobile device level. For example, the access class bus can be used to reduce saturation in a radio access network, denying access to a selected percentage of mobile devices. However, the access class bus does not have the granularity to control the use and access to the network of specific types of applications operating on mobile devices. BRIEF DESCRIPTION OF THE DRAWINGS
    [002] [002] The characteristics and advantages of this description will be evident from the following detailed description, taken in conjunction with the attached drawings, which together illustrate, by way of example, the characteristics of this description; and, where:
    [003] [003] Figure 1a is a diagram that illustrates an exemplary structure of a specific application access control management (MO) object (ASAC), according to an example;
    [004] [004] Figure 1b is a diagram that illustrates a modified model of an access network search and selection function (ANDSF) management object, according to an example.
    [005] [005] Figure 2 is a diagram illustrating an exemplary structure of an ASAC container object according to an example;
    [006] [006] Figure 3 is a diagram that illustrates an exemplary structure of an ASAC rules node object according to an example;
    [007] [007] Figure 4 is a diagram that illustrates an exemplary structure of a ForFlowBased node that is a subobject of a node object of an inter-system routing policy (ISRP), according to an example;
    [008] [008] Figure 5 is a diagram that illustrates an exemplary structure of a ForServiceBased node that is a sub-object of a node of an inter-system routing policy (ISRP) according to an example;
    [009] [009] Figure 6 illustrates an exemplary system, in which a connectivity manager (CM) can operate according to an example;
    [0010] [0010] Figure 7 illustrates a non-limiting example of a code that can be used so that the application's bus information can be included in an information transmission system according to an example;
    [0011] [0011] Figure 8 illustrates a non-limiting example of a table of field descriptions for block information system 2 (Sib2) that can be associated with the example code of figure 7;
    [0012] [0012] Figure 9a illustrates a table detailing a first non-limiting example of syntax for an attention command (AT), according to an example;
    [0013] [0013] Figure 9b illustrates a table detailing a second non-limiting example of syntax for an attention command (AT), according to an example;
    [0014] [0014] Figure 2c illustrates a table detailing a third example
    [0015] [0015] Figure 10 is a flow diagram that illustrates the steps that can be applied to user equipment (EU), according to an example;
    [0016] [0016] Figure 11 is a flow diagram that illustrates the steps that can be applied to a cellular network according to an example; and
    [0017] [0017] Figure 12 illustrates a functional block diagram of a wireless communication device according to some modalities.
    [0018] [0018] Reference will now be made to the exemplary modalities illustrated and specific language will be used here to describe the same. However, it will be understood that it is not intended to limit the scope of the invention. DETAILED DESCRIPTION
    [0019] [0019] Before the present invention is disclosed and described, it is to be understood that this invention is not limited to the particular structures, process steps or materials described herein, but extends to their equivalents as would be recognized by those vul - only experts in the relevant technique. It should also be understood that the terminology used here is used for the purpose of describing particular examples only and is not intended to be limiting. The same reference numbers in different drawings represent the same element. Numbers provided in flowcharts and processes are provided for clarity in the illustration of steps and operations and do not necessarily indicate a particular order or sequence.
    [0020] [0020] An initial overview of the technology modalities is provided below and then specific technology modalities.
    [0021] [0021] According to current ACDC standards, a user equipment device (EU) can be pre-configured with a list of authorized ACDC applications based on operator policy and subject to regional regulations. A mobile network may also be allowed to dynamically configure a list of EU authorized ACDC applications based on the policy of the mobile network operator and subject to regional regulations. The mobile network may also be allowed to enable and / or disable ACDC control for certain types of applications started by the EU. According to the modalities of the present invention, when the ACDC control is activated, an UE, regardless of whether the UE is in an idle or connected mode, can determine which applications started by the UE will be allowed to start, maintain and or use a network connection based on the EU authorized ACDC application list.
    [0022] [0022] The current 3GPP model provides some limited types of control over the classes of applications that may be allowed to use network connections during periods of network traffic saturation. Access class buses (ACB), for example, allow networks to prohibit the US from initiating access to the random access channel (RACH) for specific access classes and for some applications, such as circuit switching backward (CSFB ). In addition, service-specific access control (SSAC) allows networks to prohibit the US from initiating any access to the multimedia voice or video telephony services of the multimedia internet protocol (IMS) subsystem. .
    [0023] [0023] These limited types of control offered by the current 3GPP model, however, have several disadvantages. First, while ACB and SSAC allow some control based on application classes, they do not provide a way to distinguish between different applications that belong to the same access class. Second, if an UE is in connected mode, ACB does not provide a way to control the establishment of support for a newly opened application. Third, ACB and SSAC are applied separately; the coordination of its functionalities within the EU can be complicated.
    [0024] [0024] Another possible approach to control network saturation involves the use of access point names (APN). An Access Point Name (APN) refers to a gateway between a mobile network (for example, a general packet radio service (GPRS) or a 3GPP network) and another computer network (for example, the public internet) . An APN identifies a packet data network (PDN) with which the UE intends to communicate. An APN can also be used to identify a type of service that is provided by the associated PDN. It has been proposed that an APN or a combination of packet filters can be used to identify specific applications to which saturation controls can be applied. However, this approach is also limited because many applications generally have the same APN (for example, the Internet APN). Barring an entire APN because an application using that APN is creating network overhead can therefore affect many other applications.
    [0025] [0025] A packet filter can be applied based on, for example, Transmission Control Protocol (TCP) port numbers. However, many different applications use the hypertext transfer protocol (HTTP) and therefore use the same TCP port (port 80), so filtering based on port numbers can still affect many benign applications.
    [0026] [0026] Thus, current ACDC concepts can be improved by defining a set of criteria that can distinguish applications with greater granularity. In addition, current ACDC concepts would also be improved if the details of the barred applications could be provided to some entity (for example, a connectivity manager (CM)) in the EU that is able to control the establishment of PDN connections via 3GPP before any related signaling is transferred via a radio interface.
    [0027] [0027] In accordance with the modalities of this description, a set of Internet protocol (IP) flow descriptions can be included in an Open Mobile Alliance (OMA) management object (MO). In this context, "objects" generally refer to software constructions or data structures (for example, in object-oriented programming environments). The MO OMA can be a newly defined management object that is intended primarily for ACDC purposes, such as an application-specific access control MO (ASAC). Alternatively, MO OMA can simply be a modified version of an existing management object, such as an access network search and selection (ANDSF) function object (for example, as defined in 3GPP TS 24.312). An IP flow description can comprise one or more of: a system-specific operational application ID (OSApplID), a fully qualified domain name (FQDN), or one or more packet filtering components (for example, components as defined in the Technical Specification (TS) of Third Generation Partnership Project (3GPP) 24.312 version 12.6.0). Alternatively, an IP flow description can be empty (that is, an empty | P flow node). The IP flow descriptions included in MO OMA can be used to characterize applications running in an EU with granularity.
    [0028] [0028] In an example, each IP flow described by an IP flow description included in the MO OMA can be assigned a priority level or a set of saturation levels where access to the network is allowed . In some embodiments, a standard priority level can also be assigned to any IP flow that is not described by the IP flow descriptions included in MO OMA. When saturation occurs on a mobile network, the mobile network can send a signal containing application bus information (for example, a saturation level) to an UE. The UE can be configured to determine whether a given EU application is authorized to establish and / or maintain a PDN connection if the priority level assigned to the EU application is sufficiently high in relation to the level of saturation on the network. Priority levels can be assigned for 3GPP access and / or access via other radio access technologies.
    [0029] [0029] In another example, the set of IP flow descriptions included in the MO OMA may comprise an ordered list. When saturation occurs on a mobile network, the mobile network can send a signal containing application bus information to an UE. The application bus information can comprise a bitmap with a number of bits corresponding to the number of IP flow descriptions; each bit can correspond to a specific IP flow description included in the MO OMA. The UE can be configured to allow EU applications whose corresponding bits in the bitmap are set to 1 establish and / or maintain PDN connections, while prohibiting EU applications whose corresponding bits in the bitmap are set to 0 to establish and / or maintain PDN connections.
    [0030] [0030] In another example, the application bus information received by an UE can be provided to a connectivity manager (CM). The connectivity manager can use the application bus information and the IP flow descriptions included in the MO OMA to decide how the UE will respond to new application requests to establish PDN connections. In addition, the CM can use the application bus information and IP flow descriptions included in the MO OMA to determine how these new application requests (and the EU response to them) will affect the transmission of binding data packets. upward for existing PDN connections (if at all). In some cases, it may be allowed to redirect traffic from certain P flows to different radio access technologies (for example, from 3GPP to a WLAN). In some modalities, the CM can determine how a new application request will affect the transmission of uplink data packets to existing PDN connections, using one or more routing tables that are being used by the protocol stack EU TCP / IP to direct uplink (UL) packets. The CM can add new rules to the routing tables or read, modify or delete existing rules.
    [0031] [0031] Figure 1a is a diagram illustrating an example of a possible structure of an application specific access control management (MO) object (ASAC) 100. The MO ASAC 100 can be an object comprising an ASAC container 110. In other words, the ASAC 110 container, as illustrated in 1a, may be a subobject that is referenced in the MO ASAC 100. The A-SAC 110 container may also comprise one or more subobjects. These additional subobjects are shown in more detail in figures 2-3.
    [0032] [0032] Figure 1b is a diagram that illustrates a modified structure of a management object (MO) of search function and selection of access network (ANDSF) 120 according to another modality. The ANDSF MO can be an object that comprises an ASAC 130 container. The ASAC 130 container can be a subobject that is referenced in the MO ANDSF 120. The ASAC 130 container can also comprise one or more subobjects. These additional subobjects are shown in more detail in figures 2-3.
    [0033] [0033] Figure 2 is a diagram that illustrates an example of a possible structure of an ASAC 200 container (ie, an ASAC MO). The ASAC 200 container can be an object comprising an ASAC Rules 210 subject, a roaming sheet, a PLMN sheet and an update policy sheet. "Leaf", as used in the context of some modalities, can refer to an object or some other data construction (for example, a primitive data type variable, a matrix or a record) that does not contain any references other objects. The ASAC Rules subobject 210 (also known as ASAC rules node) can also comprise one or more subobjects and a set of ASAC rules. These additional subobjects are shown in more detail in the figure
    [0034] [0034] Figure 3 is a diagram illustrating an example of a possible ASAC rules node 300 structure (also known as ASAC Rules subobject). An ASAC rules node 300 can comprise an IP flow node 310 (also known as, an IP flow subobject), a bus rule node 320 (also known as, a bus rule subobject) and a leaf rule priority 330.
    [0035] [0035] An IP flow node 310 may comprise one or more IP flow descriptions. The IP flow node can also contain zero IP flow descriptions; in this case, the empty IP flow node can be interpreted as a fully corresponding IP flow description. The IP flow description can comprise up to an App-ID 340 node (also known as an App-ID subobject) and more sheets that define additional criteria, such as address type (for example, IPv4 or IPv6), a range of source IP addresses, a range of destination IP addresses, a fully qualified domain name (FQDN) or an APN. An IP flow can be said to correspond to an IP flow description if the IP flow meets all the criteria.
    [0036] [0036] An App-ID 340 node can include one or more operating system identifiers (OSlds) 360 and, for each operating system identifier, a set of one or more operating system-specific application identities (OSApplds) 370 OSApplds can be stored as series on certain operating systems (for example, Android, iOS and Blackberry). A FQDN (for example, Domain name 350 in figure 3) can be resolved to a destination | P address of an application server by querying a Domain Name System (DNS) into a protocol address. Internet (IP). In some modalities, Domain name 350, OSId 360 and OSAppld 370 can be used to define the IP flow descriptions.
    [0037] [0037] A Bus Rule 320 node (also known as a Bus Rule subobject) may comprise one or more sub-nodes, each of which may comprise an Access Technology sheet, an ID access sheet, an Secondary ID access sheet, ASAC priority level sheet and current flow affected sheet. Access technology 380 may specify the radio access technology to which the priority levels apply. For certain radio access technologies, a specific radio access network can again be specified by an access ID and, optionally, a secondary access ID. For example, for wireless local area networks (WLANs), the access ID can be given by a Service Set ID (SSID) and the secondary access ID by a Homogenous Extended Service Set ID (HESSID). The ASAC 390 priority level sheet can specify the priority level (or permissible saturation level, depending on the mode) that applies to the IP 310 flow node. Priority levels can be assigned to one or more different access technologies radio. In some modalities, the ASAC priority level can be stored as an integer. In others, the permissible saturation level can be coded as a list of integers or as a bitmap.
    [0038] [0038] The affected flow sheet in progress 392 can specify whether a change in application bus information affects one or more IP flows for which a PDN connectivity has already been established (ie IP flows in progress) ). In some embodiments, if the affected sheet of flow in progress 392 is not present, an IP flow in progress is not affected. If the current flow affected sheet 392 is present, the current flow affected sheet 392 can also indicate whether an ongoing flow can be prevented and whether an ongoing flow can be redirected through an alternative radio access technology. If an ongoing stream can be redirected (for example, via WLAN), an UE may still attempt to send affected uplink packets via alternative radio access technology.
    [0039] [0039] Rule priority sheet 330 can be used to determine which ASAC rule will be applied if an IP stream matches several different IP stream descriptions. In some modes, ASAC rules can be prioritized and ASAC rules can be evaluated in order of priority to match an IP stream.
    [0040] [0040] Figure 4 is a diagram illustrating an example of a possible structure of a ForFlowBased 400 node that is a subobject of the inter-system routing policy (ISRP) 132 node represented in MO ANDSF 120 of figure1b. In this example, the ASAC 410 priority level sheet and the current flow affected sheet 420 can be included under the routing rule sub-object 430, as illustrated. In this case, the ASAC priority level sheet 410 and the affected flow sheet in progress 420 can be used in the same ways described above.
    [0041] [0041] Figure 5 is a diagram illustrating an example of a possible structure of a ForServiceBased 500 node that is a sub-object of the inter-system routing policy (ISRP) 132 node represented in MO ANDSF 120 of figure1b. In this example, the ASAC priority level sheet 510 and the current flow affected sheet 520 can be included under the routing rule sub-object 530, as shown. However, if this approach sets priorities using only APN, it may not provide the ability to distinguish applications with the same level of granularity that can be achieved using the examples shown in FIGS 3-4.
    [0042] [0042] Figure 6 is a diagram illustrating an exemplary system 600 in which a connectivity manager (CM) can operate. The CM 610 (ie, the CM module) can receive a request for connectivity from a 612 application. From the type of service that is requested (for example, Internet connectivity), the CM 610 can determine an APN and the radio access technologies that may be suitable to provide the service. If necessary, the radio interface layer (RIL) 614 or CM 610 can create one or more network interfaces (NIC), such as NIC1 616, NIC2 618 and NIC3 620, for the appropriate radio access technologies ( for example, 3GPP, WLAN) and create or update related entries in the 622 routing table (s). Depending on the availability of the network interfaces for specific radio access technologies, the routing rules in the table (s) ) routing 622 (for example, standard routes for a given traffic), and the flow distribution rules in the MO ANDSF 624, the CM 610 can then select a radio access technology and establish a PDN connection through the selected radio access technology (if such a PDN connection does not already exist as a result of a previous request from another application / service).
    [0043] [0043] In some modalities, when the 612 application sends a request to the CM 610 for a connection, the CM 610 can first verify that a | P flow to the requesting application matches an IP flow description (and rule Corresponding ASAC) in an ASAC 626 MO. There may be a standard ASAC rule that applies to the IP flow that does not match any description of IP flow in the ASAC 626 MO. In some modalities, as explained above, the MO ASAC (that is, the ASAC container) can be referenced within MO ANDSF 624. If an applicable ASAC rule, made in context with the application bus information received from a network, prohibits the granting of connectivity to the application 612, the CM 610 can determine that the radio access technology of this network is not suitable for connectivity to the application
    [0044] [0044] If a network using an alternative radio access technology does not prohibit the granting of connectivity to the requesting application, the CM 610 can fulfill the request of the requesting application using alternative radio access technology. If the CM 610 cannot fulfill the request, the CM 610 can send a rejection message to the 612 application. In some modalities, the CM 610 can memorize the rejected application. When a radio access technology (RAT) becomes available again for the 612 application, the CM 610 can notify the 612 application that a RAT is available for a connection. The 610 application can then repeat the request, if necessary. In some modalities, the CM 610 can notify the 610 application when a RAT becomes available only if the 610 application specifically requests that notification.
    [0045] [0045] After a favorable PDN connection has been established, CM 610 can update routing table (s) 622, if necessary, by adding a new routing rule for the specific application. The TCP / IP stack can use the routing table (s) to select a network interface for forwarding uplink data packets that the TCP / IP stack 628 receives from application 612 In some embodiments, there may be several rules for routing specific applications in routing table (s) 622, if an application can use more than one radio access technology.
    [0046] [0046] In some modalities, a parameter called "metric" (here the "metric parameter") can be assigned to the routing rules in routing table (s) 622. The metric parameter can be used to set the priority for a routing rule so that, even if routing table (s) 622 includes more than one rule that applies to a user data packet, a routing with the highest priority can be chosen by the TCP / IP stack 628 for the user data packet.
    [0047] [0047] In some modalities, there is only one application-specific forwarding rule by application 612. Each time the network changes the access control of the specific application, the CM 610 can update the forwarding rule accordingly (for example , changing the NIC (s) included in the rule). In another mode, there may be multiple application-specific routing rules in routing table (s) 622, if an application 612 can use more than one access technology. The CM 610 can update the metric parameter of one or more of the applicable rules (for example, the metric parameter of a rule for forwarding via 3GPP access) when the access control information specific application for access via a certain RAT (eg 3GPP) changes. Ongoing IP Flow Management
    [0048] [0048] In some modalities, when a UE receives updated application bus information, a check can be done to determine whether the updated application bus information affects the routing for any current IP flow. The technical feasibility of this option may depend on the implementation of the TCP / IP stack, since, in some implementations, changing a routing rule will result in a release of the TCP connection.
    [0049] [0049] In some modalities, an IP flow for an operator service application can be considered as ongoing, if there is already a PDN connectivity for the IP flow and a related forwarding rule in the (s) routing table (s) 622. To find out if an IP flow for an extended application (OTT) is in progress, the CM 610 can query the operating system to verify that all packets have been transferred using the port (s) ) specific (s) assigned to the OTT application.
    [0050] [0050] In some modalities, if the 3GPP access for the 612 application becomes blocked for the current IP flow, due to the updated application bus information, and the Ongoing-FlowAffected sheet (for example, 392 , as illustrated in figure 3) in the MO ASAC 626 indicates that forwarding via other radio access technologies is not allowed, the CM 610 can update the internal forwarding tables to block the IP flow. Thus, when application 612 provides user data packets for uplink transmission, the TCP / IP stack will not be able to deliver them to the cellular modem user plan. If the OngoingFlowAffected sheet in MO ASAC 626 indicates that forwarding via other access technologies is allowed, the CM 610 can select an alternative radio access technology (for example, WLAN) and try to establish connectivity PDN through alternative radio access technology. The CM 610 can also update the routing table (s) 622. When the application 612 provides user data packets for uplink transmission, the TCP / IP stack can forward these EU packets internally to the plan of user for alternative radio access technology.
    [0051] [0051] In some modalities, if the 3GPP access for the 612 application becomes available again for the current IP flow due to the update of the application bus information received from the network, and the OngoingFlowAffected sheet (for example, 392, as illustrated in figure 3) in the MO ASAC 626 indicates that forwarding via other access technologies is not allowed, the CM 610 can update the routing table (s) 622 to resume the IP flow via 3GPP access. So when application 612 provides user data packets for uplink transmission,
    [0052] [0052] In some modalities, the OngoingFlowAffected sheet in the MO ASAC 626 may indicate that forwarding via other radio access technologies is allowed. If there is already a PDN 3GPP connectivity to the established IP flow, the CM 610 can update the routing table (s) 622. Thus, when the 612 application provides user data packets for uplink transmission, the TCP / IP stack 628 can route these EU packages internally to PDN 3GPP connectivity, unless there is PDN connectivity through an alternative radio access technology that has a higher access priority according to the MO ANDSF 624. Optionally, if there is no established 3GPP PDN connectivity, and the 3GPP access technology has a higher access network priority in the MO ANDSF 626 than the radio access technology of the connectivity (s) ) Existing PDN (s), CM 610 can attempt to establish 3GPP PDN connectivity and update routing table (s) 622, such that the TCP / IP stack 628 can forward user data packets through of the 3GPP PDN connectivity. Barred or unused PDN connectivities can be released if the application bus information from the network falls below a certain minimum threshold level or if there are other indications of overload / saturation in the network. Signaling application bus information from the network to the EU
    [0053] [0053] In some modalities, when saturation occurs in a network, the network can transmit application bus information through a transmission of system information so that the US in INACTIVE mode can receive it. The network can provide the information, additionally, through dedicated signaling (for example, for EU in CONNECTED mode).
    [0054] [0054] Figure 7 illustrates a non-limiting example of a code that can be used for the purpose of the application bus information being included in a system information transmission (block information system 2 (Sib2), TS 3GPP 36,331).
    [0055] [0055] Figure 8 illustrates a non-limiting example of a table of Sib2 field descriptions that can be associated with the example code in figure 7. As shown, the indication of the saturation level is an indication of a saturation level in the cell. A selected maximum number of saturation levels in a cell is defined as "maxCongestionLevels". In this example, an indication of the O saturation level indicates that there is no saturation. These values can be included in the SIB code illustrated in the example in figure 7.
    [0056] [0056] In one mode, the network can send a saturation level (for example, an integer value from 0 to n). This is the minimum level of priority that an IP stream or application needs to have in order to be authorized to establish PDN connectivity or send user data. By default, the lowest saturation level can be 0; a saturation level of O need not be signaled by the network. In modalities where the maximum saturation level n = 1, the network can only effectively signal "overload on / off."
    [0057] [0057] In another mode, the network can transmit a bitmap, where each bit corresponds to a specific IP flow in an ordered list of IP flows in the MO ASAC. For applications that are not associated with an IP flow for which there is a description of the IP flow in the MO ASAC, the network can transmit an additional bit in the bitmap to represent a standard bus state.
    [0058] [0058] In some modalities, the network may provide application bus information about non-3GPP radio access technologies, in addition to application bus information about 3GPP. There are several ways in which the network can provide application bus information about non-3GPP radio access technologies. In one option, the network can signal separate application bus information for non-3GPP access technologies, such as Institute of Electronics and Electrical Engineers (IEEE) 802.11, Bluetooth, IEEE 802.16 and other non-3GPP access technologies. The network can, in one example, signal a saturation level for a WLAN operation based on a non-3GPP access technology, with a specific service set identifier (SSID) value. In another example, the network can signal this saturation level for all WLANs by not including any specific SSID. Alternatively, the network can send a signal that indicates that the same application bus information (for example, saturation level) that was sent for 3GPP access is also applicable for non-3GPP access. This option would be useful if saturation occurred at the bottom of the nuclear network at the PDN gateway (P-GW); rerouting data traffic would not alleviate this type of saturation because the packets would eventually be routed to the same P-GW. Signaling of application bus information within the I
    [0059] [0059] In some modalities, within an EU, the application bus information received from a network is sent by the cellular protocol stack to the entity that is also using the MO ANDSF. In some modalities, the entity that uses the MO ANDSF is a CM. The cellular protocol stack can use a new attention command (AT) (see TS 3GPP 27.007 version 12.6.0) to signal to the CM. The CM can send a request to the cellular protocol stack to start or stop the application bus information reports. The cellular protocol stack can respond immediately with the current application bus information received from the network, if any, and provide additional unsolicited updates to the CM later when the network updates the application bus information.
    [0060] [0060] Figure 9a illustrates a table detailing a first non-limiting example of syntax for an AT command, which can be used by a CM to configure a cellular protocol stack to forward CM application bus information. The mode parameter can be an integer value of O or 1. An O mode value can disable unsolicited application bus information reporting, while a mode value of 1 can enable reporting information. application bus requests. The saturation level parameter (CongLevel) can be an integer that ranges from 0 to 9, with higher numbers indicating higher levels of saturation.
    [0061] [0061] Figure 9b illustrates a table detailing a second non-limiting example of syntax for an AT command, which can be used by a cellular protocol stack to forward, after requesting a CM, application bus information to the CM. The CongLevel parameter can be an integer ranging from 0 to 9, with higher numbers indicating higher levels of saturation.
    [0062] [0062] Figure 2c illustrates a table detailing a third non-limiting example of syntax for an AT command, which can be used by a cellular protocol stack to forward, after requesting a CM, application bus information to the CM . The priority level parameter (PrioLevel) can be an integer value ranging from 0 to 9, where O means that applications at all priority levels are allowed to establish network connections and 9 means that only applications at a higher priority level they are allowed to establish network connections.
    [0063] [0063] Figure 10 is a flow diagram that illustrates steps 1000, which can be applied in an EU, according to some modalities. As in 1010, circuits in the EU can be configured to receive an Open Mobile Alliance (OMA) management object (MO) from an OMA device management (DM) server. The MO OMA can comprise an MO ASAC. As in 1020, circuits in the EU can be configured to identify a set of internet protocol (IP) flow descriptions in the MO OMA. Each IP flow description in the IP flow description set can describe one or more applications that operate in the EU and that interact with one or more remote servers or remote machines. A description of the IP flow can comprise one or more of an empty IP flow node, a system-specific operational application ID (OSAppID), a fully qualified domain name (FQDN), or one or more components of packet filtering as defined in the Technical Specification (TS) of Third Generation Partnership Project (3GPP) 24.312 version 12.6.0. MO OMA can define an ASAC priority level for each IP flow description. The set of IP flow descriptions can comprise an ordered list. As in 1030, circuits in the EU can be configured to receive application bus information from a mobile network. The application bus information can be included in an information system transmission or in a dedicated signal. The application bus information can comprise a level of saturation of network traffic. The application bus information can comprise a bitmap comprising a sequence of bits, where each bit corresponds to an IP flow description in an ordered list of IP flow descriptions. As in 1040, circuits in the EU (which can comprise a connectivity manager (CM)) can be configured to use the set of IP flow descriptions (which can be comprised in an ordered list), ASAC priority levels applications and application bus information to determine whether one or more applications operating in the EU are authorized to communicate with one or more remote servers or remote machines.
    [0064] [0064] Figure 11 is a flow diagram that illustrates steps 1100 that can be applied to a mobile network according to some modalities. As in 1110, circuits on the network can be configured to send an Open Mobile Power (OMA) management object (MO) from an OMA device management (DM) server to an EU. The MO OMA can comprise a set of internet protocol (IP) flow descriptions. The MO OMA can comprise an MO ASAC. Each IP flow description in the IP flow description set can describe one or more applications that operate in the EU and that communicate with one or more remote servers or remote machines. An IP flow description can comprise one or more of an empty IP flow node, a system-specific operational application ID (OSAppID), a fully qualified domain name (FQDN), or one or more filtering components of packages as defined in the Technical Specification (TS) of Third Generation Partnership Project (3GPP) 24,312 ver-
    [0065] [0065] Figure 12 provides an example illustration of the wireless device, such as a user equipment (EU), a mobile station (MS), a wireless mobile device, a mobile communication device, a tablet, phone, or other wireless device. The wireless device may include one or more antennas configured to communicate with a node, macro node, low energy node (LPN), or transmission station, such as a base station (BS), a Node B (eNB ) evolved, a base band unit (BBU), a remote radio station (RRH), a remote radio equipment (RRE), a relay station (RS), a radio equipment (RE) or other type of point wide wireless area access (WWAN). The wireless device can be configured to communicate using one or more wireless communication standards, including LTE
    [0066] [0066] Figure 12 also provides an illustration of a microphone and one or more speakers, which can be used to input and output audio from the wireless device. The display can be a liquid crystal display (LCD), or another type of display screen, such as an organic light-emitting diode (OLED) screen. The screen can be configured as a touchscreen. The touchscreen can use capacitive, resistive technology or another type of touchscreen technology. An application processor and graphics processor can be coupled to the internal memory to provide processing and visualization capabilities. A non-volatile memory port can also be used to provide input / output options for a user. The non-volatile memory port can also be used to expand the memory capabilities of the wireless device. A keyboard can be integrated with the wireless device or connected wirelessly to the wireless device to provide additional input to the user. A virtual keyboard can also be provided using the touchscreen.
    [0067] [0067] Various techniques, or certain aspects or parts thereof, may take the form of program code (ie instructions) embodied in tangible media, such as floppy disks, CD-ROMs, hard drives, readable non-transitory storage medium by computer, or any other computer-readable storage medium, in which, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes a device for practicing the various techniques. Circuits may include hardware, firmware, program code, executable code, computer instructions and / or software. A computer-readable non-transitory storage medium may be a computer-readable storage medium that does not include the signal. In the case of executing program code on programmable computers, the computing device may include a processor, a processor-readable storage medium (including volatile and non-volatile memory and / or storage elements), one or more devices input and one or more output devices. Volatile and non-volatile memory and / or storage elements can be a RAM, EPROM, flash drive, optical drive, magnetic hard drive, solid state drive or other storage medium for electronic data. The node and wireless device may also include a transceiver module, a counting module, a processing module and / or a clock or timer module. One or more programs that can implement or use the various techniques described here can use an application programming interface (API), reusable controls, and so on. These programs can be implemented in a high procedural or object-oriented programming language to communicate with a computer system. However, the program (s) can be applied together or with machine language, if desired. In any case, the language can be a compiled or interpreted language, and combined with hardware implementations.
    [0068] [0068] It should be understood that many of the functional units described in the present specification have been labeled as modules, in order to highlight more particularly their independence of execution. For example, a module can be implemented as a hardware circuit comprising VLS | customized, ready-to-use semiconductors, such as logic chips,
    [0069] [0069] The modules can also be implemented in software for execution by different types of processors. An executable code identification module can, for example, comprise one or more physical or logical blocks of computer instructions, which can, for example, be organized as an object, procedure or function. However, the executables of an identified module do not need to be physically located together, but can comprise disparate instructions stored in different locations that, when logically together, make up the module and achieve the objective set for the module.
    [0070] [0070] In effect, an executable code module can be a single instruction, or several instructions, and can even be distributed over several different code segments, between the different programs, and through several different devices. memory. Likewise, operational data can be identified and illustrated here within the modules, and can be carried out in any suitable way and organized into any suitable type of data structure. Operational data can be collected as a single data set, or it can be distributed to different locations, including across different storage devices, and can exist, at least partially, only as electronic signals from a system or network. The modules can be passive or active, including operable agents to perform the desired functions.
    [0071] [0071] Reference throughout this specification as "an example" means that a particular feature, structure, or feature described in connection with the example is included in one or more models
    [0072] [0072] As used herein, a plurality of items, structural elements, elements of composition and / or materials can be presented in a common list for convenience. However, these lists must be interpreted as if each member of the list was identified individually as an individual and unique member. Therefore, no individual member of that list should be interpreted as a de facto equivalent of any other member of the same list solely on the basis of its presentation in a common group, without any indication to the contrary. In addition, various embodiments and examples of the present invention can be mentioned here together with alternatives for the various components thereof. It is understood that these modalities, examples and alternatives are not to be interpreted as de facto equivalent to each other, but are to be considered as separate and autonomous representations of the present invention.
    [0073] [0073] In addition, the features, structures or features described can be combined in any suitable way in one or more modalities. In the following description, numerous specific details are provided, as examples of diagrams, distances, network, etc., to provide an exhaustive understanding of the modalities of the invention. A person skilled in the relevant art will recognize, however, that the invention can be practiced without one or more of the specific details, or with other methods, components, schemes, etc. In other cases, well-known structures, materials or operations are not shown or described in detail to avoid obscuring aspects of the invention.
    [0074] [0074] While the foregoing examples are illustrative of the principles of the present invention in one or more particular applications, it will be apparent to those skilled in the art that numerous changes in form, use and details of execution can be made without the exercise of inventive faculty, and without departing from the principles and concepts of the invention.
    Therefore, the invention is not intended to be limited, except for the claims set out below.
    权利要求:
    Claims (30)
    [1]
    1. User equipment (EU) operable to communicate data from a mobile network, the EU characterized by the fact that it comprises one or more processors configured to: receive an Open Mobile Alliance (OMA) management object (MO) ) from an OMA device management (DM) server; identify a set of internet protocol (IP) flow descriptions in MO OMA, where each IP flow description in the set of IP flow descriptions describes one or more applications that operate in the EU and that interact with one or more remote servers or remote machines; receive application bus information from the mobile network; and use the set of IP flow descriptions and the application's bus information to determine whether one or more applications operating in the EU are authorized to communicate with one or more remote servers or remote machines.
    [2]
    2. EU according to claim 1, characterized in that one or more IP flow descriptions in the IP flow description set comprise one or more of: an empty IP flow node; an operating system-specific application ID (O-SAppID); a fully qualified domain name (FQDN); one or more packet filtering components, as defined in the Third Generation Partnership Project Technical Specification (TS) (S3GPP) 24.312 version 12.6.0; or a combination of them.
    [3]
    EU according to claim 1, characterized by the fact that the application bus information is received in one or more of: a dedicated signaling message or a transmission of system information.
    [4]
    4. EU according to claim 1, characterized by the fact that the application bus information comprises a level of traffic saturation on the mobile network.
    [5]
    5. EU according to claim 1, characterized by the fact that a priority level is assigned to each IP flow description in the | P flow description set.
    [6]
    6. EU according to claim 1, characterized by the fact that a standard priority level is assigned to applications that are not described by an IP flow description in the set of IP flow descriptions.
    [7]
    7. EU according to claim 5, characterized by the fact that the one or more processors are still configured to determine whether the one or more applications operating in the EU are authorized to establish a data network connectivity by package. (PDN) with the mobile network based on the priority levels assigned to one or more IP flow descriptions that correspond to one or more applications and to a level of traffic saturation received in the application bus information.
    [8]
    8. EU according to claim 5, characterized by the fact that the one or more processors are further configured to determine whether the one or more applications operating in the EU are authorized to communicate with one or more remote servers or remote machines based on the priority levels assigned to one or more IP flow descriptions that correspond to one or more applications and a level of traffic saturation received in the application bus information.
    [9]
    9. UE according to claim 8, characterized by the fact that the UE is able to communicate data through one or more alternative radio access technologies (RATs) and the one or more processors are further configured to communicate with one or more remote servers or remote machines through one or more alternative RATs, if communication through a first RAT is not allowed.
    [10]
    10. EU according to claim 1, characterized by the fact that the EU is able to communicate data through a first radio access technology (RAT) and one or more alternative radio access technologies (RATs) and a priority level is assigned to each | P stream for the first RAT and each IP stream for one or more of the one or more alternative RATs.
    [11]
    11. EU according to claim 10, characterized by the fact that the one or more processors are still configured to determine whether the one or more applications operating in the EU are authorized to communicate with one or more remote or remote servers. remote machines through the first RAT based on: the priority levels assigned to the first RAT for one or more IP flow descriptions that correspond to one or more applications; and a level of traffic saturation received by the first RAT in the application bus information.
    [12]
    12. EU according to claim 11, characterized by the fact that, if communication through the first RAT is not allowed, the one or more processors are still configured to determine if the one or more applications operating in the EU are allowed to communicate with one or more remote servers or remote machines through one or more alternative RATs based on the priority levels assigned to one or more alternative RATs for IP flow descriptions and based on a level of traffic saturation received for one or more alternative RATs in the application bus information.
    [13]
    13. EU according to claim 1, characterized in that the set of IP flow descriptions comprises an ordered list of | P flow descriptions.
    [14]
    14. EU according to claim 13, characterized by the fact that the application bus information from the mobile network comprises a bitmap, the bitmap comprising a sequence of bits, in which each bit corresponds to a | P flow description in the ordered list of IP flow descriptions.
    [15]
    15. EU according to claim 14, characterized by the fact that the one or more processors are still configured to determine whether the one or more applications operating in the EU are authorized to establish packet data network connectivity ( PDN) with the mobile network based on a bit definition corresponding to one or more IP flow descriptions that correspond to one or more applications.
    [16]
    16. EU according to claim 1, characterized by the fact that the one or more processors are still configured to operate a connectivity manager (CM) module, the CM module using the set of IP flow descriptions and the application bus information to determine whether the one or more applications operating in the EU are authorized to establish packet data network (PDN) connectivity with the mobile network.
    [17]
    17. EU according to claim 16, characterized by the fact that the CM module is further configured to use the set of IP flow descriptions and the application bus information to determine whether the one or more more applications operating in the EU are allowed to continue using existing PDN connections to the cellular network.
    [18]
    18. EU according to claim 16, characterized by the fact that the application bus information is received by a radio resource control layer (RRC) in the EU and supplied to the CM module via an attention command ( AT).
    [19]
    19. EU according to claim 16, characterized by the fact that the CM module reads one or more rules from one or more routing tables, to one or more routing tables to be used by a protocol stack Internet protocol / transmission control (TCP / IP) in the EU for forwarding uplink packets from the EU.
    [20]
    20. EU according to claim 19, characterized by the fact that the CM module is configured to modify one or more routing tables by one or more of the following: adding new rules, modifying existing rules or the exclusion of existing rules.
    [21]
    21. EU according to claim 20, characterized by the fact that one or more rules in the routing table are defined or modified based on one or more IP flow descriptions in the set of IP flow descriptions and the application bus information.
    [22]
    22. EU according to claim 20, characterized by the fact that one or more rules in the routing table are defined or modified according to the radio access technology (RAT) determined to be used to communicate with one or more remote servers or remote machines.
    [23]
    23. Network node in a mobile network operable to transmit data to user equipment (EU), the network node in the mobile network characterized by the fact that it comprises one or more processors configured to: send a management object (MO) Mobile Alliance
    Open (OMA) from an OMA device management (DM) server to the EU, the MO OMA comprising a set of Internet protocol (IP) flow descriptions, each IP flow description in the set of Internet descriptions IP flow describing one or more applications that operate in the EU and communicate with one or more remote servers or remote machines; identify a level of saturation of network traffic that affects at least part of the mobile network; and send application bus information to the UE that allows the UE to identify whether the one or more applications that operate in the UE are authorized to communicate with one or more remote servers or remote machines.
    [24]
    24. Network node according to claim 23, characterized by the fact that one or more IP flow descriptions in the set of IP flow descriptions comprise one or more of: a flow node object Empty IP; an operating system-specific application ID (O-SApplD); a fully qualified domain name (FQDN); one or more packet filtering components, as defined in the Technical Specification (TS) of Third Generation Partnership Project (3GPP) 24.312 version 12.6.0; or a combination of them.
    [25]
    25. Network node according to claim 23, characterized by the fact that the application bus information is sent in one or more of: a dedicated signaling message to the EU or a transmission of system information .
    [26]
    26. Network node according to claim 23, characterized by the fact that the application bus information comprises the level of traffic saturation on the mobile network.
    [27]
    27. Network node according to claim 23, characterized by the fact that the one or more processors are configured to send updated application bus information if the traffic network's saturation level changes.
    [28]
    28. Network node according to claim 23, characterized by the fact that the set of IP flow descriptions comprises an ordered list of IP flow descriptions.
    [29]
    29. Network node according to claim 28, characterized by the fact that the application bus information comprises a bitmap, the bitmap comprising a sequence of bits, in which each bit corresponds to an IP flow description in the ordered list of IP flow descriptions.
    [30]
    30. Network node according to claim 28, characterized by the fact that the definition of the bits corresponding to one or more IP flow descriptions indicates whether the one or more applications operating in the EU and which correspond to one or more further IP flow descriptions are allowed to establish packet data network (PDN) connectivity with the mobile network.
    类似技术:
    公开号 | 公开日 | 专利标题
    BR112016017706A2|2020-10-27|USE OF AN OMA MANAGEMENT OBJECT TO SUPPORT SPECIFIC APPLICATION SATURATION CONTROL IN MOBILE NETWORKS
    TWI651975B|2019-02-21|Supply technology in the application category of user devices during network congestion |
    BR112020023244A2|2021-02-23|message and system for influence of application function on the traffic route
    JP6822402B2|2021-01-27|Wireless terminal and its method
    US10616930B2|2020-04-07|Communication data processing method, apparatus, and system
    US9420590B2|2016-08-16|Mobile gateway, control method for the same, and radio access network equipped with the same
    KR20160002304A|2016-01-07|Apparatus and method for deciding traffic offloading in wireless communication systems
    BR112020020888A2|2021-02-23|communication method, communications device, communication system, and computer-readable storage media
    EP2989822B1|2018-05-09|Reducing location update signaling between network nodes of a mobile communication network
    CN113994744A|2022-01-28|Core paging processing
    JP2020120228A|2020-08-06|UE, control device, and communication control method
    EP3911017A1|2021-11-17|Ue, core network device, and communication control method
    JP2020088452A|2020-06-04|UE, control device, and communication control method
    JP2020088454A|2020-06-04|UE, control device, and communication control method
    BR112013003395A2|2020-08-04|method for providing network access for user equipment, public mobile network and user equipment
    同族专利:
    公开号 | 公开日
    RU2018100407A3|2019-02-20|
    AU2015236722A1|2016-08-25|
    WO2015148013A1|2015-10-01|
    EP3123675A1|2017-02-01|
    AU2015236722A8|2016-09-08|
    JP2017509235A|2017-03-30|
    US20150271708A1|2015-09-24|
    JP6526874B2|2019-06-05|
    RU2643449C1|2018-02-01|
    JP6343018B2|2018-06-13|
    RU2682390C2|2019-03-19|
    RU2018100407A|2019-02-20|
    KR20180031821A|2018-03-28|
    KR101842820B1|2018-03-27|
    KR20160113653A|2016-09-30|
    MX361418B|2018-11-29|
    KR102130904B1|2020-07-07|
    AU2015236722B2|2018-04-12|
    CA2939107C|2019-08-27|
    AU2018203437A1|2018-06-07|
    EP3123675A4|2017-09-06|
    US20180152980A1|2018-05-31|
    US9980299B2|2018-05-22|
    MX2016010888A|2016-10-26|
    AU2018203437B2|2020-05-21|
    CA2939107A1|2015-10-01|
    JP2018164267A|2018-10-18|
    引用文献:
    公开号 | 申请日 | 公开日 | 申请人 | 专利标题
    FI116958B|2003-07-01|2006-04-13|Nokia Corp|Determination of management nodes in a device management system|
    RU2419250C2|2006-08-21|2011-05-20|Телефонактиеболагет Лм Эрикссон |Selective control of user equipment capabilities|
    EP2104992A1|2006-10-05|2009-09-30|Hewlett-Packard Development Company, L.P.|Application management objects and wimax management objects for mobile device management|
    GB201010821D0|2010-06-28|2011-03-30|Nokia Oyj|Mehtod and apparatus for communicating via a gateway|
    US9565117B2|2010-12-22|2017-02-07|Cisco Technology, Inc.|Adaptive intelligent routing in a communication system|
    US8774211B2|2010-12-28|2014-07-08|Cellco Partnership|Autonomous network access congestion and collision control|
    KR101417256B1|2011-04-05|2014-07-08|엘지전자 주식회사|Method for transmitting data and a user eqipment|
    WO2012170185A1|2011-05-20|2012-12-13|Apple Inc.|Apparatus and methods for optimizing scheduled operations in hybrid network environments|
    US9655007B2|2011-06-28|2017-05-16|Interdigital Patent Holdings, Inc.|Managing data mobility policies|
    US8938233B2|2011-08-16|2015-01-20|Mediatek Inc.|Enhanced access control in LTE advanced systems|
    CN102333343A|2011-11-02|2012-01-25|电信科学技术研究院|Congestion information notification method and equipment|
    WO2013116856A1|2012-02-02|2013-08-08|Seven Networks, Inc.|Dynamic categorization of applications for network access in a mobile network|
    US20130227385A1|2012-02-23|2013-08-29|Jacob Allen|Method of allowing a word processing program to be used only with an embedded document|
    US9237557B2|2012-07-06|2016-01-12|Lg Electronics Inc.|Method and apparatus for service access barring|
    JP6055218B2|2012-07-19|2016-12-27|株式会社Ｎｔｔドコモ|Mobile communication system, network device, mobile station, and mobile communication method|
    US9585054B2|2012-07-19|2017-02-28|Interdigital Patent Holdings, Inc.|Method and apparatus for detecting and managing user plane congestion|
    US9526022B2|2012-08-03|2016-12-20|Intel Corporation|Establishing operating system and application-based routing policies in multi-mode user equipment|
    US20140133293A1|2012-11-15|2014-05-15|Seven Networks, Inc.|Triggering congestion control in a manner such that the mobile device radio is application aware|
    US20140136709A1|2012-11-15|2014-05-15|Research In Motion Limited|System and Method for Resource Management in a Wireless Network|
    WO2014158206A1|2013-03-29|2014-10-02|Intel Corp|Hybrid beamforming for data transmission|
    KR20160047572A|2013-08-30|2016-05-02|인터디지탈 패튼 홀딩스, 인크|Methods for application specific access control|
    WO2015038563A1|2013-09-10|2015-03-19|Silver Spring Networks, Inc.|Mesh network nodes configured to alleviate congestion in cellular network|US20160065480A1|2014-09-03|2016-03-03|Qualcomm Incorporated|Controlling application traffic|
    US10972960B2|2014-11-10|2021-04-06|Lg Electronics Inc.|Method and user equipment for blocking network access by ACDC|
    US9860824B2|2014-11-10|2018-01-02|Lg Electronics Inc.|Method and user equipment for blocking network access by ACDC|
    EP3248341B1|2015-01-22|2021-11-24|Apple Inc.|Application specific congestion control for data communications|
    US9713046B2|2015-01-28|2017-07-18|Mediatek Inc.|RAN assistance parameter reporting for LTE-WLAN interworking control and management|
    CN107637137B|2015-05-22|2021-11-09|三星电子株式会社|Terminal and base station and communication method thereof|
    US20160353356A1|2015-06-01|2016-12-01|Qualcomm Incorporated|Application-specific congestion control for data communicationin connected mode|
    US10103955B2|2015-10-01|2018-10-16|Oracle International Corporation|Methods, systems, and computer readable media for transmitting diameter peer status information|
    US10110421B2|2015-10-29|2018-10-23|Oracle International Corporation|Methods, systems, and computer readable media for using link aggregation groupstatus information|
    US20170324574A1|2016-05-03|2017-11-09|Mediatek Inc.|Method of Enhanced Application Specific Congestion Control for Data Communication Mechanism|
    EP3448112B1|2016-05-13|2020-04-22|Huawei Technologies Co., Ltd.|Service data stream transmission method and device|
    US10149143B2|2016-08-30|2018-12-04|Oracle International Corporation|Methods, systems, and computer readable media for realm-based routing of diameter request messages|
    WO2018086059A1|2016-11-11|2018-05-17|Qualcomm Incorporated|Access control in connected mode, idle mode, and inactive state|
    US10506082B2|2017-03-09|2019-12-10|Fortinet, Inc.|High availabilityinternet protocol securityvirtual private networkclient|
    US10257838B2|2017-05-19|2019-04-09|At&T Intellectual Property I, L.P.|Standardized commands for coverage modes in a wireless communications system|
    WO2020164745A1|2019-02-15|2020-08-20|LenovoPte. Ltd.|Deriving an operating system identity|
    JP2021012266A|2019-07-05|2021-02-04|信越化学工業株式会社|Composition for forming organic film, substrate for manufacturing semiconductor device, method for forming organic film, patterning method, and polymer|
    WO2021250726A1|2020-06-08|2021-12-16|日本電信電話株式会社|Separation system, separation method, and separation program|
    法律状态:
    2020-11-10| B06U| Preliminary requirement: requests with searches performed by other patent offices: procedure suspended [chapter 6.21 patent gazette]|
    2020-11-10| B15K| Others concerning applications: alteration of classification|Free format text: AS CLASSIFICACOES ANTERIORES ERAM: H04L 12/801 , H04L 29/08 Ipc: H04W 4/50 (2018.01), H04W 28/08 (2009.01), H04W 76 |
    2021-11-09| B25A| Requested transfer of rights approved|Owner name: INTEL CORPORATION (US) |
    2021-12-07| B350| Update of information on the portal [chapter 15.35 patent gazette]|
    优先权:
    申请号 | 申请日 | 专利标题
    US201461969778P| true| 2014-03-24|2014-03-24|
    US61/969,778|2014-03-24|
    US14/582,382|US9980299B2|2014-03-24|2014-12-24|Use of an OMA management object to support application-specific congestion control in mobile networks|
    US14/582,382|2014-12-24|
    PCT/US2015/016327|WO2015148013A1|2014-03-24|2015-02-18|Use of an oma management object to support application-specific congestion control in mobile networks|
    [返回顶部]