Selection of a serving node in a wireless communication system

Selection of Service Node in Wireless Communication System

SELECTION OF A SERVING NODE IN A WIRELESS COMMUNICATION SYSTEM

<b>[Cross-reference of related applications]</b>

This patent application claims to enjoy provisional application No. 62/065,514 filed with the U.S. Patent and Trademark Office on October 17, 2014, and non-provisional application No. 14/659,435 filed with the U.S. Patent and Trademark Office on March 16, 2015. The priority and interests of the company, all of their contents are incorporated into this article by reference.

In a nutshell, the content of this case is about communication systems, and more specifically, about the selection of service nodes in wireless communication systems.

Wireless communication systems are widely deployed to provide various telecommunication services such as telephone, video, data, messaging, and broadcasting. This type of wireless technology has gone through many stages of improvement to various telecommunication standards, each of which provides protocols that enable various wireless devices to communicate on a city, country, regional, and global level. Such wireless communication systems may include various components, such as user equipment (UE), radio access network (RAN) nodes, and service nodes. An example of an existing telecommunications standard is Long Term Evolution (LTE), which is also known as Evolutionary Packet System (EPS). In LTE , The RAN node may be an evolved node B (eNB), and the serving node may be a mobility management entity (MME).

In an existing communication system (e.g., LTE), the selection of a serving node (e.g., MME) can be performed partly based on load balancing. Load balancing can avoid a disproportionate overload of one service node relative to another service node. However, existing communication systems may not best accommodate the complexity introduced by device types and/or services operable at various UEs. Therefore, existing communication systems can benefit from features that better accommodate such complexity and provide further enhancements to the overall user experience.

The following provides a brief summary of one or more aspects of the content of the case in order to provide a basic understanding of such aspects. This summary is not a general comment on all the expected features of the content of the case, nor is it intended to identify the key or important elements of all aspects of the content of the case, or to illustrate the scope of protection of any or all aspects of the content of the case. Its sole purpose is to introduce some concepts of one or more aspects of the content of this case in a brief form, as a prelude to the more detailed description provided later.

In one aspect, the content of this case provides a wireless communication method operable at the user equipment (UE). The method may include sending a connection request message configured to request an initial connection with a radio access network (RAN) node, and the connection request message may include information configured to indicate a service profile of the UE. Some aspects of the content of this case provide a UE configured for wireless communication. The UE may include a transceiver, a memory, and at least one processor communicatively coupled to the transceiver and the memory. At least A processor may be configured to use the transceiver to send a connection request message, the connection request message being configured to request an initial connection with a RAN node, and the connection request message may include information configured to indicate the service profile of the UE. News. Some aspects of the content of this case provide a computer-readable medium that includes computer-executable code. The computer executable code may be configured to send a connection request message configured to request an initial connection with a RAN node, and the connection request message may include information configured to indicate a service profile of the UE. Some aspects of the content of this case provide a UE configured for wireless communication. The UE may include a unit for sending a connection request message configured to request an initial connection with a RAN node, and the connection request message includes information configured to indicate a service profile of the UE.

In another aspect, the content of this case provides a wireless communication method operable at the RAN node. The method may include receiving a connection request message from a UE, and the connection request message may include information configured to indicate a service profile of the UE. The method may also include selecting a serving node for the UE based at least in part on the service profile of the UE. The method may also include forwarding the connection request message to the selected service node. Some aspects of the content of this case provide a RAN node configured for wireless communication. The RAN node may include a transceiver, a memory, and at least one processor communicatively coupled to the transceiver and the memory. The at least one processor may be configured to use the transceiver to receive a connection request message from a UE, and the connection request message may include information configured to indicate a service profile of the UE. The at least one processor may also be configured to perform data based at least in part on the service profile of the UE Select a serving node for the UE. The at least one processor may also be configured to use the transceiver to forward the connection request message to the selected service node. Some aspects of the content of this case provide a computer-readable medium that includes computer-executable code. The computer executable code may be configured to receive a connection request message from a UE, and the connection request message may include information configured to indicate a service profile of the UE. The computer executable code may also be configured to select a serving node for the UE based at least in part on the service profile of the UE. The computer executable code can also be configured to forward the connection request message to the selected service node. Some aspects of the content of this case provide a RAN node configured for wireless communication. The RAN node may include a unit for receiving a connection request message from a UE, and the connection request message may include information configured to indicate a service profile of the UE. The RAN node may also include means for selecting a serving node for the UE based at least in part on the service profile of the UE. The RAN node may also include a unit for forwarding the connection request message to the selected serving node.

In another aspect, the content of this case provides a wireless communication method operable at the service node. The method may include receiving a connection request message from a RAN node, and the connection request message may be configured to establish communication with the UE and may include a service profile corresponding to the UE. The method may also include determining an identifier for the UE, and the identifier may be a function of the service profile corresponding to the UE. The method may also include sending a connection acceptance message to the RAN node, and the connection acceptance message may include the identifier for the UE. Some aspects of the content of this case provide a service node configured for wireless communication. The service node can include transceiver, memory , And at least one processor communicatively coupled to the transceiver and the memory. The at least one processor may be configured to use the transceiver to receive a connection request message from a RAN node, and the connection request message may be configured to establish communication with the UE and may include a service profile corresponding to the UE. The at least one processor may also be configured to determine an identifier for the UE, and the identifier may be a function of the service profile corresponding to the UE. The at least one processor may also be configured to use the transceiver to send a connection acceptance message to the RAN node, and the connection acceptance message may include the identifier for the UE. Some aspects of the content of this case provide a computer-readable medium that includes computer-executable code. The computer executable code may be configured to receive a connection request message from the RAN node, and the connection request message may be configured to establish communication with the UE and may include a service profile corresponding to the UE. The computer executable code may also be configured to determine an identifier for the UE, and the identifier may be a function of the service profile corresponding to the UE. The computer executable code may be configured to send a connection acceptance message to the RAN node, and the connection acceptance message may include the identifier for the UE. Some aspects of the content of this case provide a service node configured for wireless communication. The serving node may include a unit for receiving a connection request message from the RAN node, and the connection request message may be configured to establish communication with the UE and may include a service profile corresponding to the UE. The serving node may also include a unit for determining an identifier for the UE, and the identifier may be a function of the service profile corresponding to the UE. The serving node may also include a unit for sending a connection acceptance message to the RAN node, and the connection acceptance message may include the identifier for the UE.

These and other aspects of the present invention will be more fully understood after reviewing the following detailed description. For those with ordinary knowledge in the field to which the present invention belongs, after reviewing the following specific and exemplary embodiments of the content of the case in conjunction with the accompanying drawings, other aspects, features and embodiments of the content of the case will become apparent. Although the features of the content of the present case may be discussed with respect to the following specific embodiments and drawings, all embodiments of the content of the present case may include one or more of the advantageous features discussed herein. In other words, although one or more embodiments may be discussed as having specific advantageous features, one or more of such features may also be used in accordance with the various embodiments of the present content discussed herein. By analogy, although exemplary embodiments may be discussed below as device, system, or method embodiments, it should be understood that various devices, systems, and methods may be used to implement such exemplary embodiments.

<p>100Evolved Packet System (EPS)</p><p>102User Equipment (UE)</p><p>104Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)</p><p>106RAN node</p><p>108RAN node</p><p>110Evolved Packet Core (EPC)</p><p>112Service Node</p><p>114Service Node</p><p>116Service Gateway (SGW)</p><p>118Packet Data Network (PDN) Gateway</p><p>120Home User Server (HSS)</p><p>122IP service of service provider</p><p>200Access to the Internet</p><p>202Honeycomb area (cell)</p><p>206Lower power level RAN node</p><p>210Honeycomb area</p><p>300Figure</p><p>302DL-RS includes cell specific RS (CRS)</p><p>304UE Specific RS (UE-RS)</p><p>400Figure</p><p>410aResource block</p><p>410bResource block</p><p>420aResource block</p><p>420bResource block</p><p>430Physical Random Access Channel (PRACH)</p><p>500Figure</p><p>506Physical layer</p><p>508Floor 2 (L2 Floor)</p><p>510Media Access Control (MAC) sublayer</p><p>512Radio Link Control (RLC) sublayer</p><p>514Packet Data Convergence Protocol (PDCP) sublayer</p><p>516Radio Resource Control (RRC) sublayer</p><p>616Transmit (TX) Processor</p><p>618Transmitter TX</p><p>620antenna</p><p>652antenna</p><p>654Receiver RX</p><p>656receive (RX) processor</p><p>658Channel Estimator</p><p>659controller/processor</p><p>660Memory</p><p>662Data Slot</p><p>667Data source</p><p>668TX processor</p><p>670RX processor</p><p>674Channel Estimator</p><p>675controller/processor</p><p>676Memory</p><p>702Switch</p><p>704TA update</p><p>706Cell reselection</p><p>800Network Architecture</p><p>802Core Network A</p><p>804Core Network B</p><p>806Core Network C</p><p>814Service Node</p><p>816Service Node</p><p>820RAN</p><p>Figure 900</p><p>902S1 establishment request</p><p>904S1 establishment response</p><p>1000Figure</p><p>1002Attach request</p><p>1004Block</p><p>1006Attach request</p><p>1008Attach and accept c</p><p>1010Attach and accept</p><p>Figure 1100</p><p>1106Service or TAI request</p><p>1108Context request</p><p>1110Context response</p><p>1112Service Node</p><p>1114Service or TAU response acceptance</p><p>1116Service or TAI response acceptance</p><p>1200Figure</p><p>1202Step</p><p>1204Step</p><p>1206Step</p><p>1208Step</p><p>1210Step</p><p>Figure 1300</p><p>1302Step</p><p>1304Step</p><p>1306Step</p><p>1308Step</p><p>1310Step</p><p>Figure 1400</p><p>1402Step</p><p>1404Step</p><p>1406Step</p><p>1408Step</p><p>1410Step</p><p>1412Step</p><p>1414Step</p><p>1416Step</p><p>1418Step</p><p>Figure 1500</p><p>1502Step</p><p>1504Step</p><p>1506Step</p><p>1508Step</p><p>1510Step</p><p>1512Step</p><p>1514Step</p><p>1516Step</p><p>1518Step</p><p>1600UE</p><p>1601Processing system</p><p>1603Bus</p><p>1604Processor</p><p>1606Computer readable media</p><p>1608Bus Interface</p><p>1610Transceiver</p><p>1612User Interface</p><p>1614Memory</p><p>1620Receiving circuit</p><p>1621Control circuit</p><p>1622Transmission circuit</p><p>1623Other circuits</p><p>1630Service profile information</p><p>1632Other storage modules</p><p>1640Receive command</p><p>1641Control command</p><p>1642Transmission command</p><p>1643Transmission command</p><p>1700RAN node</p><p>1701Processing system</p><p>1703Bus Interface</p><p>1704Processor</p><p>1706Computer readable media</p><p>1708Bus Interface</p><p>1710Transceiver</p><p>1714Memory</p><p>1720Receiving circuit</p><p>1721Control circuit</p><p>1722Transmission circuit</p><p>1723Other circuits</p><p>1730Service Profile Information</p><p>1740Receive command</p><p>1741Control command</p><p>1742Transmission command</p><p>1743Other commands</p><p>1800Service Node</p><p>1801Processing system</p><p>1803Bus</p><p>1804Processor</p><p>1806Computer readable media</p><p>1808Bus Interface</p><p>1810Transceiver</p><p>1814Memory</p><p>1820Receiving circuit</p><p>1821Control circuit</p><p>1822Transmission circuit</p><p>1823Other circuits</p><p>1830Service Profile Information</p><p>1832Other storage modules</p><p>1840Receive command</p><p>1841Control command</p><p>1842Transmission command</p><p>1843Other commands</p>

FIG. 1 is a diagram illustrating an example of a network architecture for an Evolutionary Packet System (EPS) according to some embodiments of the content of this case.

Fig. 2 is a diagram illustrating an example of an access network according to some embodiments of the content of the present case.

FIG. 3 is a diagram illustrating an example of a downlink (DL) frame structure in an EPS network according to some embodiments of the content of this case.

FIG. 4 is a diagram illustrating an example of an uplink (UL) frame structure in an EPS network according to some embodiments of the content of this case.

FIG. 5 is a diagram illustrating an example of a wireless protocol architecture for a user plane and a control plane according to some embodiments of the content of this case.

Figure 6 is a diagram illustrating a wireless storage system according to some embodiments of the content of this case. Take a diagram of examples of network (RAN) nodes and user equipment (UE).

FIG. 7 is a diagram illustrating an example of a network topology structure for an EPS network according to some embodiments of the content of this case.

FIG. 8 is a diagram illustrating an example of a network architecture according to some embodiments of the content of this case.

FIG. 9 is a diagram illustrating an example of communication establishment between a RAN node and a service node according to some embodiments of the content of this case.

FIG. 10 is a diagram illustrating an example of the establishment of communication between the UE and various components of the network according to some embodiments of the content of the present case.

FIG. 11 is a diagram illustrating an example of service node reselection according to some embodiments of the content of this case.

FIG. 12 is a diagram illustrating examples of various methods and/or procedures operable at the UE.

FIG. 13 is a diagram illustrating another example of various methods and/or procedures operable at the UE.

FIG. 14 is a diagram illustrating examples of various methods and/or procedures operable at the RAN node.

FIG. 15 is a diagram illustrating examples of various methods and/or procedures operable at a service node.

FIG. 16 is a diagram illustrating an example of a hardware implementation of a UE including a processing system.

FIG. 17 is a diagram illustrating an example of a hardware implementation of a RAN node including a processing system.

Figure 18 illustrates the hardware implementation of the service node including the processing system Diagram of an example of the way.

The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations, and is not intended to represent the only configuration in which the concepts described herein can be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, for those with ordinary knowledge in the field to which the present invention belongs, it will be obvious that these concepts can also be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring such concepts. In order to provide various non-limiting examples to illustrate some aspects of the content of this case, the following description may describe some features and embodiments in the context of the long-term evolution (LTE) architecture, because the following description may be based on the third-generation partner plan. Draw (3GPP) to define. However, any LTE-specific terms or entities are only provided as non-limiting examples, and some aspects of the content of this case can be implemented in any appropriate network or technology.

FIG. 1 is a diagram illustrating an example of a network architecture for an Evolutionary Packet System (EPS) 100 according to some embodiments of the content of this case. The network architecture of EPS 100 can be an LTE network architecture or any other network architecture that does not deviate from the protection scope of the content of this case. EPS 100 may include one or more user equipment (UE) 102, evolved universal mobile telecommunications system (UMTS) terrestrial radio access network (E-UTRAN) 104, evolved packet core (EPC) 110, home user server Server (HSS) 120 and the IP service 122 of the service provider. EPS 100 can be interconnected with other access networks (not shown). EPS 100 provides packet switching services; however, those with general knowledge in the field of the present invention It will be easy to realize that the various concepts introduced throughout the content of this case can be extended to the network that provides circuit-switched services.

The E-UTRAN 104 may include a radio access network (RAN) node 106. A non-limiting example of the RAN node 106 is an evolved Node B (eNB). The E-UTRAN 104 may also include other RAN nodes 108 (for example, other eNBs). The RAN node 106 provides the UE 102 with user plane and control plane agreement termination. The RAN node 106 can be connected to other eNBs 108 via the X2 interface (ie, backload). The RAN node 106 may also be called a base station, a base station transceiver, a radio base station, a radio transceiver, a transceiver functional unit, a basic service set (BSS), an extended service set (ESS), or some other appropriate terminology. The RAN node 106 provides the UE 102 with an access point to the EPC 110. Examples of UE 102 include cellular phones, smart phones, tablets, dialog initiation protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video equipment, digital Audio players (for example, MP3 players), cameras, game consoles, household appliances (for example, washing machines) or any other devices with similar functions. UE 102 can also be referred to as mobile station, user station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile user by those with ordinary knowledge in the field of the present invention. Station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile service client, client, or some other appropriate term.

The RAN node 106 is connected to the EPC 110 via the S1 interface. The EPC 110 may include a service gateway (SGW) 116 and a packet data network (PDN) gateway 118. The EPC 110 also includes a service node 112. Non-limiting of service node 112 An example is the Mobility Management Entity (MME) 112. The EPC 110 may also include various other service nodes 114 (for example, other MMEs). The serving node (SN) 112 may be a control node that handles signal transfer between the UE 102 and the EPC 110. Generally, the service node 112 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the SGW 116, which itself is connected to the packet data network (PDN) gateway 118. The PDN gateway 118 provides UE IP address allocation and other functions. The PDN gateway 118 is connected to the IP service 122 of the service provider. The IP service 122 of the service provider includes the Internet, intranet, IP Multimedia Subsystem (IMS), and Packet Switched Streaming Service (PSS).

In EPS 100, service node 112 supports multiple functions and interfaces, including: non-access layer (NAS) signal transmission and security; access layer (AS) security control; tracking area list management; PDN gateway 118 and SGW 116 Selection; service node (e.g., MME) selection for handover between service nodes (e.g., inter-MME); inter-core network node signal transmission for mobility between 3GPP access networks; roaming and authentication; and EPS bearer management. The details of these functions and interfaces can be found in the 3GPP technical specifications numbered 23.401, 23.402, and 23.002, which are incorporated herein by reference. The serving node 112 generally manages which services are active and the mobility of the UE. In other words, the serving node 112 manages how to connect to the UE. When a UE is connected, the serving node 112 knows which RAN node the UE is connected to. When the UE is idle, the serving node 112 lists the RAN nodes that want to page the UE.

FIG. 2 is a diagram illustrating an example of the access network 200 in the LTE network architecture. In this example, the access network 200 is divided into a plurality of honeycomb areas (cells) 202. One or more lower power level RAN nodes 206 may have A honeycomb area 210 where one or more of the cells 202 overlap. The lower power class RAN node 206 may be a femto cell (e.g., a home eNB (HeNB)), a pico cell, a micro cell, or a remote radio head (RRH). The macro RAN nodes 106 are each assigned to the corresponding cell 202 and configured as an access point for all UEs 102 in the cell 202 to provide to the EPC 110. There is no centralized controller in this example of the access network 200, but a centralized controller can be used in an alternative configuration. The RAN node 106 is responsible for all wireless-related functions, including: radio bearer control, admission control, mobility control, scheduling, security, and connectivity to the SGW 116. The RAN node may support one or more (for example, three) cells (also referred to as sectors). The term "cell" can represent the smallest coverage area of a RAN node and/or a RAN node subsystem serving a specific coverage area. In addition, without departing from the scope of protection of the content of this case, the terms "RAN node", "eNB", "base station" and/or "cell" may be used interchangeably in this article.

The modulation and multiplexing access scheme adopted by the access network 200 may vary according to the specific telecommunication standard being deployed. In LTE applications, orthogonal frequency division multiplexing (OFDM) is used on the downlink (DL) and single carrier frequency division multiple access (SC-FDMA) is used on the uplink (UL) to support frequency division Both duplex (FDD) and time division duplex (TDD). As those with ordinary knowledge in the field of the present invention will easily realize from the following detailed description, the various concepts introduced in this article are well suited for LTE applications. However, these concepts can be easily extended to other telecommunication standards that use other modulation and multiple access technologies. By way of example, these concepts can be extended to Evolutionary Data Optimization (EV-DO) or Ultra Mobile Broadband (UMB). EV-DO and UMB are the third generation Partner Project 2 (3GPP2) is an air interface standard that is part of the CDMA2000 series of standards and uses CDMA to provide broadband Internet access to mobile stations. These concepts can also be extended to Universal Terrestrial Radio Access (UTRA) using Wideband-CDMA (W-CDMA) and other variants of CDMA such as TD-SCDMA; Global System for Mobile Communications (GSM) using TDMA; and evolution Type UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20 and flash OFDM using OFDMA. UTRA, E-UTRA, UMTS, LTE and GSM are described in documents from the 3GPP organization. CDMA2000 and UMB are described in documents from the 3GPP2 organization. The actual wireless communication standard and multiple access technology used will depend on the specific application and the overall design constraints imposed on the system.

The RAN node 106 may have multiple antennas supporting multiple input multiple output (MIMO) technology. The use of MIMO technology enables the RAN node 106 to use the spatial domain to support spatial multiplexing, beamforming, and transmit diversity. Spatial multiplexing can be used to send different data streams on the same frequency at the same time. The data stream can be sent to a single UE 102 to increase the data rate, or the data stream can be sent to multiple UEs 102 to increase the overall system capacity. This is achieved by spatially precoding each data stream (ie applying scaling of amplitude and phase) and then transmitting each spatially precoded stream on the DL via multiple transmit antennas. The spatially precoded data streams arrive at the UE 102 with different spatial signatures, which enables each of the UEs 102 to recover one or more data streams destined for the UE 102. On the UL, each UE 102 transmits a spatially precoded data stream, which enables the RAN node 106 to identify the source of each spatially precoded data stream.

Space multiplexing is usually used when the channel is in good condition. When the channel conditions are less favorable, beamforming can be used to focus the transmission energy in one or more directions. This can be achieved by spatially precoding the data for transmission via multiple antennas. To achieve good coverage at the edges of the cells, may be in conjunction with transmit diversity using beamformed transmit a single stream.

In the following detailed description, some aspects of the access network will be described with reference to the MIMO system supporting OFDM on the DL. OFDM is a spread spectrum technology in which data is modulated on multiple sub-carriers within an OFDM symbol. The sub-carriers are separated by precise frequencies. The spacing provides the "orthogonality" that enables the receiver to recover data from the subcarrier. In the time domain, a guard interval (e.g., cyclic prefix) can be added to each OFDM symbol to combat inter-OFDM symbol interference. UL can use SC-FDMA in the form of a discrete Fourier transform (DFT) extended OFDM signal to compensate for the peak-to-average power ratio (PAPR).

FIG. 3 is a diagram 300 illustrating an example of a DL frame structure in LTE. A frame (10 milliseconds) can be divided into 10 sub-frames of equal size. Each sub-frame can include two consecutive time slots. The resource grid can be used to represent two time slots, and each time slot includes a resource block. The resource grid is divided into multiple resource elements. In LTE, for a general cyclic prefix, a resource block includes 12 consecutive subcarriers in the frequency domain and 7 consecutive OFDM symbols in the time domain, or a total of 84 resource elements. For the extended cyclic prefix, the resource block contains 12 consecutive subcarriers in the frequency domain and 6 consecutive OFDM symbols in the time domain, or 72 resource elements in total. Some of the resource elements marked as R 302, 304 include DL reference signals (DL-RS). DL-RS includes cell-specific RS (CRS) (sometimes called public RS) 302 and UE-specific RS (UE-RS) 304. The UE-RS 304 is sent only on the resource block on which the corresponding entity DL shared channel (PDSCH) is mapped. The number of bits carried by each resource element depends on the modulation scheme. Therefore, the more resource blocks the UE receives and the higher the modulation scheme, the higher the data rate for the UE.

FIG. 4 is a diagram 400 illustrating an example of a UL frame structure in LTE. The available resource block for UL can be divided into a data part and a control part. The control part can be formed at the two edges of the system bandwidth and can have a configurable size. The resource blocks in the control part can be assigned to the UE for transmission of control information. The data part may include all resource blocks that are not included in the control part. The UL frame structure allows the data part to include consecutive sub-carriers, which may allow all consecutive sub-carriers in the consecutive sub-carriers in the data part to be assigned to a single UE.

The resource blocks 410a, 410b in the control part can be assigned to the UE to send control information to the RAN node. The resource blocks 420a and 420b in the data part can also be assigned to the UE to send data to the RAN node. The UE can send control information in the physical UL control channel (PUCCH) on the assigned resource block in the control part. The UE may send only data or both data and control information in the physical UL shared channel (PUSCH) on the assigned resource block in the data part. UL transmission can span two time slots of subframes and can hop across frequencies.

A collection of resource blocks can be used to perform initial system access and achieve UL synchronization in a physical random access channel (PRACH) 430. PRACH 430 carries a random sequence and cannot carry any UL data/signal transmission. Each The random access preamble signal occupies the bandwidth corresponding to 6 consecutive resource blocks. The starting frequency is specified by the network. In other words, the transmission of random access preamble signals is limited to specific time and frequency resources. There is no frequency hopping for PRACH. The PRACH attempt is carried in a single subframe (1 millisecond) or a sequence of a few consecutive subframes, and the UE can only perform a single PRACH attempt for each frame (10 milliseconds).

FIG. 5 is a diagram 500 illustrating an example of a radio protocol architecture for the user plane and the control plane in LTE. The radio agreement architecture for UE and RAN nodes is shown as having three layers: layer 1, layer 2, and layer 3. Layer 1 (L1 layer) is the lowest layer and implements various physical layer signal processing functions. The L1 layer will be referred to as the physical layer 506 herein. Layer 2 (L2 layer) 508 is located above the physical layer 506, and is responsible for the link between the UE and the RAN node on the physical layer 506.

In the user plane, the L2 layer 508 includes: a medium access control (MAC) sublayer 510, a radio link control (RLC) sublayer 512, and a packetized data convergence protocol (PDCP) 514 sublayer. These sublayers terminate in the network At the RAN node on the roadside. Although not shown, the UE may have several upper layers above the L2 layer 508, including the network layer (for example, the IP layer) that terminates at the PDN gateway 118 on the network side, and the other end of the connection (for example, , Remote UE, server, etc.) application layer.

The PDCP sublayer 514 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 504 also provides header compression for upper-layer data packets to reduce the burden of radio transmission management, provides security by encrypting the data packets, and provides handover support between RAN nodes for the UE. The RLC sublayer 512 provides segmentation and reassembly of upper-layer data packets, and reconfiguration of lost data packets. Transmission and reordering of data packets to compensate for out-of-order reception caused by hybrid automatic repeat request (HARQ). The MAC sublayer 510 provides multiplexing between logical channels and transmission channels. The MAC sublayer 510 is also responsible for allocating various radio resources (for example, resource blocks) in a cell among the UE. The MAC sublayer 510 is also responsible for HARQ operations.

In the control plane, for the physical layer 506 and the L2 layer 508, except that there is no header compression function for the control plane, the radio protocol architecture for the UE and the RAN node is essentially the same. The control plane also includes a radio resource control (RRC) sublayer 516 in layer 3 (L3 layer). The RRC sublayer is responsible for obtaining radio resources (for example, radio bearers) and using RRC signal transfer between the RAN node and the UE to configure the bottom layer.

FIG. 6 is a block diagram of the communication between the RAN node 106 and the UE 102 in the access network. In the DL, the upper layer packets from the core network are provided to the controller/processor 675. The controller/processor 675 implements the functions of the L2 layer. In the DL, the controller/processor 675 provides: header compression, encryption, packet segmentation and reordering, multiplexing between logical channels and transmission channels, and radio resource configuration for UE 102 based on various priority order metrics. The controller/processor 675 is also responsible for HARQ operations, retransmission of lost packets, and sending signals to the UE 102.

The transmission (TX) processor 616 implements various signal processing functions for the L1 layer (that is, the physical layer). These signal processing functions include encoding and interleaving to facilitate forward error correction (FEC) at the UE 102, and based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying ( QPSK), M-Phase Shift Keying (M-PSK), M-Quadrature Amplitude Modulation (M-QAM)) are mapped to signal clusters. The coded and modulated symbols are then split into Parallel streams. Each stream is then mapped to OFDM sub-carriers, multiplexed with reference signals (e.g. pilot frequencies) in the time domain and/or frequency domain, and then combined using inverse fast Fourier transform (IFFT) to generate the carrier The physical channel for the stream of time-domain OFDM symbols. The OFDM stream is spatially precoded to generate multiple spatial streams. The channel estimates from the channel estimator 674 can be used to determine coding and modulation schemes, as well as for spatial processing. The channel estimation can be derived from the reference signal and/or channel status feedback sent by the UE 102. Each spatial stream can then be provided to a different antenna 620 via a separate transmitter 618TX. Each transmitter 618TX can use the corresponding spatial stream to modulate the RF carrier for transmission.

At the UE 102, each receiver 654RX receives signals via its respective antenna 652. Each receiver 654RX recovers the information modulated on the RF carrier and provides the information to the receive (RX) processor 656. The RX processor 656 implements various signal processing functions of the L1 layer. The RX processor 656 can perform spatial processing on the information to recover any spatial stream to the UE 102. If multiple spatial streams are destined for the UE 102, they can be combined into a single OFDM symbol stream via the RX processor 656. The RX processor 656 then uses a Fast Fourier Transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal includes a separate stream of OFDM symbols for each subcarrier in the OFDM signal. The symbols and reference signals on each sub-carrier are recovered and demodulated by determining the most likely signal cluster point sent by the RAN node 106. These soft decisions may be based on channel estimates calculated by the channel estimator 658. These soft decisions are then decoded and de-interleaved to recover the data and control signals originally sent by the RAN node 106 on the physical channel. These data and control signals are subsequently Provided to the controller/processor 659.

The controller/processor 659 implements the L2 layer. The controller/processor may be associated with a memory 660 that stores program codes and data. The memory 660 may also be referred to as a computer readable medium. In UL, the controller/processor 659 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transmission channel and the logical channel to recover upper-layer packets from the core network. The upper layer packet is then provided to a data slot 662, which represents all protocol layers located above the L2 layer. Various control signals can also be provided to the data slot 662 for L3 processing. The controller/processor 659 is also responsible for using acknowledgement (ACK) and/or negative acknowledgement (NACK) protocols for error detection to support HARQ operations.

In UL, the data source 667 is used to provide upper layer packets to the controller/processor 659. The data source 667 represents all protocol layers located above the L2 layer. Similar to the functionality described in connection with the DL transmission performed by the RAN node 106, the controller/processor 659 provides header compression, encryption, packet segmentation and reordering, and based on the radio resource configuration performed by the RAN node 106. The multiplexing between the logic channel and the transmission channel realizes the L2 layer for the user plane and the control plane. The controller/processor 659 is also responsible for HARQ operations, retransmission of lost packets, and sending signals to the RAN node 106.

The TX processor 668 can use the channel estimation derived by the channel estimator 658 from the reference signal or feedback sent by the RAN node 106 to select an appropriate coding and modulation scheme, and to facilitate spatial processing. The spatial stream generated by the TX processor 668 can be provided to different antennas 652 via a separate transmitter 654TX. Each transmitter 654TX can use the corresponding spatial stream to modulate the RF carrier for transmission.

The UL transmission is processed at the RAN node 106 in a manner similar to that described in connection with the receiver function at the UE 102. Each receiver 618RX receives signals via its respective antenna 620. Each receiver 618RX recovers the information modulated on the RF carrier and provides the information to the RX processor 670. The RX processor 670 may implement the L1 layer.

The controller/processor 675 implements the L2 layer. The controller/processor 675 may be associated with a memory 676 that stores program codes and data. The memory 676 may also be referred to as a computer readable medium. In the UL, the controller/processor 675 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transmission channel and the logical channel to recover upper-layer packets from the UE 102. The upper layer packets from the controller/processor 675 can be provided to the core network. The controller/processor 675 is also responsible for error detection using ACK and/or NACK protocols to support HARQ operations.

Figure 7 illustrates the network topology of the EPS network. In particular, FIG. 7 illustrates some aspects of the mobile programs in the EPS network. The EPS network may include various cells, and these various cells may be served by various RAN nodes (for example, eNB). The EPS network may also include various service nodes (for example, MME). The EPS network can also include various SGWs, and these various SGWs can be grouped into one or more service areas. For example, the service area 1 may include SGW1 and SGW2 and a service node pool 1. The service node pool includes a service node 1 and a service node 2. The service area 2 may include SGW1 and SGW2 and a service node pool 2, which includes a service node 3 and a service node 4. Each service area may include one or more tracking areas (TA). For example, service area 1 may include tracking area 1, tracking area 2, and tracking area 3. Service area 2 can include Tracking area 4 and tracking area 5. Each tracking area may include one or more RAN nodes. The UE 102 may be in an active mode or an idle mode. When in the active mode, the UE 102 can perform the handover 702 as the UE 102. When in the idle mode, the UE 102 may perform cell reselection 706 and/or TA update 704. Those with ordinary knowledge in the field of the present invention will understand that the EPS network can include any number of tracking areas, cells, SGWs, service node pools, service nodes and /Or RAN node. For example, multiple service nodes may be included in the service area of the same service node pool. The service areas of each service node and/or MME may overlap with each other.

The UE 102 can roam without changing the serving node. The service area can be served by one or more service nodes in parallel. In the existing LTE and EPS networks, since additional functionality for the service node has been defined in successive versions, the service node has become more complex over time. In this type of network, load balancing and RAN are mainly used to perform service node selection. This type of service node pool and service node selection defined by network characteristics is based on the identifier of the device (for example, the globally unique temporary identifier (GUTI)).

FIG. 8 illustrates an exemplary network architecture 800 including UE 102, RAN node 106, and various service nodes 112, 814, and 816. As described in more detail above, a non-limiting example of the RAN node 106 is an eNB, and a non-limiting example of the serving nodes 112, 814, 816 are various MMEs. The UE 102 can perform various communications in a specific RAN 820. The UE 102 in the RAN 820 can communicate with the RAN node 106. The UE 102 can communicate with various other RAN nodes (for example, other RAN nodes) without departing from the scope of protection of the content of this case. Node 108) communicates. The RAN node 106 may communicate with one or more service nodes 112, 814, and 816. The service node may be part of the core network (CN). For example, the service node 112 may be part of the core network A 802, another service node 814 may be part of the core network B 804, and yet another service node 816 may be part of the core network C 806. Those with ordinary knowledge in the field of the present invention will understand that the network architecture 800 may include various other components not shown in FIG. 8 without departing from the scope of protection of the content of the case.

General initial connection establishment and service node selection

FIG. 9 is a diagram 900 illustrating the initial establishment of a communication interface between the RAN node 106 (e.g., eNB) and the serving node 112 (e.g., MME). The communication between the RAN node 106 and the service node 112 is realized via a signal transmission interface such as the S1-MME interface in the LTE standard. During the initial establishment of the communication interface between the RAN node 106 and the service node 112, the RAN node 106 may send an S1 setup request 902 to the service node 112. After receiving the S1 setup request 902, the service node 112 may send an S1 setup response 904 to the RAN node 106. During the initial setup, when the RAN node 106 and the service node 112 are connected to each other, such a signal transmission interface can be established. Generally speaking, the purpose of such a signal transmission interface setup procedure is to exchange application-level data required by the RAN node 106 and the service node 112 to correctly interact with each other on the signal transmission interface. Such a signal transmission interface setup program can erase some existing application-level configuration data in the RAN node 106 and the service node 112, and use the received application-level configuration data to replace the existing application-level configuration data. As part of the setup of the signal transfer interface, the RAN node 106 can be configured with There are relative capacity information elements (IE) for each service node in the pool. Therefore, the probability that the RAN node 106 selects a specific service node (for example, the service node 112) in the service node pool is proportional to its relative capacity. The relative capacity is usually set according to the capacity of a service node relative to other service nodes, and usually changes infrequently.

General UE connection establishment and service node selection

When the UE 102 arrives at the RAN node 106 and attempts to connect or attach to the RAN node 106, the UE 102 may send a connection request message configured to request establishment of a connection to the RAN node 106. This type of message may be referred to as an attachment request 1002. Such messages can be sent to the RAN node 106. If the UE 102 has already registered with the serving node 112 (for example, MME), the UE 102 provides the RAN node 106 with a globally unique temporary identifier (for example, GUTI). The identifier can provide unambiguous identification of the UE 102 and allow identification of the serving node 112 and the network. The network and the UE 102 can use such identifiers to establish the UE's identification code during the signal transmission between the UE 102 and the network. The identifier may include two components: a first component that uniquely identifies the serving node 112 to which the identifier is allocated, and a second component that uniquely identifies the UE within the serving node 112 to which the identifier is allocated.

The identifier may include a globally unique service node identifier (for example, when the service node 112 is an MME, it is a globally unique mobility management entity identifier (GUMMEI)) and a service node temporary mobile user identification code (for example, temporary mobile user identification code ( TMSI)). GUMMEI may include: mobile country code (MCC) that identifies the country where the mobile user lives, mobile network code (MNC), MME group ID (MMEGI), and MME code that identifies the mobile user's home public land mobile network (PLMN) (MMEC).

If the UE 102 has not registered with any serving node 112, the UE 102 does not serve as a registered serving node entity to provide information to be forwarded by the RAN node 106 to the serving node 112. At this stage, the RAN node 106 can perform serving node selection for the UE 102. As described in more detail above, the RAN node 106 selects the serving node 112 for the UE 102 based on the relative capacity IE. The load balancing function is performed based on the relative capacity of the service node. Load balancing guides UEs entering the service node pool to appropriate services in a way of realizing load balancing between service nodes.

In some existing networks, during the connection establishment signal transmission between the UE 102 and the RAN node 106 (for example, radio resource control (RRC) signal transmission), the UE 102 provides the RAN node 106 with a specific establishment reason IE. Among other things, the Establish Reason IE includes parameters that indicate what the connection will be used for, such as for emergency dialing, for access for mobile station termination, for signal transmission or data initiated by the mobile station, and so on. Therefore, the RAN node 106 can determine whether the UE 102 is configured for low access priority based on the information received in the transmission of the connection establishment signal, and can use this information for service node selection. However, this information still lacks indications about the UE 102 itself, such as the device type or the service operated at the UE 102, which can better improve the service node selection.

Once the RAN node 106 has selected the serving node 112, the RAN node 106 sends an initial UE message to the selected serving node 112. In other words, through the signal transfer interface (for example, the S1-MME interface), the RAN node 106 sends an initial UE message to send information corresponding to the UE's connection request message to the service node 112. The message can include: NAS message (for example, attached (The request message), the UE signal transfer reference ID, and other S1 (that is, the signal transfer interface) addressing information. The serving node 112 can use the identifier in the initial UE message to determine whether the serving node 112 has an existing UE context. The service node 112 starts to establish the UE context by storing UE network capacity information, packet data network (PDN) connectivity requests, etc., and then uses the UE network capacity information and packet data network during secure startup and bearer establishment. (PDN) Connectivity request, etc. The service node 112 responds to the RAN node 106 with the NAS attach accept message. The RAN node 106 may then transmit to the UE 102 a message with the NAS attach acceptance received from the serving node (unless this message is transmitted to the UE 102 in another way). When the UE 102 moves away from the service area of the selected serving node, the selected serving node indicates that the UE 102 performs serving node selection.

Enhanced initial connection establishment and service node selection

According to some aspects of the content of this case, the setup procedure for establishing a new signal transmission interface (for example, S1-MME connection) between the RAN 106 and the service node 112 can be modified or enhanced to include one or more additional information elements. For example, referring to FIG. 9, in some aspects of the content of this case, the S1 setup request from the RAN node 106 to the service node 112 may indicate that the RAN node 106 supports different technologies (for example, different RATs, different UE device types, and /Or different UE services, etc.), which may be useful to the serving node 112. For example, in response to a request for establishing a signal transfer interface, the service node 112 may provide the RAN node 106 with information related to the capacity of the service node, including but not limited to: a list of supported device types, a list of supported services, and an initial device identifier The prefix list and/or the radio access technology (RAT) list.

Table 1 below provides information such as may be included in the establishment of service node S1 Some non-limiting examples of such parameters in the response message.

<tables><img id="" he="1381" wi="1972" file="TWI640208B_D0001.tif" alt="" img-content="drawing" img-format="tif" orientation="portrait" inline="no" /></tables>Table 1 (above) lists some non-limiting examples of various parameters. In some aspects of the content of this case, one or more of these parameters may be sent from the service node 112 to the RAN node 106. The device type list may be an enumerated list of device types supported by the service node 112, and the service list may be an enumerated list of services supported by the service node 112.

Some non-limiting examples of services supported by the UE 102 include: data services, voice services, video services, Internet services, and any other appropriate services operable on the UE 102. The initial device identifier prefix list may be an enumerated list of device identifier prefixes supported by the service node 112. The RAN node 106 may select this serving node 112 for the device or the UE 102 that has the initial identifier appearing in this list. The RAT list may be an enumerated list of RATs supported by the service node 112 for access. In other words, the specific The service node 112 may not only serve different device types; in some aspects of the content of this case, different service nodes may also serve different RATs. For example, one service node may serve fifth-generation (5G) devices and fourth-generation (4G) devices, while another service node may only serve wireless local area network (WLAN) devices. Therefore, the RAT list provided by the serving node can assist in the selection of the serving node. In the S1 setup response 904, such parameters other than one or more other parameters corresponding to the service node 112 (for example, relative capacity IE) may be provided from the service node 112 to the RAN node 106. In this way, the RAN node 106 can store these parameters about the serving node 112 in its memory. Such parameters can be used for serving node selection when connecting with the UE 102.

In some aspects of the content of this case, the S1 setup response message 904 sent from the service node 112 to the RAN node 106 may include one or more device identifier prefixes supported by the service node 112. In other words, the UE 102 can implicitly indicate its device type via a part of its device identifier. Here, by storing a list of device identifier prefixes supported by the service node 112, the RAN node 106 can select this service node 112 for the UE indicating the identifier in such a list. In some other aspects of the content of this case, as a supplement or alternative to the S1 setup response message 904, an operation and maintenance (OAM) configuration message transfer can be used to provide the above-described service node 112 parameters to the RAN node 106. In other words, in some configurations of the content of this case, the parameters listed in Table 1 (above) may be included in one or both of the S1 setup response message 904 and/or OAM signal transmission.

Enhanced UE connection establishment

FIG. 10 is a diagram illustrating some aspects of the UE 102 according to the content of this case. Diagram 1000 of the initial connection establishment procedure with the EPS network. The UE 102 may select a core network from a plurality of core networks or virtualized core networks, for example, according to a network identifier such as PLMN-ID. Before attempting to attach to a specific RAN node 106, the UE 102 may initially decide which RAN node 106 it desires to attach to. According to some aspects of the content of this case, the UE 102 may be able to determine whether the RAN node 106 has a signal transmission interface (for example, an S1-MME interface) corresponding to a service node capable of supporting the equipment type and/or service corresponding to the UE 102. For example, the RAN node 106 may be configured to broadcast one or more messages indicating information related to the service node 112 associated with the RAN node 106. Here, these broadcasts can include information from Table 1 (above). For example, such information may include: a list of device types, a list of services, a list of initial device identifier prefixes, and/or a list of RATs. Therefore, the UE 102 can use such information (in addition to the existing mechanism for selecting the RAN node 106) to decide whether to attempt to attach the RAN node 106.

As another example, the UE 102 may be configured with a list of RAN nodes 106. The UE 102 can utilize an appropriate identifier for the RAN node 106. Non-limiting examples of such identifiers include PLMN-ID, tracking area function variable code, and/or cell ID, where support for the device type corresponding to UE 102 is available. Therefore, in some configurations, the UE 102 may be configured to try to attach a specific cell based on its RAN node 106 list. In some configurations, the device type of the UE 102 may be related to the service performed on the UE 102. For example, UE 102 may be a washing machine connected to the Internet. The washing machine can indicate that it is an Internet of everything (IOE) device, and the services it performs are related to the type of equipment (for example, washing machine-related services). close. However, in some other configurations, the device type of the UE may be independent of the service performed on the UE 102. In other words, a specific device type does not necessarily imply a specific service type. For example, UE 102 may be a tablet computer. A tablet computer can be connected to the Internet, but a tablet computer can perform a number of different services (for example, voice, Internet, data, video, etc.).

When the UE 102 attempts to attach to the RAN node 106, the UE 102 may send a connection request message. A non-limiting example of the connection request message is attach request 1002. However, according to some aspects of the content of this case, the attach request 1002 sent from the UE 102 to the RAN node 106 may include information that the RAN node 106 can use for serving node selection. For example, the attach request 1002 may include the device ID or other appropriate identifier of the UE, one or more device types corresponding to the UE 102, and one or more services that can be utilized by the UE 102. For example, the UE 102 may send an attach request 1002 including the "service profile" of the UE 102. The service profile may be configured to indicate one or more of the device types of the UE 102 and/or one or more services operable at the UE 102. In some aspects of the content of this case, the device type indication from the UE 102 to the RAN node 106 for the service node selection performed by the RAN node 106 may be explicit and/or implicit.

Regarding the implicit indication of the device type of the UE, the RAN node 106 may select the serving node 112 for the UE 102 according to the indication of the UE identifier. The identifier signaled by the UE 102 and used for serving node selection can be any suitable identifier, including but not limited to the UE's International Mobile Service User Identifier (IMSI) or UE 102's Media Access Control (MAC -ID) identifier. For example, the identifier may be defined as including information related to the device type of the UE. The RAN node 106 can use the identifier of the UE, based on, for example, IMSI prefix matching. Configurable to select the service node 112. The list of IMSI prefix matches can be provided from the service node 112 to the RAN node 106 by using OAM configuration or during the S1 setup signal transmission. When the UE 102 is establishing a connection and explicitly indicating the device type and/or service of the UE 102 that needs to be supported by the serving node 112 in the initial NAS message from the UE 102, there may be an explicit serving node selection. In some aspects of the content of this case, when the UE 102 has not yet attached to the network, the information configured to indicate the service profile of the UE may only be included in the attach request 1002. In other words, the device type information can only be included in the initial attachment message, and not in the subsequent connection establishment signal transmission.

In some aspects of the content of this case, the UE 102 may have multiple device types. Such a UE 102 may perform a separate attachment procedure for each device type, thereby generating a separate connection (for example, there is one connection for each device type). For example, a smart phone may be configured to connect to a service node 112 for telephone service. The smart phone can establish another connection for the video player service. The smart phone can also establish another connection for low-power services, such as a connection configured to send records.

Without departing from the scope of protection of the content of this case, the service type and access point name (APN) can be configured in various configurations. In some configurations, a particular service can be mapped to one or more associated APNs (eg, Internet APN, voice APN, data APN, etc.). For example, a specific application executed on the UE 102 may utilize a voice APN and a data APN. In some configurations, one or more applications can be mapped to a single APN. For example, both a video application and an Internet browsing application running on the UE 102 can be mapped to the Internet APN. In some configurations, if no service is active for a particular APN, then You can start the specific APN. For example, if a voice-related application is mapped to a data APN, and the user is not currently making a voice call, then the data APN can be activated. The APN can be activated or deactivated based on the active service using the APN. In some configurations, some services can be mapped to their own dedicated APNs. For example, a service provider's voice service can utilize its own dedicated APN.

At block 1004, the RAN node 106 may select the serving node 112. The RAN node 106 may determine a set of service nodes 112 that can handle the device type and/or service corresponding to the UE 102. This information from the service node 112 to the RAN node 106 can be stored in the memory at the RAN node 106, and OAM configuration signal transmission and/or S1 setup procedure signal transmission can be used to provide this information from the service node 112 to the RAN. Node 106. The RAN node 106 may select a specific service node 112 from the set accordingly based on such parameters and the relative capacity IE, so as to promote load balancing among various service nodes. In some aspects of the content of this case, the serving node 112 may assign GUTI to the UE 102. The assigned GUTI may be the device type and/or service or subscription profile of the UE 102. After the RAN node 106 selects the serving node 112, the RAN node 106 may send an attachment request 1006 to the serving node 112. After receiving the attach request 1006, the serving node 112 may send an attach acceptance 1008 to the RAN node 106. In response, the RAN node 106 may send an attach acceptance 1010 to the UE 102.

To select a serving node (e.g., serving node 112) according to a specific device type of UE 102, the selected serving node (e.g., serving node 112) should generally be able to handle all services associated with the device type. For example, UE 102 may be a smart phone. If the smart phone is connected to the service Node 112, the service node 112 should generally be able to handle all (for example, up to tens or hundreds of) services that can be implemented by a smart phone. If the smart phone activates a service that is currently unavailable or not supported at the selected service node 112, the service node 112 can execute the service node to another service node that supports the specific service as described in more detail below Re-elect.

Enhanced service node reselection

FIG. 11 is a diagram 1100 illustrating a service node reselection procedure according to some aspects of the content of this case. As described in more detail above, the selected serving node (e.g., serving node 112) should be able to handle all services associated with the device type of the UE. If the UE 102 attempts to start a service that is currently unavailable or not supported by the current serving node, the serving node 112 may perform serving node reselection (for example, reselecting to another serving node 112). The RAN node 106 may utilize the equipment type of the UE and/or the signaled service to select the target RAN node 106 for the handover of the UE 102. In some configurations, the UE 102 may provide the selected device type and/or service of the UE 102 during the RRC signal delivery. In some configurations, the serving node 112 and/or the source RAN node 116 may provide the selected device type and/or service of the UE 102 during the S1/X2 handover to select the target cell for future handover. For example, as part of the X2 setup procedure, the RAN node 106 may exchange available device types and/or services from the service node to which it is connected. Generally, the X2 setup procedure establishes an X2 interface between various RAN nodes 106 (e.g., eNB). In this way, when the connected UE When 102 is preparing for handover, the RAN node 106 may limit the set of candidate RAN nodes 106 to connect to the cell that supports the device type and/or service of the UE. As described in more detail above, the UE 102 may send an attach request message to the RAN node 106 1002. Subsequently, at block 1004, the RAN node 106 may perform serving node reselection. A detailed description of such steps is provided above with reference to FIG. 10, so it will not be repeated.

Various situations can trigger the service node reselection procedure. In some cases, after the UE 102 connects to the serving RAN node 106, the UE 102 may indicate to the RAN node 106 one or more new services and/or indicate new or different service types. If the currently connected serving node 112 does not support such an indicated service and/or device type of the UE 102, in such a case, a serving node reselection may occur. In some other cases, the UE 102 with an existing serving node connection can move in location. Because of the movement in position, the UE 102 can change its tracking area and/or move out of the service area of its selected serving node 112. In such cases, service node reselection can occur.

According to some aspects of the content of this case, the UE 102 may send certain information to the RAN node 106, such as a service or tracking area update (TAU) request. Such transmission may include appropriate information for service node selection as described in more detail above. Such information may include, but is not limited to: a device ID, one or more device types, and/or one or more services utilized by the UE 102. The RAN node may perform the service node selection procedure as described in more detail above. The RAN node 106 may check the device type and/or service to ensure that they are supported by the existing service node 112 indicated in the device ID. If the device type and/or service is supported by the indicated existing serving node 112 (for example, by the GUTI of the UE), the RAN node 106 may forward the request to the current serving node 112.

If the existing service node 112 does not support the equipment type and/or service of the UE 102, the RAN node 106 may decide to select a new service node 1112. As above As described in the text, the RAN node 106 can refer to the information stored in its memory as received from the serving nodes 112 and 1112 to find the appropriate serving node 1112 for the UE 102. A set of service nodes capable of handling these types of equipment and/or services can be selected from the service nodes, and such information for these service nodes has been stored at the RAN node 106. The RAN node 106 may then select a specific service node 1112 from this set of service nodes based on the relative capacity IE, so as to implement load balancing among the service nodes.

In order to select a new service node 1112, the RAN node 106 may send a service or TAI request 1106 to the new service node 1112. Subsequently, the new service node may send a context request 1108 to the existing (eg, "old") service node 112, and in response, the existing service node 112 may send a context response 1110 to the new service node 1112. In response to receiving the context response 1110, the new serving node 1112 may send a service or TAU response acceptance 1114 to the RAN node 106, and the RAN node 106 will forward the service or TAI response acceptance 1116 to the UE 102. Therefore, the newly selected serving node 1112 can retrieve the UE 102 context from the existing serving node 112 based on GUTI. The new serving node 1112 can also select and assign a new GUTI to the UE 102. The new serving node 1112 may assign a GUTI that is a function of the UE 102's device type, service, and/or subscription profile.

Various methods and/or procedures operable at the UE

FIG. 12 is a diagram 1200 illustrating examples of various methods and/or procedures operable at the UE 102. At step 1202, the UE 102 may decide whether to include the service profile of the UE 102 in the connection request message. For example, referring to FIG. 10, the connection request message may be an attach request 1002. Can not deviate from the case In the case of the protection scope of the content, such a decision is performed according to many configurations. In some configurations, if the UE 102 has not been registered with the network, the UE 102 may decide whether to include the service profile of the UE 102 in the connection request message (eg, attach request 1002). In some other configurations, if the service profile has changed since the UE 102 recently established a connection at the network, the UE 102 may decide whether to include the service profile of the UE 102 in the connection request message (eg, attach request 1002) . In some other configurations, the UE 102 may support the service profile of the UE 102 according to the known network identifier and tracking area for the RAN node 106 and the UE 102 according to the list of RAN nodes stored in the memory of the UE 102. The decision associated with at least one of the function variable code, the cell ID, or the SSID determines the establishment of a connection with the RAN node 106.

Subsequently, at step 1204, the UE 102 may send a connection request message (e.g., attach request 1002) configured to request an initial connection with the RAN node 106. The connection request message may include information configured to indicate the service profile of the UE 102. The service profile may be configured to indicate one or more device types of the UE 102 and/or one or more services operable at the UE 102. As described in more detail above, the service profile of the UE 102 may include an implicit indication of the device type of the UE 102 and/or explicit information configured to indicate the device type of the UE 102. The device types of the UE 102 may include: voice devices, streaming media devices, web browsing devices, mission-critical devices, low-power devices, Internet devices, sensor devices, and/or IOE devices. The above provides additional descriptions about service profiles, device types, and services operable at the UE 102, so they will not be repeated.

After sending the connection request message, at step 1206, the UE 102 Can receive connection acceptance messages. The connection acceptance message may include information configured to indicate a service node selected based at least in part on the service profile of the UE 102. For example, referring to FIG. 10, the UE 102 may receive an attach acceptance 1010 from the RAN node 106, and the attach acceptance 1010 may include information indicating a service node selected based at least in part on the service profile of the UE 102.

In some cases, the service profile of UE 102 may change. For example, the UE 102 may have variations in one or more device types of the UE 102 and/or one or more services operable at the UE 102. In such a case, at step 1208, the UE 102 may send information indicating the change of the service profile to the RAN node 106. For example, referring to FIG. 11, the existing service node 112 may not support the device type and/or service of the UE 102. Therefore, the RAN node 106 may need to decide to select a new serving node 1112. Subsequently, at step 1210, the UE 102 may receive information indicating the change of the selected serving node. The change of the selected serving node may be consistent with the changed service profile of the UE 102. For example, the information may indicate a change from the service node 112 to the service node 1112. The serving node 112 can be changed (to another serving node 1112), because the serving node 112 can accommodate the changed service profile of the UE 102.

FIG. 13 is a diagram 1300 illustrating another example of various other methods and/or procedures operable at the UE 102. In some configurations, the service profile of UE 102 may include the device type of UE 102. At step 1302, the UE 102 may receive a broadcast message from the RAN node 106. The broadcast message may include information for indicating whether at least one serving node associated with the RAN node supports the device type of the UE. For example, referring to FIG. 10, such information may indicate whether at least one of the service nodes 112, 1112 associated with the RAN node 106 supports The specific device type of UE 102. At step 1304, the UE 102 may decide to establish an initial connection with the RAN node 106. The UE 102 may decide to establish an initial connection with the RAN node 106 according to the received broadcast message. For example, referring to FIG. 10, because at least one of the serving nodes 112, 1112 supports a specific device type of the UE 102, the UE 102 may decide to establish an initial connection with the RAN node 106.

Subsequently, at step 1306, the UE 102 may send a connection request message (e.g., attach request 1002) configured to request an initial connection with the RAN node 106. The connection request message may include information configured to indicate the service profile of the UE 102. The service profile may be configured to indicate one or more device types of the UE 102 and/or one or more services operable at the UE 102. As described in more detail above, the service profile of the UE 102 may include an implicit indication of the device type of the UE 102 and/or explicit information configured to indicate the device type of the UE 102. The device type of the UE 102 may include: a voice device, a streaming media device, a web browsing device, a mission-critical device, a low-power device, an Internet device, a sensor device, and/or an IOE device. The above provides additional descriptions about service profiles, device types, and services operable at the UE 102, so they will not be repeated.

In some configurations, at step 1308, UE 102 may send a TAU request message. The TAU request message may include information configured to indicate the service profile of the UE 102. For example, such transmissions may include appropriate information for service node selection as described in more detail above. Such information may include, but is not limited to: a device ID, one or more device types, and/or one or more services utilized by the UE 102. As described above with reference to FIG. 11, the RAN node 106 may check the device type and/or service to ensure that they are indicated by the existing service indicated in the device ID. Service node 112 supports. If the device type and/or service is supported by the indicated existing serving node 112 (for example, by the GUTI of the UE), the RAN node 106 may forward the request to the current serving node 112. In order to select a new service node 1112, the RAN node 106 may send a service or TAI request 1106 to the new service node 1112. Subsequently, the new service node may send a context request 1108 to the existing service node 112, and in response, the existing service node 112 may send a context response 1110 to the new service node 1112. In response to receiving the context response 1110, the new serving node 1112 may send a service or TAU response acceptance 1114 to the RAN node 106, and the RAN node 106 will forward the service or TAI response acceptance 1116 to the UE 102. Therefore, at step 1310, the UE 102 may receive the TAU request acceptance message. The TAU request acceptance message may include information for indicating a serving node (eg, serving node 1112) selected based at least in part on the service profile of the UE 102.

Various methods and/or procedures operable at the RAN node

FIG. 14 is a diagram 1400 illustrating examples of various methods and/or procedures operable at the RAN node 106. At step 1402, the RAN node 106 may receive information from the serving node. Such information may indicate one or more UE device types and/or services supported by the selected serving node. Such information may also include an identifier that identifies the UE 102. Such information may include various aspects described herein with reference to the service profile of UE 102. At step 1404, the RAN node 106 may store such information in the memory of the RAN node 106. In some configurations, such information may be received by the RAN node 106 as a signal transfer that includes part of the signal transfer that is used to establish an interface between the RAN node 106 and the selected service node. In some other configurations, Such information can be received by the RAN node 106 as an OAM signal between the RAN node 106 and the selected serving node.

At step 1406, the RAN node 106 may broadcast a message including information indicating the service profile supported by the set of service nodes associated with the RAN node. By broadcasting such messages, the RAN node 106 can provide the UE with notifications about the capacity of the set of service nodes associated with the RAN node to support various service profiles. For example, referring to FIG. 11, the RAN node 106 may broadcast such a message for indicating the service profile supported by the service node 112 and the service node 1112.

At step 1408, the RAN node 106 may receive a connection request message from the UE 102. For example, referring to FIG. 10, the RAN node 106 may receive an attach request 1002 from the UE 102. The connection request message (e.g., attach request 1002) may include information configured to indicate the service profile of the UE. The above provides additional information about the service profile of UE 102, so it will not be repeated.

At step 1410, the RAN node 106 may select a serving node for the UE 102 based at least in part on the service profile of the UE 102. For example, referring to FIG. 10, at block 1004, the RAN node 106 may select the serving node 112 at least in part because the serving node 112 supports the service profile of the UE 102. In some configurations, the RAN node 106 may select a serving node for the UE 102 via the following operations: (i) Determine one or more serving nodes that can attach the UE 102 with the device type as indicated in the service profile of the UE 102 And (ii) selecting a service node from the set of one or more service nodes based on the capacity information elements received from each of the set of one or more service nodes. At step 1412, the RAN node 106 may forward to the selected serving node Connection request message. For example, referring to FIG. 10, the RAN node 106 may forward the attach request 1006 to the serving node 112.

In some cases, the service profile of UE 102 may change. For example, the UE 102 may have variations in one or more device types of the UE 102 and/or one or more services operable at the UE 102. In such a case, at step 1414, the RAN node 106 may receive information from the UE 102 for indicating changes in the service profile of the UE 102. According to the decision that the selected serving node does not support the changed service profile of the UE 102, at step 1416, the RAN node 106 may select a new service profile for the UE 102 based at least in part on the changed service profile of the UE 102 Service node. For example, referring to FIG. 11, when it is determined that the serving node 112 does not support the changed service profile of the UE 102, the RAN node 106 may select a new serving node 1112 for the UE 102 because the existing serving node 112 does not support the UE 102 The changed service profile. At step 1418, the RAN node 106 may send an indication of the new serving node 1112 to the UE 102 or the existing serving node 112.

Various methods and/or procedures that can be operated at the service node

FIG. 15 is a diagram 1500 illustrating examples of various methods and/or procedures operable at a service node. At step 1502, the serving node may receive a request for establishing an interface between the RAN node 106 and the serving node 112 from the RAN node 106. For example, referring to FIG. 9, the service node 112 may receive an S1 setup request 902 from the RAN node 106 to establish an interface between the RAN node 106 and the service node 112. At step 1504, the service node may send a response including information related to one or more service profiles supported by the service node. For example, referring to FIG. 9, the service node 112 may send an S1 setup response 904 to the RAN node 106, And the S1 setup response 904 may include information related to the service profile supported by the service node 112.

Such information can be provided in various configurations without departing from the scope of protection of the content of the case. In some configurations, such information may indicate one or more RATs supported by the serving node 112. The service profile may indicate one or more device types supported by the service node 112. In some other configurations, such information may include one or more device identifier prefixes supported by the service node 112. The service profile of the service node 112 can be provided in various configurations without departing from the protection scope of the content of this case. The service profile may indicate one or more service profiles supported by the service node 112. The above provides an additional description of the service profile, so it will not be repeated.

At step 1506, the serving node may receive a connection request message from the RAN node 106. For example, referring to FIG. 10, the serving node 112 may receive the attach request 106 from the RAN node 106. The connection request message (eg, attach request 106) may be configured to establish communication with the UE 102. The connection request message may include a service profile corresponding to the UE 102. At step 1508, the serving node may determine an identifier for UE 102. The identifier may be a function of the service profile corresponding to UE 102. At step 1510, the serving node may send a connection acceptance message to the RAN node 106. The connection acceptance message may include an identifier for the UE 102. For example, referring to FIG. 10, the serving node 112 may send an attach accept 1008, and the attach accept 1008 may include an identifier for the UE 102.

In some cases, the service profile of UE 102 may change. For example, the UE 102 may have variations in one or more device types of the UE 102 and/or one or more services operable at the UE 102. In such cases, in step 1512 At this point, the serving node may receive a message indicating the update of the service profile corresponding to the UE. For example, referring to FIG. 11, the service node 112 may receive a context request 1108. At step 1514, the serving node may determine that the received message indicates that the serving node (for example, the serving node 112) no longer supports the UE 102. For example, the serving node 112 may determine that the serving node 112 may no longer be able to support the updated service profile of the UE 102. Subsequently, at step 1516, the serving node may send information to another serving node that supports the updated service profile corresponding to the UE 102. For example, referring to FIG. 11, the serving node 1112 may support the updated service profile corresponding to the UE 102. Therefore, the service node 112 can send a context response 1110 to the service node 1112. In some configurations, at step 1518, the serving node may also send information for the UE 102 to the RAN node 106 for indicating other serving nodes (for example, the serving node 1112) for the UE 102.

UE's hardware implementation

FIG. 16 is a diagram illustrating an example of a hardware implementation of a UE including a processing system 1601. By way of example and not limitation, the UE 1600 described herein with reference to FIG. 16 may be similar to those described herein with reference to FIG. 1, FIG. 2, FIG. 6, FIG. 7, FIG. 8, FIG. 9, FIG. 10, FIG. 11, FIG. 12, and/or FIG. The UE 102 described in 13 is the same. In some configurations, the processing system 1601 may include a user interface 1612. The user interface 1612 may be configured to receive one or more inputs from a user of the processing system 1601. The user interface 1612 may also be configured to display information (for example, text and/or images) to the user of the processing system 1601. The user interface 1612 can exchange data to and/or exchange data from the processing system 1601 via the bus interface 1608.

The processing system 1601 may also include a transceiver 1610. The transceiver 1610 can be configured to receive data and/or send data when communicating with another device. The transceiver 1610 provides a unit for communicating with another device via a wired and/or wireless transmission medium. The transceiver 1610 can be configured to use various types of technologies to perform this type of communication. Those with ordinary knowledge in the field to which the present invention pertains will understand that many types of technologies for performing this type of communication can be used without departing from the scope of protection of the content of the case. The processing system 1601 may also include a memory 1614, one or more processors 1604, a computer-readable medium 1606, and a bus interface 1608. The bus interface 1608 can provide an interface between the bus 1603 and the transceiver 1610. The memory 1614, one or more processors 1604, the computer readable medium 1606, and the bus interface 1608 may be connected together via the bus 1603. The processor 1604 may be communicatively coupled to the transceiver 1610 and/or the memory 1614.

The processor 1604 may include a receiving circuit 1620, a control circuit 1621, a transmission circuit 1622, and/or other circuits 1623. Generally, the receiving circuit 1620, the control circuit 1621, the transmission circuit 1622, and/or other circuits 1623 may individually or collectively include various hardware components and/or software modules, and the various hardware components and/or software modules may be Perform and/or implement any one or more of the functions, methods, operations, procedures, features, and/or aspects described herein with reference to the UE.

In some configurations, the control circuit 1621 may be configured to decide whether to include the service profile of the UE 1600 in the connection request message. Such decisions can be performed according to many configurations described in more detail herein. For example, if the UE 1600 has not been registered at the network, the control circuit 1621 can perform such a decision. As another example, if the UE 1600 has recently established a connection on the network Since the service profile has changed, the control circuit 1620 can perform such a decision. As another example, the control circuit 1620 may support the service profile of the UE 1600 according to the known network identifier and tracking area function for the RAN node and the UE 1600 according to the list of RAN nodes stored in the memory at the UE 1600. At least one of the variable code, cell ID, or SSID is associated with a decision to perform such a decision.

The transmission circuit 1622 may be configured to use the transceiver 1610 to send a connection request message, where the connection request message is configured to request an initial connection with the RAN node. The connection request message may include information configured to indicate the service profile of the UE 1600. The service profile may be configured to indicate one or more device types of the UE 1600 and/or one or more services operable at the UE 1600. As described in more detail above, the service profile of the UE 1600 may include an implicit indication of the device type of the UE 1600 and/or explicit information configured to indicate the device type of the UE 1600. The device types of the UE 1600 may include: voice devices, streaming media devices, web browsing devices, mission-critical devices, low-power devices, Internet devices, sensor devices, and/or IOE devices. The above provides additional descriptions about service profiles, device types, and services operable at the UE 1600, so it will not be repeated.

The receiving circuit 1620 may be configured to receive a connection acceptance message. The connection acceptance message may include information configured to indicate a service node selected based at least in part on the service profile of the UE 1600. In some cases, the service profile of the UE 1600 may vary. For example, the UE 1600 may have a variation of one or more device types of the UE 1600 and/or one or more services operable at the UE 1600. In such cases, the transmission circuit 1622 can be configured to utilize The transceiver 1610 sends information indicating the change of the service profile to the RAN node. The RAN node may need to decide to select a new service node. Therefore, the receiving circuit 1620 may be configured to use the transceiver 1610 to receive information indicating the change of the selected service node. The change of the selected serving node may be consistent with the changed service profile of the UE 1600. For example, as illustrated in FIG. 11, the information may indicate a change from one service node 112 to another service node 1112, because other service nodes 1112 can accommodate the changed service profile.

In some configurations, the receiving circuit 1620 may be configured to receive broadcast messages from RAN nodes. The broadcast message may include information for indicating whether at least one serving node associated with the RAN node supports the device type of the UE 1600. The control circuit 1621 may be configured to decide to establish an initial connection with the RAN node based on the received broadcast message. For example, as illustrated in FIG. 10, the UE 102 may decide to establish an initial connection with the RAN node 106, because at least one of the serving nodes 112, 1112 supports a specific device type of the UE 102. The transmission circuit 1622 may be configured to use the transceiver 1610 to send a connection request message, and the connection request message may be configured to request an initial connection with a RAN node. The connection request message may include information configured to indicate the service profile of the UE 1600. The service profile may be configured to indicate one or more device types of the UE 1600 and/or one or more services operable at the UE 1600. The above provides additional descriptions about service profiles, device types, and services operable at the UE 1600, so it will not be repeated.

In some configurations, the transmission circuit 1622 may be configured to use the transceiver 1610 to send TAU request messages. The TAU request message can include Set to information indicating the service profile of the UE 1600. Such information may include, but is not limited to: device ID, one or more device types, and/or one or more services utilized by the UE 1600. The receiving circuit 1620 may be configured to use the transceiver 1610 to receive the TAU request acceptance message. The TAU request acceptance message may include information indicating the service node selected based at least in part on the service profile of the UE 1600.

The foregoing description provides a non-limiting example of the processor 1604 of the processing system 1601. Although various circuits have been described above, those skilled in the art to which the present invention pertains will understand that the processor 1604 may also include various other circuits 1623 that supplement or replace the circuits 1620, 1621, and 1622. Such other circuits 1623 may provide units for performing any one or more of the functions, methods, operations, procedures, features, and/or aspects described herein with reference to the UE.

The computer-readable medium 1606 includes various computer-executable instructions. The computer executable code may be executed by various hardware components of the processing system 1601 (for example, the processor 1604 or any one or more of its circuits 1620, 1621, 1622, 1623). Instructions can be part of various software programs and/or software modules. The computer-readable medium 1606 may include receiving instructions 1640, control instructions 1641, transmission instructions 1642, and/or other instructions 1643. Generally, the receiving instruction 1640, the control instruction 1641, the transmission instruction 1642, and/or other instructions 1643 can be individually or collectively configured to execute and/or implement the functions, methods, operations, procedures, features, and features described herein with reference to the UE. / Or any one or more of the aspects.

In some configurations, the control instructions 1641 may include computer-executable Instructions, the computer-executable instructions are configured to determine whether to include the service profile of the UE 1600 in the connection request message. Such decisions can be performed according to many configurations described in more detail above. For example, if the UE 1600 has not been registered at the network, the control instructions 1641 may be configured to perform such a decision. As another example, if the service profile has changed since the UE 1600 recently established a connection at the network, the control instructions 1640 may be configured to perform such a decision. As yet another example, the control command 1640 may be configured to support the service profile of the UE 1600 according to a known network identifier for the RAN node and the UE 1600 according to the list of RAN nodes stored in the memory at the UE 1600, At least one of the tracking area function variable code, cell ID, or SSID is associated with a decision to perform such a decision.

The transmission instruction 1642 may include a computer-executable instruction configured to send a connection request message, and the connection request message may be configured to request an initial connection with the RAN node. The connection request message may include information configured to indicate the service profile of the UE 1600. The service profile may be configured to indicate one or more device types of the UE 1600 and/or one or more services operable at the UE 1600. As described in more detail above, the service profile of the UE 1600 may include an implicit indication of the device type of the UE 1600 and/or explicit information configured to indicate the device type of the UE 1600. The device types of the UE 1600 may include: voice devices, streaming media devices, web browsing devices, mission-critical devices, low-power devices, Internet devices, sensor devices, and/or IOE devices. The above provides additional descriptions about service profiles, device types, and services operable at the UE 1600, so it will not be repeated.

The receiving instruction 1640 may include a Computer-executable instructions for information. The connection acceptance message may include information configured to indicate a service node selected based at least in part on the service profile of the UE 1600. In some cases, the service profile of the UE 1600 may vary. For example, the UE 1600 may have a variation of one or more device types of the UE 1600 and/or one or more services operable at the UE 1600. In such cases, the transmission instructions 1642 may include computer-executable instructions configured to send information indicating changes in the service profile to the RAN node. The RAN node may need to decide to select a new service node. Therefore, the receiving instructions 1640 may include computer-executable instructions configured to receive information indicating changes to the selected service node. The change of the selected serving node may be consistent with the changed service profile of the UE 1600. For example, as illustrated in FIG. 11, the information may indicate a change from the service node 112 to the service node 1112, because the service node 1112 can accommodate the changed service profile.

In some configurations, the receiving instructions 1640 may include computer-executable instructions configured to receive broadcast messages from the RAN node. The broadcast message may include information for indicating whether at least one serving node associated with the RAN node supports the device type of the UE 1600. The control instructions 1641 may include computer-executable instructions configured to determine the establishment of an initial connection with the RAN node based on the received broadcast message. For example, as illustrated in FIG. 10, the UE 102 may decide to establish an initial connection with the RAN node 106, because at least one of the serving nodes 112, 1112 supports a specific device type of the UE 102. The transmission instruction 1642 may include a computer-executable instruction configured to send a connection request message, and the connection request message may be configured to request an initial connection with the RAN node. The connection request message may include a service profile configured to indicate UE 1600 File information. The service profile may be configured to indicate one or more device types of the UE 1600 and/or one or more services operable at the UE 1600. The above provides additional descriptions about service profiles, device types, and services operable at the UE 1600, so it will not be repeated.

In some configurations, the transmission instructions 1642 may include computer-executable instructions configured to send TAU request messages. The TAU request message may include information configured to indicate the service profile of the UE 1600. Such information may include, but is not limited to: device ID, one or more device types, and/or one or more services utilized by the UE 1600. The receiving instructions 1640 may include computer-executable instructions configured to receive TAU request acceptance messages. The TAU request acceptance message may include information indicating the service node selected based at least in part on the service profile of the UE 1600.

The foregoing description provides a non-limiting example of the computer-readable medium 1606 of the processing system 1601. Although various instructions (for example, computer executable code) have been described above, those skilled in the art to which the present invention pertains will understand that the computer readable medium 1606 may also include supplementary or alternative instructions 1640, 1641, 1642. 1643 of various other instructions. Such other instructions 1643 may include computer executable code configured to perform any one or more of the functions, methods, procedures, operations, features, and/or aspects described herein with reference to the UE.

The memory 1614 may include various storage modules. The storage module can be configured to store and read various values and/or information from the processor 1604 or any of its circuits 1620, 1621, 1622, 1623. The storage module can also be configured to store and retrieve the The computer-executable code is included in the computer-readable medium 1606 or any instructions in the computer-readable medium 1606 or its instructions 1640, 1641, 1642, 1643. In some configurations, the memory 1614 may include service profile information 1630. The service profile information 1630 may include data about the service profile. The service profile may be configured to indicate one or more device types of the UE 1600 and/or one or more services operable at the UE 1600. As described in more detail above, the service profile of the UE 1600 may include an implicit indication of the device type of the UE 1600 and/or explicit information configured to indicate the device type of the UE 1600. The device types of the UE 1600 may include: voice devices, streaming media devices, web browsing devices, mission-critical devices, low-power devices, Internet devices, sensor devices, and/or IOE devices. The above provides additional descriptions about service profiles, device types, and services operable at the UE 1600, so it will not be repeated. Those skilled in the art to which the present invention pertains will also understand that the memory 1614 may also include various other storage modules 1632. The other storage module 1632 may be configured to store information therein and read information therefrom regarding any of the features, functions, methods, procedures, operations, and/or aspects described herein.

Those with ordinary knowledge in the field of the present invention will also understand that the processing system 1601 may include alternative and/or additional elements without departing from the scope of protection of the content of the case. According to some aspects of the content of the present case, the element, or any part of the element, or any combination of the elements may be implemented using a processing system 1601 including one or more processors 1604. Examples of the one or more processors 1604 include microprocessors, microcontrollers, digital signal processors (DSPs), field controllers that are configured to perform the various functions described throughout this case. Programmable gate array (FPGA), programmable logic device (PLD), state machine, gated logic unit, individual hardware circuits and other appropriate hardware. The processing system 1601 can be implemented using a bus architecture generally represented by a bus 1603 and a bus interface 1608. The bus bar 1603 may include any number of interconnecting bus bars and bridges, depending on the specific application of the processing system 1601 and the overall design constraints. The bus 1603 can connect various circuits including one or more processors 1604, a memory 1614, and a computer-readable medium 1606 together. The bus 1603 can also be connected to various other circuits known in the art, such as timing sources, peripheral devices, voltage regulators, and power management circuits.

One or more processors 1604 may be responsible for managing the bus 1603 and general processing, including the execution of software stored on the computer-readable medium 1606. The software, when executed by one or more processors 1604, causes the processing system 1601 to perform various functions described below for any one or more devices. The computer-readable medium 1606 can also be used to store data manipulated by one or more processors 1604 when executing software. Whether it is called software, firmware, intermediary software, microcode, hardware description language, or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code snippets, program codes, programs, and vice-versa. Programs, software modules, applications, software applications, packaged software, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc. The software may be located on a computer readable medium 1606. The computer-readable medium 1606 may be a non-transitory computer-readable medium. By way of example, non-transitory computer-readable media include magnetic storage devices (such as hard disks, floppy disks, magnetic strips), optical disks (such as , Compact disc (CD), digital versatile disc (DVD), smart card, Flash memory device (for example, card, stick or key disk)), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM) ), electronically erasable PROM (EEPROM), register, removable disk and any other appropriate media. By way of example, the computer-readable medium 1606 may also include carrier waves, transmission lines, and any other suitable media for transmitting software and/or instructions that can be accessed and read by a computer. The computer-readable medium 1606 may be located in the processing system 1601, external to the processing system 1601, or distributed across multiple entities including the processing system 1601. The computer readable medium 1606 may be embodied in a computer program product. By way of example and not limitation, the computer program product may include the computer readable medium in the packaging material. Those with ordinary knowledge in the field to which the present invention pertains will recognize how to best implement the functions described throughout the content of this case based on specific applications and the overall design constraints imposed on the entire system.

Hardware implementation of RAN node

FIG. 17 is a diagram illustrating an example of a hardware implementation of the RAN node 1700 including the processing system 1701. By way of example and not limitation, the RAN node 1700 described herein with reference to FIG. 17 may be the same as that described herein with reference to FIG. 1, FIG. 2, FIG. 6, FIG. 7, FIG. 8, FIG. 9, FIG. 10, FIG. 11, and/or FIG. The RAN node 106 is the same. The processing system 1701 may include a transceiver 1710. The transceiver 1710 may be configured to receive data and/or send data when communicating with another device. The transceiver 1710 provides a unit for communicating with another device via a wired and/or wireless transmission medium. The transceiver 1710 can be configured to use various types of technologies to perform this type of communication. Those with ordinary knowledge in the field to which the present invention belongs will understand that, without departing from the scope of protection of the content of this case, Many types of technologies are used to perform this type of communication. The processing system 1701 may also include a memory 1714, one or more processors 1704, a computer-readable medium 1706, and a bus interface 1708. The bus interface 1708 can provide an interface between the bus 1703 and the transceiver 1710. The memory 1714, one or more processors 1704, the computer-readable medium 1706, and the bus interface 1708 may be connected together via the bus 1703. The processor 1704 may be communicatively coupled to the transceiver 1710 and/or the memory 1714.

The processor 1704 may include a receiving circuit 1720, a control circuit 1721, a transmission circuit 1722, and/or other circuits 1723. Generally, the receiving circuit 1720, the control circuit 1721, the transmission circuit 1722, and/or other circuits 1723 may individually or collectively include various hardware components and/or software modules, and the various hardware components and/or software modules may be Perform and/or implement any one or more of the functions, methods, operations, procedures, features, and/or aspects described herein with reference to the RAN node.

The receiving circuit 1720 may be configured to use the transceiver 1710 to receive information from the service node. Such information may indicate one or more device types and/or services supported by the selected service node. Such information may also include identifiers that identify the UE. Such information may include various aspects described herein with reference to the service profile of the UE. The control circuit 1721 may be configured to store such information in the memory of the RAN node 1700. In some configurations, such information may be received by the RAN node 1700 as a signal transfer that includes part of the signal transfer for establishing an interface between the RAN node 1700 and the selected serving node. In some other configurations, such information can be transmitted as OAM signals between the RAN node 1700 and the selected service node. The RAN node 1700 receives.

In some configurations, the transmission circuit 1722 may be configured to utilize the transceiver 1710 to broadcast a message including information indicating the service profile supported by the set of service nodes associated with the RAN node 170. By broadcasting such messages, the RAN node 1700 can provide the UE with a notification about the capacity of the set of service nodes associated with the RAN node 1700 to support various service profiles. For example, referring to FIG. 11, the RAN node 106 may broadcast such a message indicating the service profile supported by the existing service node 112 and the new service node 1112.

In some configurations, the receiving circuit 1720 may be configured to receive a connection request message from the UE. For example, referring to FIG. 10, the RAN node 106 may receive an attach request 1002 from the UE 102. The connection request message may include information configured to indicate the service profile of the UE. The above provides additional information about the service profile of the UE, so it will not be repeated.

In some configurations, the control circuit 1721 may be configured to select a serving node for the UE based at least in part on the service profile of the UE. For example, referring to FIG. 10, at block 1004, the RAN node 106 may select the serving node 112 at least in part because the serving node 112 supports the service profile of the UE 102. In some configurations, the control circuit 1721 may be configured to select a serving node for the UE via the following operations: (i) Determine one or more serving nodes that can attach the UE with the device type as indicated in the service profile of the UE And (ii) selecting a service node from the set of one or more service nodes based on the capacity information elements received from each of the set of one or more service nodes. The transmission circuit 1722 may be configured to use the transceiver 1710 to send the selected The service node forwards the connection request message. For example, as illustrated in FIG. 10, the RAN node 106 may forward the attach request 1006 to the serving node 112.

In some cases, the service profile of the UE may change. For example, the UE may have a variation of one or more device types of the UE and/or one or more services operable at the UE. In such a case, the receiving circuit 1720 may be configured to use the transceiver 1710 to receive information indicating the change of the service profile from the UE. According to the decision that the selected serving node does not support the UE's changed service profile, the control circuit 1721 may be configured to select a new serving node for the UE based at least in part on the UE's changed service profile. For example, as shown in FIG. 11, when it is determined that the serving node 112 does not support the changed service profile of the UE 102, the RAN node 106 may select a new serving node 1112 for the UE 102 because the serving node 1112 supports The changed service profile of the UE 102. The transmission circuit 1722 may be configured to send an indication of a new serving node (for example, the serving node 1112) to the UE or an existing serving node (for example, the serving node 112).

The foregoing description provides a non-limiting example of the processor 1704 of the processing system 1701. Although various circuits have been described above, those skilled in the art to which the present invention pertains will understand that the processor 1704 may also include various other circuits 1723 that supplement or replace the circuits 1720, 1721, 1722. Such other circuits 1723 may provide units for performing any one or more of the functions, methods, operations, procedures, features, and/or aspects described herein with reference to the RAN node.

The computer-readable medium 1706 includes various computer-executable instructions. The computer executable code can be executed by various hardware components of the processing system 1701 (for example, The processor 1704, or any one or more of its circuits 1720, 1721, 1722, 1723). Instructions can be part of various software programs and/or software modules. The computer-readable medium 1706 may include: receiving instructions 1740, control instructions 1741, transmission instructions 1742, and/or other instructions 1743. Generally, the receiving instruction 1740, the control instruction 1741, the transmission instruction 1742, and/or other instructions 1743 can be individually or collectively configured to execute and/or implement the functions, methods, operations, procedures, and features described herein with reference to the RAN node. And/or any one or more of the aspects.

The receiving instructions 1740 may include computer executable code configured to receive information from the service node. Such information may indicate one or more device types and/or services supported by the selected service node. Such information may also include identifiers that identify the UE. Such information may include various aspects described herein with reference to the service profile of the UE. The control instructions 1741 may include computer executable code configured to store such information in the memory of the RAN node 1700. In some configurations, such information may be received by the RAN node 1700 as a signal transfer that includes part of the signal transfer for establishing an interface between the RAN node 1700 and the selected serving node. In some other configurations, such information may be transmitted as an OAM signal between the RAN node 1700 and the selected serving node to be received by the RAN node 1700.

In some configurations, the transmission instruction 1742 may include computer-executable code configured to broadcast a message including information for indicating the service profile supported by the set of service nodes associated with the RAN node 170. By broadcasting such a message, the RAN node 1700 can provide the UE with a notification about the capacity of the set of serving nodes associated with the RAN node 1700 to support each Service profile. For example, referring to FIG. 11, the RAN node 106 may broadcast such a message for indicating the service profile supported by the service node 112 and the service node 1112.

In some configurations, the receive instruction 1740 may include computer executable code configured to receive a connection request message from the UE. For example, referring to FIG. 10, the RAN node 106 may receive an attach request 1002 from the UE 102. The connection request message may include information configured to indicate the service profile of the UE. The above provides additional information about the service profile of the UE, so it will not be repeated.

In some configurations, the control instructions 1741 may include computer executable code configured to select a serving node for the UE based at least in part on the service profile of the UE. For example, referring to FIG. 10, at block 1004, the RAN node 106 may select the serving node 112 at least in part because the serving node 112 supports the service profile of the UE 102. In some configurations, the control instructions 1741 may include computer-executable code configured to select a serving node for the UE via the following operations: (i) Determine that a UE with a device type as indicated in the service profile of the UE can be attached And (ii) selecting a service node from the set of one or more service nodes based on the capacity information elements received from each of the set of one or more service nodes. The transmission instruction 1742 may include computer executable code configured to forward the connection request message to the selected service node. For example, as illustrated in FIG. 10, the RAN node 106 may forward the attach request 1006 to the serving node 112.

In some cases, the service profile of the UE may change. For example, the UE may have a variation of one or more device types of the UE and/or one or more services operable at the UE. In such cases, receiving instructions 1740 may include being The computer executable code is configured to receive information indicating the change of the service profile from the UE. Based on the decision that the selected serving node does not support the UE's changed service profile, the control instruction 1741 may include a configuration configured to select a new serving node for the UE based at least in part on the UE's changed service profile. Computer executable code. For example, as shown in FIG. 11, when it is determined that the serving node 112 does not support the changed service profile of the UE 102, the RAN node 106 may select a new serving node 1112 for the UE 102 because the serving node 1112 supports The changed service profile of the UE 102. The transmission instruction 1742 may include computer executable code configured to send an instruction to a new service node (eg, service node 1112) to the UE or an existing service node (eg, service node 112).

The foregoing description provides a non-limiting example of the computer-readable medium 1706 of the processing system 1701. Although various instructions (for example, computer executable code) have been described above, those skilled in the art to which the present invention pertains will understand that the computer readable medium 1706 may also include supplementary or alternative instructions 1740, 1741, 1742 Of various other instructions 1743. Such other instructions 1743 may include computer executable code configured to perform any one or more of the functions, methods, procedures, operations, features, and/or aspects described herein with reference to the RAN node.

The memory 1714 may include various storage modules. The storage module can be configured to store and read various values and/or information from the processor 1704 or any of its circuits 1720, 1721, 1722, 1723. The storage module can also be configured to store and read various values and/or information when the computer executable code is executed. The computer executable code is included in the computer executable code. Read media 1706, or any of its instructions 1740, 1741, 1742, 1743. In some configurations, the memory 1714 may include service profile information 1730. The service profile information 1730 may include data about the service profile. The service profile may be configured to indicate one or more device types of any device and/or one or more services operable at that device. As described in more detail above, the service profile of a device may include an implicit indication of the device type of such a device and/or explicit information configured to indicate the device type of the device. Device types can include: voice devices, streaming media devices, web browsing devices, mission-critical devices, low-power devices, Internet devices, sensor devices, and/or IOE devices. The above provides additional descriptions about service profiles, device types, and operable services, so they will not be repeated. Those skilled in the art to which the present invention pertains will also understand that the memory 1714 may also include various other storage modules 1732. The other storage module 1732 may be configured to store information therein and read information therefrom, which information relates to any of the features, functions, methods, procedures, operations, and/or aspects described herein with reference to the RAN node.

Those with ordinary knowledge in the field of the present invention will also understand that the processing system 1701 may include alternative and/or additional elements without departing from the scope of protection of the content of the case. According to some aspects of the content of the present case, the element, or any part of the element, or any combination of the elements may be implemented using a processing system 1701 including one or more processors 1704. Examples of one or more processors 1704 include microprocessors, microcontrollers, digital signal processors (DSP), field programmable gate arrays (FPGA), programmable gate arrays (FPGA), Programming logic device (PLD), State machines, gated logic units, individual hardware circuits, and other appropriate hardware. The processing system 1701 can be implemented using a bus architecture generally represented by a bus 1703 and a bus interface 1708. The busbar 1703 may include any number of interconnecting busbars and bridges, depending on the specific application of the processing system 1701 and the overall design constraints. The bus 1703 can connect various circuits including one or more processors 1704, a memory 1714, and a computer-readable medium 1707 together. The bus 1703 can also be connected to various other circuits known in the art, such as timing sources, peripheral devices, voltage regulators, and power management circuits.

One or more processors 1704 may be responsible for managing the bus 1703 and general processing, including the execution of software stored on a computer-readable medium 1706. The software, when executed by one or more processors 1704, causes the processing system 1701 to perform various functions described below for any one or more devices. The computer-readable medium 1706 can also be used to store data manipulated by one or more processors 1704 when executing software. Whether it is called software, firmware, intermediary software, microcode, hardware description language, or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code snippets, program codes, programs, and vice-versa. Programs, software modules, applications, software applications, packaged software, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc. The software may be located on a computer readable medium 1706. The computer-readable medium 1706 may be a non-transitory computer-readable medium. By way of example, non-transitory computer-readable media include magnetic storage devices (such as hard disks, floppy disks, magnetic strips), optical disks (such as , Compact disc (CD), digital versatile disc (DVD), smart card, flash memory device (for example, card, stick or key disk)), random access Memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electronically erasable PROM (EEPROM), scratchpad, removable disk and any Other appropriate media. By way of example, the computer-readable medium 1706 may also include carrier waves, transmission lines, and any other suitable media for transmitting software and/or instructions that can be accessed and read by a computer. The computer-readable medium 1706 may be located in the processing system 1701, external to the processing system 1701, or distributed across multiple entities including the processing system 1701. The computer readable medium 1706 may be embodied in a computer program product. By way of example and not limitation, the computer program product may include the computer readable medium in the packaging material. Those with ordinary knowledge in the field to which the present invention pertains will recognize how to best implement the functions described throughout the content of this case based on specific applications and the overall design constraints imposed on the entire system.

Hardware implementation of the service node

FIG. 18 is a diagram illustrating an example of a hardware implementation of the service node 1800 including the processing system 1801. By way of example and not limitation, the service node 1800 described herein with reference to FIG. 18 may be the same as the service node described herein with reference to FIG. 1, FIG. 2, FIG. 7, FIG. 8, FIG. 9, FIG. 10, FIG. 11, and/or FIG. 112 and 1112 are the same. The processing system 1801 may include a transceiver 1810. The transceiver 1810 may be configured to receive data and/or send data when communicating with another device. The transceiver 1810 provides a unit for communicating with another device via a wired and/or wireless transmission medium. The transceiver 1810 can be configured to use various types of technologies to perform this type of communication. Those with ordinary knowledge in the field to which the present invention pertains will understand that many types of technologies for performing this type of communication can be used without departing from the scope of protection of the content of the case. Processing system 1801 also It may include a memory 1814, one or more processors 1804, a computer-readable medium 1806, and a bus interface 1808. The bus interface 1808 can provide an interface between the bus 1803 and the transceiver 1810. The memory 1814, one or more processors 1804, the computer-readable medium 1806, and the bus interface 1808 may be connected together via the bus 1803. The processor 1804 may be communicatively coupled to the transceiver 1810 and/or the memory 1814.

The processor 1804 may include a receiving circuit 1820, a control circuit 1821, a transmission circuit 1822, and/or other circuits 1823. Generally, the receiving circuit 1820, the control circuit 1821, the transmission circuit 1822, and/or other circuits 1823 may individually or collectively include various hardware components and/or software modules, and these various hardware components and/or software modules may be Perform and/or implement any one or more of the functions, methods, operations, procedures, features, and/or aspects described herein with reference to the service node.

The receiving circuit 1820 may be configured to use the transceiver 1810 to receive a request for establishing an interface between the RAN node and the serving node from the RAN node. For example, as illustrated in FIG. 9, the service node 112 may receive an S1 setup request 902 from the RAN node 106 to establish an interface between the RAN node 106 and the service node 112. The transmission circuit 1822 may be configured to use the transceiver 1810 to send a response including information related to one or more service profiles supported by the service node. For example, as illustrated in FIG. 9, the service node 112 may send an S1 setup response 904 to the RAN node 106, and the S1 setup response 904 may include information related to the service profile supported by the service node 112.

Such information can be provided in various configurations without departing from the scope of protection of the content of the case. In some configurations, this type of information can indicate One or more RATs supported by the serving node. The service profile may indicate one or more device types supported by the service node. In some other configurations, such information may include one or more device identifier prefixes supported by the service node. The service profile of the service node can be provided in various configurations without departing from the protection scope of the content of this case. The service profile may indicate one or more service profiles supported by the service node. The above provides an additional description of the service profile, so it will not be repeated.

The receiving circuit 1820 may be configured to use the transceiver 1810 to receive the connection request message from the RAN node. For example, as illustrated in FIG. 10, the serving node 112 may receive the attach request 106 from the RAN node 106. The connection request message can be configured to establish communication with the UE. The connection request message may include a service profile corresponding to the UE. The control circuit 1821 may be configured to decide an identifier for the UE. The identifier may be a function of the service profile corresponding to the UE. In some configurations, the transmission circuit 1822 may be configured to use the transceiver 1810 to send a connection acceptance message to the RAN node. The connection acceptance message may include an identifier for the UE. For example, as illustrated in FIG. 10, the serving node 112 may send an attach accept 1008, and the attach accept 1008 may include an identifier for the UE 102.

In some cases, the service profile of the UE may change. For example, the UE may have a variation of one or more device types of the UE and/or one or more services operable at the UE. In such a case, the receiving circuit 1820 may be configured to use the transceiver 1810 to receive a message indicating the update of the service profile corresponding to the UE. For example, as illustrated in FIG. 11, the service node 112 may receive the context request 1108. The control circuit 1821 may be configured to determine the received The message indicates that the serving node no longer supports the UE. For example, as illustrated in FIG. 11, the serving node 112 may determine that the serving node 112 no longer supports the updated service profile of the UE 102. Therefore, the transmission circuit 1822 may be configured to use the transceiver 1810 to send information to another service node that supports the updated service profile corresponding to the UE. For example, as illustrated in FIG. 11, the serving node 1112 may support the updated service profile corresponding to the UE 102. In this way, the service node 112 can send a context response 1110 to the service node 1112. In some configurations, the transmission circuit may also be configured to use the transceiver 1810 to send information for the UE to the RAN node for indicating other service nodes (for example, the service node 1112) for the UE.

The foregoing description provides a non-limiting example of the processor 1804 of the processing system 1801. Although various circuits have been described above, those skilled in the art to which the present invention pertains will understand that the processor 1804 may also include various other circuits 1823 that supplement or replace the circuits 1820, 1821, 1822. Such other circuits 1823 may provide units for executing any one or more of the functions, methods, operations, procedures, features, and/or aspects described herein with reference to the service node.

The computer-readable medium 1806 includes various computer-executable instructions. The computer executable code can be executed by various hardware components of the processing system 1801 (for example, the processor 1804 or any one or more of its circuits 1820, 1821, 1822, 1823). Instructions can be part of various software programs and/or software modules. The computer-readable medium 1806 may include receiving instructions 1840, control instructions 1841, transmission instructions 1842, and/or other instructions 1843. Generally, receive instructions 1840, control instructions 1841, transmit instructions 1842, and/or other instructions 1843 It may be individually or collectively configured to execute and/or implement any one or more of the functions, methods, operations, procedures, features, and/or aspects described herein with reference to the service node.

The receiving instruction 1840 may include a request configured to receive a computer-executable instruction for establishing an interface between the RAN node and the service node from the RAN node. For example, as illustrated in FIG. 9, the service node 112 may receive an S1 setup request 902 from the RAN node 106 to establish an interface between the RAN node 106 and the service node 112. The transmission instructions 1842 may include computer-executable instructions configured to send a response including information related to one or more service profiles supported by the service node. For example, as illustrated in FIG. 9, the service node 112 may send an S1 setup response 904 to the RAN node 106, and the S1 setup response 904 may include information related to the service profile supported by the service node 112.

Such information can be provided in various configurations without departing from the scope of protection of the content of the case. In some configurations, such information may indicate one or more RATs supported by the serving node. The service profile may indicate one or more device types supported by the service node. In some other configurations, such information may include one or more device identifier prefixes supported by the service node. The service profile of the service node can be provided in various configurations without departing from the protection scope of the content of this case. The service profile may indicate one or more service profiles supported by the service node. The above provides an additional description of the service profile, so it will not be repeated.

The receiving instruction 1840 may include a computer-executable instruction configured to receive a connection request message from the RAN node. For example, as illustrated in FIG. 10, the serving node 112 may receive the attach request 106 from the RAN node 106. Connection request The message can be configured to establish communication with the UE. The connection request message may include a service profile corresponding to the UE. The control instructions 1841 may include computer-executable instructions configured to determine an identifier for the UE. The identifier may be a function of the service profile corresponding to the UE. In some configurations, the transmission instructions 1842 may include computer-executable instructions configured to send a connection acceptance message to the RAN node. The connection acceptance message may include an identifier for the UE. For example, as illustrated in FIG. 10, the serving node 112 may send an attach accept 1008, and the attach accept 1008 may include an identifier for the UE 102.

In some cases, the service profile of the UE may change. For example, the UE may have a variation of one or more device types of the UE and/or one or more services operable at the UE. In such cases, the receiving instructions 1840 may include computer-executable instructions configured to receive a message indicating an update of the service profile corresponding to the UE. For example, as illustrated in FIG. 11, the service node 112 may receive the context request 1108. The control instructions 1841 may include computer-executable instructions configured to determine that the received message indicates that the serving node no longer supports the UE. For example, as illustrated in FIG. 11, the serving node 112 may determine that the serving node 112 no longer supports the updated service profile of the UE 102. Therefore, the transmission instructions 1842 may include computer-executable instructions configured to send information to another service node that supports the updated service profile corresponding to the UE. For example, as illustrated in FIG. 11, the new serving node 1112 may support the updated service profile corresponding to the UE 102. In this way, the service node 112 can send a context response 1110 to the new service node 1112. In some configurations, the transmission circuit may also be configured to use the transceiver 1810 to send the UE to the RAN node for instructing other service nodes for the UE (for example, the new service node 1112). News.

The foregoing description provides a non-limiting example of the computer-readable medium 1806 of the processing system 1801. Although various instructions (for example, computer executable code) have been described above, those skilled in the art to which the present invention pertains will understand that the computer readable medium 1806 may also include supplementary or alternative instructions 1840, 1841, 1842 Of various other instructions 1843. Such other instructions 1843 may include computer executable code configured to execute any one or more of the functions, methods, programs, operations, features, and/or aspects described herein with reference to the service node.

The memory 1814 may include various storage modules. The storage module can be configured to store and read various values and/or information from the processor 1804 or any of its circuits 1820, 1821, 1822, 1823. The storage module can also be configured to store and read various values and/or information when the computer executable code is executed. The computer executable code is included in the computer readable medium 1806 or its instructions 1840, 1841. Any instructions in 1842, 1843. In some configurations, the memory 1814 may include service profile information 1830. The service profile information 1830 may include data about the service profile. The service profile may be configured to indicate one or more device types of any device and/or one or more services operable at that device. As described in more detail above, the service profile of a device may include an implicit indication of the device type of such a device and/or explicit information configured to indicate the device type of the device. Device types can include voice devices, streaming media devices, web browsing devices, mission-critical devices, low-power devices, Internet devices, sensor devices, and/or IOE devices. The above provides information about service profiles, device types, and operable services. Additional description of the service, so it will not be repeated. Those skilled in the art to which the present invention pertains will also understand that the memory 1814 may also include various other storage modules 1832. The other storage module 1832 may be configured to store information therein and read information therefrom, which information relates to any of the features, functions, methods, procedures, operations, and/or aspects described herein with reference to the service node.

Those with ordinary knowledge in the field of the present invention will also understand that the processing system 1801 may include alternative and/or additional elements without departing from the scope of protection of the content of the case. According to some aspects of the content of the present case, the element, or any part of the element, or any combination of the elements may be implemented by a processing system 1801 including one or more processors 1804. Examples of one or more processors 1804 include microprocessors, microcontrollers, digital signal processors (DSP), field programmable gate arrays (FPGA), programmable gate arrays (FPGA), Programming logic devices (PLD), state machines, gated logic units, individual hardware circuits, and other appropriate hardware. The processing system 1801 can be implemented using a bus architecture generally represented by a bus 1803 and a bus interface 1808. The bus bar 1803 may include any number of interconnecting bus bars and bridges, depending on the specific application of the processing system 1801 and the overall design constraints. The bus 1803 can connect various circuits including one or more processors 1804, a memory 1814, and a computer-readable medium 1808 together. The bus 1803 can also be connected to various other circuits known in the art, such as timing sources, peripheral devices, voltage regulators, and power management circuits.

One or more processors 1804 may be responsible for managing the bus 1803 and general processing, including the execution of software stored on the computer readable medium 1806 . The software, when executed by one or more processors 1804, enables the processing system 1801 to perform various functions described below for any one or more devices. The computer-readable medium 1806 can also be used to store data manipulated by one or more processors 1804 when executing software. Whether it is called software, firmware, intermediary software, microcode, hardware description language, or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code snippets, program codes, programs, and vice-versa. Programs, software modules, applications, software applications, packaged software, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc. The software may be located on a computer readable medium 1806. The computer-readable medium 1806 may be a non-transitory computer-readable medium. By way of example, non-transitory computer-readable media include magnetic storage devices (such as hard disks, floppy disks, magnetic strips), optical disks (such as , Compact disc (CD), digital versatile disc (DVD), smart card, flash memory device (for example, card, stick or key disk)), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electronically erasable PROM (EEPROM), scratchpad, removable disk and any other appropriate media. By way of example, the computer-readable medium 1806 may also include carrier waves, transmission lines, and any other suitable media for sending software and/or instructions that can be accessed and read by a computer. The computer-readable medium 1806 may be located in the processing system 1801, external to the processing system 1801, or distributed across multiple entities including the processing system 1801. The computer readable medium 1806 may be embodied in a computer program product. By way of example and not limitation, the computer program product may include the computer readable medium in the packaging material. Those with general knowledge in the field to which the present invention belongs It will be recognized how to best implement the functions described throughout the content of this case, depending on the specific application and the overall design constraints imposed on the entire system.

One or more of the components, steps, features, and/or functions illustrated in FIGS. 12 to 15 may be rearranged and/or combined into a single component, step, feature, or function, or be embodied in several components, Step or function. Without departing from the novel features disclosed herein, additional elements, components, steps and/or functions can also be added. The apparatuses, devices, and/or components illustrated in FIGS. 12-15 may be configured to perform one or more of the methods, features, or steps described herein. The novel algorithms described in this article can also be effectively implemented in software and/or embedded in hardware. It should be understood that the specific order or hierarchy of steps in the disclosed method is only an illustration of an exemplary procedure. It should be understood that the specific order or hierarchy of steps in the method can be rearranged based on design preferences. The attached method request item introduces the elements of each step in a sampling order, but unless it is clearly recorded therein, it does not mean that it is limited to the specific order or level introduced.

As mentioned above, several aspects of the telecommunication system described herein have been introduced with reference to the LTE system. As those with ordinary knowledge in the field of the present invention will be easily aware, the various aspects described throughout the content of this case can be extended to other telecommunication systems, network architectures and communication standards, including 5G systems or those defined by 3GPP or other standards bodies. Other appropriate systems. The actual telecommunication standard, network architecture, and/or communication standard used may depend on the specific application and the overall design constraints imposed on the system.

In the content of this case, the term "exemplary" is used to mean "serving as an example, example, or illustration." Any implementation described as "exemplary" in this article The style or aspect need not be construed as being preferable to or more advantageous than other aspects of the content of the case. Similarly, the term "aspect" does not require all aspects of the content of the case to include the discussed features, advantages or modes of operation. The term "coupling" is used herein to represent a direct or indirect coupling between two objects. For example, if the object A physically contacts the object B, and the object B contacts the object C, then the object A and the object C can still be considered to be coupled to each other, even if they are not directly in physical contact with each other. For example, in a package, the first die can be coupled to the second die even though the first die never physically contacts the second die directly. The terms "circuit" and "circuit" are widely used and are intended to include both the hardware implementation of electrical equipment and conductors and the software implementation of information and instructions. When these electrical equipment and conductors are connected and configured, Realize the execution of the functions described in the content of this case (there are no restrictions such as the type of electronic circuit), and when the information and instructions are executed by the processor, realize the execution of the functions described in the content of this case.

The foregoing description is provided to enable anyone with ordinary knowledge in the field to which the present invention pertains to practice some aspects described herein. Various modifications to these aspects will be obvious, and the general principles defined herein can be applied to other aspects. Therefore, the claim is not intended to be limited to the state shown in this article, but is consistent with the full scope of the language of the claim, where unless specifically stated otherwise, quoting an element in the singular does not intend to mean " One and only one" but "one or more". Unless specifically stated otherwise, the term "some" refers to one or more. The phrase referring to "at least one of" the list of items refers to any combination of those items, which includes a single member. As an example, "at least one of a, b, or c" is meant to cover a ; B; c; a and b; a and c; b and c; and a, b, and c. All the structural and functional equivalents of some aspects of the elements described throughout the content of this case are expressly incorporated herein by reference and are intended to be covered by the claims. These structural and functional equivalents have common knowledge in the field to which the present invention belongs. It is well-known or will be well-known. In addition, none of the contents disclosed in this article is intended to be dedicated to the public, regardless of whether such disclosures are clearly recorded in the scope of the patent application. No element of a claim shall be interpreted in accordance with the provisions of Article 19, Item 4 of the Enforcement Rules of the Patent Law, unless the element is clearly stated using a measure of "unit for ...", or in the case of a method claim Below, this element is described using the wording "steps for...".