US20190150225A1

Movatterモバイル変換

Info

Publication number: US20190150225A1
Application number: US16/301,881
Authority: US
Inventors: Ahmed Mohamed; Michael F. Starsinic; Qing Li
Original assignee: Convida Wireless LLC
Current assignee: InterDigital Patent Holdings Inc
Priority date: 2016-05-17
Filing date: 2017-05-17
Publication date: 2019-05-16
Also published as: WO2017201157A1; KR102162732B1; US20230017009A1; EP3459316A1; JP2019519983A; CN115623609A; US12284726B2; KR20190007479A; JP6738908B2; CN109315003A

Abstract

A user equipment device (UE) initiates the creation of a dedicated bearer between a local gateway (L-GW) and a packet data network gateway (P-GW). A GTP tunnel is established to connect the L-GW, a serving gateway (S-GW), and the P-GW. The L-GW and P-GW apply Network Address Translation (NAT) and/or Traffic Flow Template (TFT) to route the traffic between the LS and a Service Capability Server/Application Server (SCS/AS). Alternatively, an SCS-initiates the bearer creation, and an SCEF manages the creation of the GTP tunnel connecting. The L-GW may be co-located with an Evolved UTRAN Node B (eNB) and/or connected to multiple eNBs which are not co-located with the L-GW.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No. 62/337,504, filed on May 17, 2016, entitled “Enablement Of Direct Connections Between Local Servers And Service Capability Servers/Application Servers Over 3GPP Mobile Core Networks”, the content of which is hereby incorporated by reference in its entirety.

BACKGROUND

Machine-to-machine (M2M) systems, also called Internet-of-Things (IoT) or web of things (WoT) systems, often incorporate multiple interconnected heterogeneous networks in which various networking protocols are used to support diverse devices, applications, and services. These protocols have different functions and features, each optimized for one situation or another. There is no one-size-fits-all solution due to the diversity of devices, applications, services, and circumstances.

Various standards and proposed protocols, such as 3GPP and oneM2M, describe methods for various entities to establish connections and communicate at various layers of operation. Such an entity may be, for example, a local, serving, or packet data network gateway (L-GW, S-GW, or P-GW), user equipment (UE), application server (AS), a service capability server (SCS), a mobility management entity (MME), an evolved UTRAN node B (eNB), a service capability exposure function (SCEF), or a home subscriber server (HSS). Layers of operation may include, for example, evolved packet core (EPC)/AS(SCS) interfaces, 3GPP Core Network and Service Layer. Operations may involve the use of a local data plane and may use tunneling protocol such as general packet radio service tunneling protocol (GTP).

SUMMARY

BRIEF DESCRIPTION OF THE FIGURES

A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings.

FIG. 1 is a block diagram that shows an example (S)Gi-LAN in relation to a mobile network operator (MNO) domain and the public Internet.

FIG. 2 is an example call flow for a method for UE-requested bearer resource modification.

FIGS. 3 and 4 depict an example call flow for a method for dedicated bearer activation.

FIGS. 5-7 depict an example call flow for a method of establishing UE-requested PDN connectivity.

FIG. 8 shows an example architecture for a LIPA L-GW co-located with an HeNB.

FIG. 9 is an example call flow for a network-triggered service request method.

FIG. 10 is an example of a 3GPP SCEF architecture.

FIG. 11 is an example network architecture showing LGW-PGW bearer/PDN connections.

FIGS. 12 and 13 depict an example call flow for a UE-initiated LGW-PGW bearer creation method.

FIG. 14 depicts example IP address allocations to an AE, LS, and SCS.

FIG. 15 depicts the relationship of data in packets for the downlink of NAT data from an SCS.

FIG. 16 depicts the relationship of data in packets for the uplink of NAT data to an SCS.

FIGS. 17 and 18 depict an example call flow for a UE-initiated LGW-PGW session creation method.

FIG. 19 depicts the relationship of data in packets for the downlink of NAT data to an L-GW.

FIG. 20 depicts the relationship of data in packets for the uplink of NAT data from an L-GW.

FIG. 21 is an example network architecture in which multiple eNBs connected to one L-GW.

FIGS. 22-24 depict example call flows for an SCEF-initiated LGW-PGW bearer creation method.

FIGS. 25-27 depict example call flows for an SCEF-initiated LGW-PGW session creation method.

FIG. 28 is an example call flow for conveying port number to an LS and an SCS over a user plane for UE-initiated methods.

FIG. 29 is an example call flow for conveying port number to an LS for SCS-initiated methods.

FIG. 30 is an example graphical user interface.

FIG. 31 is a system diagram of an example machine-to-machine (M2M), Internet of Things (IoT), or Web of Things (WoT) communication system in which one or more disclosed embodiments may be implemented.

FIG. 32 is a system diagram of an example architecture that may be used within the M2M/IoT/WoT communications system illustrated inFIG. 31.

FIG. 33 is a system diagram of an example communication network node, such as an M2M/IoT/WoT device, gateway, or server that may be used within the communications system illustrated inFIGS. 31 and 32.

FIG. 34 is a block diagram of an example computing system in which a node of the communication system ofFIGS. 31 and 32 may be embodied.

FIG. 35 illustrates an example communications system.

FIG. 36 is a block diagram of an example apparatus or device configured for wireless communications such as, for example, a wireless transmit/receive unit (WTRU).

FIG. 37 is a system diagram of a first example radio access network (RAN) and core network.

FIG. 38 is a system diagram of a second example RAN.

FIG. 39 is a system diagram of a third example radio access network RAN.

FIG. 40 is a system diagram of a third example radio access network RAN.

DETAILED DESCRIPTION

Referring toFIG. 1, the (S)Gi-LAN3402 is a packet data network (PDN) that is between the Internet3403 and the General Packet Radio Service (GPRS) Support Node (GGSN) or PDN Gateway (P-GW) GGSN/P-GW3404. P-GW/GGSN3404) of the Mobile Corenetwork3401. The (S)Gi-LAN3402 is under control of the Mobile Network Operator (MNO) inoperator domain3401. When uplink data packets leave the (S)Gi-LAN3402 toward the Internet3403, they are no longer under control of the MNO and the packets can be generally considered to have gone to thepublic Internet3403. The (S)Gi-LAN3402 may include Value Added Services (VASs). Examples of VASs include Network Address Translations (NATs), Firewalls, Video Compression, Data Compression, load balancers, HTTP Header Enrichment functions, Transmission Control Protocol (TCP) optimizers, etc. Generally, Deep Packet Inspection (DPI) techniques determine if each Value Added Service (VAS) should operate on a given data flow. Traffic may be routed to or from the (S)Gi-LAN3402 and Servers in thepublic Internet3403 such as a machine-to-machine (M2M)Server3406 for example.

The concepts presented here may also be applied, e.g., to a 5G network. The application server (AS) or service capability server (SCS) may also be called an application function. The ideas that apply to the P-GW may also be applied to a User Plane Function (UPF). The ideas that apply to the MME may also be applied to a Access and Mobility Function (AMF). The ideas that apply to the HSS may also be applied to a User Data Management Function (UDM). The ideas that apply to the SCEF may also be applied to a Network Exposure Function (NEF). The ideas that apply to the eNB may also be applied to a 5G base station.

In general, once a UE has attached to an EPC network and established a PDN connection and a LIPA PDN connection, the UE may initiate a process to establish a connection, such as a dedicated bearer or a new PDN connection, between the L-GW and the P-GW that may be used by an LS or SCS/AS. This may be done in a number of ways. For example, the amount of signaling to the UE may be minimized, e.g., if no radio resources need to be reserved for the UE. Further, an SCS/AS may similarly initiate bearer creation and session creation.

At times, it would be beneficial for a network, such as a 3GPP network, to establish a direct connection between a local server (LS) and an application server (AS) for the benefit of a user of a user equipment device (UE). For example, the user may be a mobile subscriber who requests a service from an AS, where the AS is accessed via a Mobile Core Network (MCN). The subscriber may connect to the AS via a base station that is associated with a local network. The local network may host Local Servers (LS), e.g., an IN-CSE or MN-CSE, that is aware of local context information. In many cases it would be advantageous for the LS to be able to share this local context information with the remote AS. For example, the user may be subscribed to an advertisement service at a backend AS. In such a subscription, the user identifies the type of advertisements that interests him or her. Advertisements that are not of interest should be filtered out by the backend AS and should not reach the mobile subscriber. Then, when the user visits a shopping mall and he or she may get connected to the shopping mall small cells over a LIPA connection. The small cells may provide access to the Internet as well as to multiple local servers. A local advertisement LS is not permitted to send its local advertisements directly to the mobile subscriber. Instead, it has to send its advertisements to the backend AS, which will filter them first according to the user preferences, then forward the recommended ones to the UE.

There is no connection through a standard EPC between an LS and an SCS/AS. An LS and SCS/AS can communicate outside of the EPC network via Internet. However, a non-EPC connection is not preferred from an operator's value added service perspective, given that the information will traverse non-3GPP networks. Therefore, it is preferred that information be conveyed from LS to SCS/AS and vice versa over the operator's EPC. To achieve this, a PDN connection or dedicated bearer between LS and SCS/AS may be initiated by either the UE or an SCS/AS.

This may be accomplished in a number of ways. For example, a UE may initiate a request for dedicated bearer between an L-GW and a P-GW such that the connection will be associated with the UE. Similarly, the UE may initiate a new PDN connection request between the L-GW and P-GW such that the connection will be associated with the UE. Likewise, SCS/AS may initiate a request for a dedicated bearer or PDN connection between the LS and SCS/AS such that the connection will be associated with the SCS/AS.

Table 1 provides expansions of many acronyms used in describing the methods and apparatuses discussed herein.

TABLE 1

Acronyms and Abbreviations.

	AAA	Authentication, Authorization, and Accounting
	AE	Application Entity
	AESE	Architecture Enhancements for Service Capability
		Exposure
	APN	Access Point Name
	API	Application Program Interface
	AS	Application Server
	eNB	Evolved UTRAN Node B
	EPC	Evolved Packet Core
	EPS	Evolved Packet System
	GGSN	Gateway GPRS Support Node
	GPRS	General packet radio service
	GTP	GPRS Tunneling Protocol
	HeNB	Home eNB (an LTE femtocell or Small Cell)
	HLR	Home Location Register
	HSS	Home Subscriber Server
	IE	Information Element
	IMSI	International Mobile Subscriber Identity
	L-GW	Local Gateway
	LGW-PGW	Local Gateway to Packet Data Network Gateway
	LBI	Linked Bearer Identifier
	LIPA	Local Internet Protocol Access
	LIPA-APN	LIPA Access Point Name
	LTE	Long Term Evolution
	LS	Local Server
	MCN	Mobile Core Network
	MME	Mobility Management Entity
	MSC	Mobile Switching Center
	NAS	Non Access Stratum
	NAT	Network Address Translation
	PCRF	Policy and Charging Rules Function
	PDN	Packet Data Network
	PTI	Procedure Transaction Identifier
	P-GW	Packet Data Network Gateway
	QoS	Quality of Service
	RAN	Radio Access Network
	RAT	Radio Access Technology
	RRC	Radio Resource Control
	SCS	Service Capability Server
	SCEF	Service Capability Exposure Function
	(S)Gi-LAN	LAN between the GGSN/P-GW and the Internet
	SGSN	Serving GPRS Support Node
	S-GW	Serving Gateway
	TAD	Traffic Aggregate Description
	TFT	Traffic Flow Template
	UE	User Equipment

FIGS. 2-10 depict call flows and architectures, based on standards and proposed standards, that may be adapted to effect the UE and SCS/AS initiated connection creation methods described here.

FIG. 2 is a call flow for an example method for UE-requested bearer resource modification. A UE may request a modification of bearer resources using the “UE requested bearer resource modification” procedure, as explained in clause 5.4.5 of 3GPP TS 23.401, “General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access,” V12.4.0, March 2014. Such a request may be used to request a new Quality of Service (QoS) or modify particular packet filters. The UE may accept such request and invoke dedicated bearer activation/deactivation or modification procedures TS 23.401.

FIGS. 3 and 4 depict an example call flow for dedicated bearer activation. The PDN-GW may invoke a “dedicated bearer activation” procedure, based on a UE's request (Section 2.2) as explained in clause 5.4.1 of TS 23.401. The dedicated bearer will be established over the same existing default PDN connection between the UE and PDN-GW. Such dedicated bearer will have associated packet filters, which will be stored in a Traffic Flow Template (TFT). The TFT will be used to traffic the intended packets over the dedicated bearer, as opposed to the default bearer.

FIGS. 6-7 depict an example call flow for a method of establishing UE-requested PDN connectivity. Unlike the bearer resource modification procedure described in reference toFIG. 2, here, a UE may request a new PDN connection as described in clause 5.10.2 of TS 23.401. In response, a default bearer will be activated over the new PDN connection. Furthermore, the P-GW will assign a new IP address to the UE over the new PDN connection.

LIPA enables a UE to access the available local IP services via a HeNB and a Local Gateway (L-GW), without the user plane traversing the mobile operator's network, except the HeNB, per clause 4.4.16 of TS 23.401.FIG. 8 depicts an example LIPA architecture for HeNB co-located with L-GW, which is currently the only scenario standardized for LIPA, per clause 4.4.9 of TS 23.401. A direct user plane is established between the HeNB and L-GW which is managed via a Correlation ID parameter. More precisely, the HeNB uses the Correlation ID to match the radio bearers (from the UE) with the direct user plane connections (from the L-GW). There is no support for LIPA dedicated bearer activation.

InFIG. 8, there is an S5 reference point between the L-GW and S-GW. Such a reference point is utilized in case the L-GW has downlink data to a UE, which is in ECM-IDLE state. In other words, when a local server (LS), not shown inFIG. 8, sends downlink data towards the L-GW and the target UE is in the ECM-IDLE state, the L-GW sends the first downlink packet to the S-GW. Accordingly, the S-GW triggers the MME to page the UE. Once the UE is in ECM-CONNECTED state, downlink data flows directly from the L-GW to the UE through the HeNB. SeeFIG. 9 and in clause 5.3.4.3 of TS 23.401.

3GPP has a framework to expose underlying network capabilities to application/service providers in 3GPP TS 23.682, “Architecture Enhancements to facilitate communications with Packet Data Networks and Applications”. This includes a function called a Service Capability Exposure Function (SCEF). The SCEF provides access to network capabilities through homogenous network application programming interfaces (e.g. Network API) defined by OMA, GSMA, and possibly other standardization bodies. The SCEF abstracts the services from the underlying 3GPP network interfaces and protocols.FIG. 10 is an example architecture showing an SCEF in relation to applications and an EPC. Although not shown inFIG. 10, a GMLC may be one of the Network Entities that may connect to the SCEF.

FIG. 11 shows an example network architecture showing LGW-PGW bearer/PDN connection. The UE has a default PDN connection with a default bearer to the SCS/AS. The UE also has a LIPA PDN connection. A tunnel between the L-GW and P-GW may be created such that the tunnel is associated with a particular SCS/AS or UE.

FIGS. 12 and 13 show an example call flow whereby a UE initiates an LGW-PGW bearer creation. The UE may be aware that there is an LS that could share context information with an AS/SCS associated with the UE. For example, an LS may be able to tell the SCS/AS what stores are in close proximity to the UE so that the SCS/AS can push coupon offers to the UE. In such a situation, it is advantageous for the LS to be able to send data to the SCS/AS.

A UE may initiate an LGW-PGW bearer creation, with a minimum of radio signaling to the UE, via modification of the method for “UE Requested Bearer Resource Modification” described in clause 5.4.5 of TS 23.401 to establish a dedicated bearer between the UE and P-GW. Here, a bearer is established between the L-GW and P-GW instead.

Referring toFIG. 12, instep0, a default PDN connection is established between the UE and the P-GW. Further, a LIPA connection is established between the UE and the L-GW. Consequently, the UE has two IP addresses: a public IP address that was allocated by the P-GW, and an LIPA IP address that was allocated by the L-GW.FIG. 13 illustrates the IP address allocations of the UE, LS, and SCS.

Referring again toFIG. 12, instep1 the UE forms a Traffic Aggregate Description (TAD) that indicates that any data packet assigned to LS-PORT-NUM X should be sent over a new dedicated bearer. For example, while in communication with LS, the UE may recognize that it could benefit by allowing the LS to send context information to the SCS/AS directly. The UE may then decide that it wants to allow the LS to communicate with the SCS/AS so that context information can be sent to SCS/AS. The UE and LS may negotiate a port number that will be used for LS-to-SCS/AS communication, the LS may inform the UE of what port number will be used, or the UE may inform the LS of what port number will be used for LS-to-SCS/AS communication. Alternatively, a well-known port number may be used.

Next the UE sends an RRC “UL Information Transfer” (NAS-PDU)message2A from the UE to the eNB.Message2A contains NAS-PDU “Request Bearer Resource Modification” (LBI, PTI, EPS Bearer Identity, QoS, TAD, Bind-To-LGW-Flag, LS-IP-ADDRESS, Protocol Configuration Options) information. The eNB conveys the UE'sNAS message2A in an S1-AP “Uplink NAS Transport” (NAS-PDU, L-GW Transport Layer Address or Local Home Network ID)message2B. The inclusion of the L-GW address is indicated in clause 8.6.2.3 of 3GPP TS 36.413, “Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (SLAP),” V12.1.0, March 2014. As indicated in Section 5.4.5 of TS 23.401, the UE sends the Linked Bearer Id (LBI) only when the requested operation is “add” to indicate to which PDN connection the additional bearer resource is linked to. The Procedure Transaction Identifier (PTI) is dynamically allocated by the UE for this procedure. The TAD indicates one requested operation (add) and includes the packet filter(s) to be added, which is formed in the previous step. By adding the Bind-To-LGW-Flag IE, the UE is able to inform the MME that this is a special request to create bearer between the L-GW and P-GW. Finally, the LS-IP-ADDRESS is the local (LIPA) IP address of the LS.

The inclusion of the Bind-To-LGW-Flag IE causes the MME to allocate a new bearer ID, namely, LGW-Bearer-ID, to reference the bearer between the L-GW and P-GW. The MME then sends the “Bearer Resource Command” (IMSI, LBI, PTI, EPS Bearer Identity, QoS, TAD, LS-IP-ADDRESS, Protocol Configuration Options, Bind-To-LGW-Flag, LGW-Bearer-ID, L-GW Address or Local Home Network ID)message3 to the S-GW. For convenience, we will refer to the “L-GW Transport Layer Address” as the “L-GW Address”.

The serving gateway (S-GW) forwards the MME message by sending a “Bearer Resource Command” (IMSI, LBI, PTI, EPS Bearer Identity, QoS, TAD, LS-IP-ADDRESS, Protocol Configuration Options, Bind-To-LGW-Flag, LGW-Bearer-ID, L-GW address or Local Home Network ID)message4 to the P-GW.

The P-GW then sends a IP-CAN Session modification (TAD, Bind-To-LGW-Flag, LGW-Bearer-ID)message5 to the PCRF. The ‘Bind-To-LGW-Flag’ is included to indicate to the PCRF that the newly requested bearer is associated with an LS, rather than a UE.

Instep6, the P-GW processes message5. If therequest5 is accepted, the P-GW adds the received TAD from the UE to form an updated Traffic Flow Template (TFT). The TFT will be used to link packet data to be sent over LS-PORT-NUM X to the LGW-Bearer-ID dedicated bearer.

Instep7, the P-GW will create a new Network Address Translation (NAT) entry indicating that if data to be sent over LS-PORT-NUM X and the destination IP address is the UE's default IP address (UE-IP-Address), the local LS IP address (LS-IP-ADDRESS) should be used in place of the UE's IP Address (UE-IP-ADDRESS).

Normally, a NAT is formed in the P-GW. That logical function typically resides in the (S)Gi-LAN. To effect the call flow depicted inFIG. 12, it is not necessary to locate all NAT functionality at the P-GW. Rather, the P-GW need only be responsible for charging the destination IP address of specific traffic flows that match specific TFT rules. In this example, the destination IP address of IP packets that are addressed to the UE's IP address and LS-PORT-NUM will be changed to the local LS IP address (LS-IP-ADDRESS). Alternatively, the P-GW may be allowed to configure an external NAT function with this rule. SeeFIG. 15.

The P-GW then initiates steps similar to the “Dedicated Bearer Activation” procedure of clause 5.4.1.1 of TS 23.401. The P-GW sends a “Create Bearer Request” (IMSI, PTI, EPS Bearer QoS, TFT, P-GW S5 TEID, Charging Id, LBI, Protocol Configuration Options, SCS-IP-ADDRESS, UE-IP-ADDRESS)message8 to the S-GW over the S5 interface. The PTI parameter is included to correlatemessage8 to the request inmessage4. The PTI parameter is only used when the procedure was initiated by a “UE Requested Bearer Resource Modification” procedure, which is the case here. The PTI will be used also in the end of this call flow to inform the UE about the success of the bearer request. Given that the PTI IE exists, there is no need to include the ‘LGW-Bearer-ID’ IE, since the S-GW already knows both IEs.

In turn, the S-GW sends a “Create Bearer Request” (IMSI, PTI, EPS Bearer QoS, TFT, S-GW TEID, P-GW TEID, LBI, Protocol Configuration Options, LGW-Bearer-ID, SCS-IP-ADDRESS, UE-IP-ADDRESS)message9 to the L-GW over the S5 interface. The S1-TEID IE (to eNB), which would normally have been used to identify the eNB to S-GW tunnel, is replaced by an S-GW TEID which identifies an L-GW to S-GW tunnel. Further, ‘LGW-Bearer-ID’, SCS-IP-ADDRESS, and UE-IP-ADDRESS IEs are included in the “Create Bearer Request” message to the L-GW. The PTI is not known by the L-GW, and so having both the PTI and ‘LGW-Bearer-ID’ IEs this message is advantageous. Finally, the TFT is included to carry the TFT rules to the L-GW.

The call flow ofFIG. 12 is continued inFIG. 13. Instep10, the L-GW applies the received TFT to link packet data to be sent over LS-PORT-NUM X to the LGW-Bearer-ID dedicated bearer.

Instep11, the L-GW creates a new NAT entry indicating that, if data is to be sent over the LIPA connection from the LS using LS-PORT-NUM X and the destination IP address is SCS (SCS-IP-ADDRESS), the source Address should be changed to the UE's public IP address (UE-IP-ADDRESS). The SCS-IP-ADDRESS and UE-IPADDRESS were received instep9. This action is illustrated inFIG. 16.

Referring again toFIG. 13, the L-GW acknowledges the bearer activation to the S-GW by sending a “Create Bearer Response” (LGW-Bearer-ID, LGW-TEID)message12 to the S-GW. A GTP tunnel between the L-GW and S-GW is now created.

Next, the S-GW acknowledges the bearer activation to the P-GW by sending a “Create Bearer Response” (LGW-Bearer-ID, SGW-TEID)message13. A GTP tunnel between the P-GW and the S-GW is now created.

As the complete tunnel between the P-GW and the L-GW is now established through the S-GW, the S-GW sends a new “Bearer Resource Response” (LGW-Bearer-ID)message14 to the MME to indicate the success of creating the GTP tunnel between L-GW and P-GW.

The MME conveys the success by sending a NAS “Bearer Resource Modification Response” (PTI, LGW-Bearer-ID)message15 to the eNB, which forwards the success to the UE inmessage16. This message, which is not included in the standard dedicated bearer activation procedure, informs the UE about the success of its request. Prior to receivingmessage16 the UE knows only the PTI, and does not know the LGW-Bearer-ID. Once the UE receives thisresponse message16, identified by the PTI, the UE knows that its request is successful and that the LGW-Bearer-ID is the newly created bearer ID between the L-GW and P-GW. The NAS-PDU is sent first from the MME to the eNB using the S1-AP “Downlink NAS Transport” (NAS-PDU)message15. The NAS-PDU is next forwarded to the UE in the “DL Information Transfer” (NAS-PDU)message16.

Standard protocol messages for “UE requested bearer activation” and “Dedicated bearer activation” procedures may be adapted to support the establishment of a bearer between the L-GW and P-GW. Referring again toFIG. 2, a UE sends an NAS “Request Bearer Resource Modification”message1 to the MME, Here, in addition to the LBI, PTI, EPS Bearer Identity, QoS, TAD, and Protocol Configuration Options information,message1 also includes a Bind-To-LGW-Flag, LIPA-APN, and LS-IP-ADDRESS information. As indicated in Section 5.4.5 of TS 23.401, the UE sends the Linked Bearer Id (LBI) only when the requested operation is add to indicate to which PDN connection the additional bearer resource is linked to. The TAD indicates one requested operation (add) and includes the packet filter(s) to be added. The Bind-To-LGW-Flag tells the MME that this is a special request to create a new bearer. This new bearer will not be used by the UE to send and receive data. Instead, it will be used by a service in the local network to send data via the L-GW. The LIPA-APN is used by the MME to determine the L-GW Identity. The LS-IP-ADDRESS is the IP address of the LS.

Next, the MME sends a “Bearer Resource Command”message2 to the S-GW. Here, in addition to the IMSI, LBI, PTI, EPS Bearer Identity, QoS, TAD, and Protocol Configuration Options,message2 also includes a Bind-To-LGW-Flag, L-GW Address, and an LS-IP-ADDRESS. The Bind-To-LGW-Flag tells the S-GW that this new bearer will be bound to the L-GW. This new bearer will be used by a service in the local network to send data via the L-GW. The L-GW Address, or a Local Home Network ID, identifies the particular L-GW that is associated with the LIPA-APN that was provided inmessage1.

The S-GW sends a BearerResource Command message3 to the P-GW. Here, in addition to the IMSI, LBI, PTI, EPS Bearer Identity, QoS, TAD, and Protocol Configuration Options,message3 includes a Bind-To-LGW-Flag and LS-IP-ADDRESS.

At this point, a dedicated bearer activation procedure will be executed, shown inFIGS. 3 and 4 and described in section 5.4.1 of TS 23.401, with some differences. Here, the messages inFIGS. 3 and 4 include the Bind-To-LGW-Flag, L-GW Address or Local Home Network ID, SCS-IP-ADDRESS, and UE-IP-ADDRESS IE's.

Further, not shown inFIG. 4, afterstep11, the S-GW sends a Create Session Request to the L-GW. The L-GW responds with a Create Session Response to the S-GW (P-GW Address for the user plane, P-GW TEID of the user plane, P-GW TEID of the control plane, PDN Type, PDN Address, EPS Bearer Id, EPS Bearer QoS, Protocol Configuration Options, Charging Id, Prohibit Payload Compression, APN Restriction, Cause, MS Info Change Reporting Action (Start) (if the P-GW decides to receive UE's location information during the session), CSG Information Reporting Action (Start) (if the P-GW decides to receive UE's User CSG information during the session), Presence Reporting Area Action (if the P-GW decides to receive notifications about a change of UE presence in Presence Reporting Area), PDN Charging Pause Enabled indication (if P-GW has chosen to enable the function), APN-AMBR). The NAT at the P-GW and L-GW is similar to what is shown inFIGS. 15 and 16.

FIGS. 17 and 18 show an example call flow whereby a UE initiates the creation of a new connection between an L-GW and a P-GW. The call flow is similar to the “UE Requested PDN Connectivity” method presented in clause 5.10.2 of TS 23.401, with some modifications.

Referring toFIG. 17. Instep0, a default PDN connection is established between a UE and a PDN gateway (P-GW), and a LIPA connection is established between the UE and the L-GW. Consequently, the UE has a public IP address, allocated by the P-GW. Furthermore, the UE has a different local IP address, allocated by the L-GW.

The UE intends to send a NAS-PDU “PDN Connectivity Request” (APN, LIPA-APN, PDN Type, Protocol Configuration Options, Request Type, Bind-To-LGW-Flag) to the MME. This is done in two steps. First the NAS-PDU is carried in an RRC “UL Information Transfer” (NAS-PDU) in message1A from the UE to the eNB. This is indicated in clause 5.6.2 of 3GPP TS 36.331, “Radio Resource Control (RRC) Protocol specification,” V12.1.0, March 2014.

Second, the eNB conveys the UE's NAS information in a S1-AP “Uplink NAS Transport” (NAS-PDU, L-GW Transport Layer Address) message1b. This is indicated in clause 8.6.2.3 of TS 36.413.

In addition, a ‘Bind-To-LGW-Flag’ IE may be used to inform the MME that this is a special request to create a new PDN connection between the L-GW and P-GW. Furthermore, a LIPA-APN IE may be used to indicate the APN of the local service.

From the ‘Bind-To-LGW-Flag’ IE in message1A, the MME understands that this request is related to connection between LGW and P-GW. Accordingly, the MME allocates a special bearer Id (LGW-Bearer-ID) and sendsmessage2 to the S-GW.Message2 contains a “Create Session Request” (IMSI, MSISDN, MME TEID for control plane, RAT type, P-GW address, L-GW Address or Local Home Network ID, Default EPS Bearer QoS, PDN Type, subscribed APN-AMBR, APN, LIPA-APN, LGW-Bearer-ID, Protocol Configuration Options, Handover Indication, ME Identity, User Location Information (ECGI), UE Time Zone, User CSG Information, MS Info Change Reporting support indication, Selection Mode, Charging Characteristics, Trace Reference, Trace Type, Trigger Id, OMC Identity, Maximum APN Restriction, Dual Address Bearer Flag, Bind-To-LGW-Flag). In this way, the MME conveys the LIPA-related parameters (LIPA-APN, L-GW Address or Local Home Network ID) to the S-GW.

Next the S-GW creates a new entry in its EPS Bearer table and sendsmessage3 to the P-GW indicated in the P-GW address received inmessage2.Message3 contains a “Create Session Request” (IMSI, MSISDN, S-GW Address for the user plane, S-GW TEID of the user plane, S-GW TEID of the control plane, RAT type, Default EPS Bearer QoS, PDN Type, subscribed APN-AMBR, APN, LGW-Bearer-ID, Protocol Configuration Options, Handover Indication, ME Identity, User Location Information (ECGI), UE Time Zone, User CSG Information, MS Info Change Reporting support indication, PDN Charging Pause Support indication, Selection Mode, Charging Characteristics, Trace Reference, Trace Type, Trigger Id, OMC Identity, Maximum APN Restriction, Dual Address Bearer Flag, Bind-To-LGW-Flag). There is no need to convey the ‘L-GW Address’ or Local Home Network ID IEs to the P-GW. This information needs to be available at the S-GW.

Inmessage4, the P-GW initiates IP-CAN Session modification to the PCRF carrying the (Bind-To-LGW-Flag, LGW-Bearer-ID) information. The ‘Bind-To-LGW-Flag’ is included to indicate to the PCRF that the newly requested PDN connection is associated with an LS, rather than a UE.

In step5A, the P-GW creates a new entry in its EPS bearer context table and generates a ‘LGW-Charging Id’ for the LGW-Bearer-ID Bearer. The new entry allows the P-GW to route user plane PDUs between the S-GW and the packet data network, and to start charging. Furthermore, the P-GW allocates a new IP address to be assigned to the LS, namely, ‘LS-IP-ADDRESS-new’. The P-GW may include the IP address of the SCS ‘SCS-IP-ADDRESS’, to be used in the NAT function at the L-GW.

The P-GW returns message5B to the S-GW. Message5B contains a “Create Session Response” (P-GW Address for the user plane, P-GW TEID of the user plane, P-GW TEID of the control plane, PDN Type, LS-IPADDRESS-new, LGW-Bearer-ID, EPS Bearer QoS, Protocol Configuration Options, LGW-Charging Id, Prohibit Payload Compression, APN Restriction, Cause, PDN Charging Pause Enabled indication (if P-GW has chosen to enable the function), APN-AMBR, SCS-IP-ADDRESS)S-GW, establishing a GTP tunnel between the S-GW and P-GW.

The call flow ofFIG. 17 is continued inFIG. 18. The S-GW initiates S-GW a GTP tunnel to the L-GW by sending S-GW message6 to the L-GW indicated in the L-GW Address or Local Home Network ID specified inmessage2.Message6 contains a “Create Session Request” (IMSI, MSISDN, S-GW Address for the user plane, S-GW TEID of the user plane, S-GW TEID of the control plane, RAT type, Default EPS Bearer QoS, PDN Type, LS-IP-ADDRESS-new, SCS-IP-ADDRESS, subscribed APN-AMBR, LIPA-APN, LGW-Bearer-ID, Protocol Configuration Options, Handover Indication, ME Identity, User Location Information (ECGI), UE Time Zone, User CSG Information, MS Info Change Reporting support indication, PDN Charging Pause Support indication, Selection Mode, Charging Characteristics, Trace Reference, Trace Type, Trigger Id, OMC Identity, Maximum APN Restriction, Dual Address Bearer Flag, Bind-To-LGW-Flag). The ‘LIPA-APN’ is included in this step as it is targeting a session to the L-GW. Furthermore, the ‘LS-IP-ADDRESS-new’ and ‘SCS-IP-ADDRESS’ IP addresses are included to be used in the NAT construction at the L-GW.

Instep7, the L-GW associates the PDN connection with a new IP address ‘LS-IP-ADDRESS--new’. Normally, this IP address would be used by the UE. However, this IP address will be used by the LS. Accordingly in order to route the traffic between the SCS and LS, the L-GW establish a NAT.FIGS. 19 and 20 illustrate the NAT function that will be performed at the L-GW. The LS-IP-ADDRESS is the local LS IP address over the LIPA connection.

Referring again toFIG. 18, instep7 the L-GW further creates a new entry in its EPS bearer context table. This is analogous to step5A performed by the P-GW. The new entry allows the L-GW to route user plane PDUs between the S-GW and the LIPA packet data network.

Inmessage8, the L-GW returns to the S-GW a “Create Session Response” (L-GW Address or Local Home Network ID for the user plane, L-GW TEID of the user plane, L-GW TEID of the control plane, PDN Type, LGW-Bearer-ID, EPS Bearer QoS, Protocol Configuration Options, Prohibit Payload Compression, APN Restriction, Cause, APN-AMBR), establishing S-GW a GTP tunnel between the S-GW and L-GW. The L-GW will not generate a new charging ID, as the P-GW will be the one responsible for charging the new LGW-P-GW connection using the ‘LGW-Charging Id’ create in steps5A and5B.

Once the S-GW creates a tunnel with the P-GW and L-GW, inmessage9 the S-GW acknowledges the MME's request by sending to the MMW a “Create Session Response” (PDN Type, IP-UE-new, S-GW address for User Plane, S-GW TEID for User Plane, S-GW TEID for control plane, LGW-Bearer-ID, EPS Bearer QoS, P-GW address and TEID, L-GW address or Local Home Network ID, Protocol Configuration Options, Prohibit Payload Compression, APN Restriction, Cause, MS Info Change Reporting Action (Start), CSG Information Reporting Action (Start), Presence Reporting Area Action, APN-AMBR).

The MME acknowledges the UE's request by sending a NAS PDU “PDN Connectivity Accept” (APN, LIPA-APN, PDN Type, IP-UE-new, LGW-Bearer-ID, Session Management Request, Protocol Configuration Options)message10A to eNB.Message10A using an S1-AP “Downlink NAS Transport” (NAS-PDU) format.

The eNB forwards to the NAS-PDU information to the UE in a “DL Information Transfer” (NAS-PDU) message10AB.

When multiple requests are initiated by multiple UEs to establish the same LS-SCS (LGW-PGW) connection, the P-GW accepts the request of the first UE to establish such connection. The subsequent requests are not be executed by the P-GW, and acknowledgements would be sent to the subsequent requesting UEs indicating that the new dedicated bearer or PDN connection is already established. The ‘LGW-Bearer-ID’ is included in such acknowledgement messages.

FIG. 21 shows an example configuration where an L-GW is connected to multiple eNBs. For example, the eNBs may be deployed at Road Side Units (RSUs) distributed across a certain geographic area, where the RSUs are all connected to one L-GW, and where the L-GW in turn is connected to a Location Server (LS), whereby the LS captures and provides information about the area covered by the multiple eNBs.

Referring toFIG. 21, for a LIPA connection to exist between a UE and a L-GW, as discussed in reference toFIGS. 12, 13, 17, and 18, there will be a GTP tunnel between the eNB and L-GW. This is similar to the GTP tunnel that can exist between the eNB and S-GW over the S1-U reference point. Consequently, the eNB knows the L-GW IP address, which is required to construct the GTP tunnel. The L-GW IP address can therefore be used by the eNBs, for UE-initiated LGW-PGW bearer creation and UE-initiated LGW-PWG new PDN connection creation For example, inFIG. 12 the eNB and L-GW are collocated. The eNB conveys the information in the UE'sNAS message2A via the S1-AP “Uplink NAS Transport”message2B, including the NAS-PDU and the L-GW address or Local Home Network ID. In the multiple-eNB scenario ofFIG. 21, the eNB may include the L-GW address or Local Home Network ID in a S1-AP “Uplink NAS Transport” message sent the MME.

FIGS. 22-24 are example call flows of a method by which an SCS may initiate LGW-PGW bearer creation. An SCS/AS requests local information to be provided by a particular local server. The local server is connect to a UE through an existing LIPA connection. The request is initiated by the SCS/AS and managed by the SCEF. To do so, the SCEF communicates with the P-GW (P-GW) and the MME as follows.

Prior to the sending ofmessage1, a default PDN connection is established between the UE and the P-GW. A LIPA connection is established between the UE and the L-GW. Consequently, the UE has a public IP address that is allocated by the P-GW. Furthermore, the UE has a different local IP address that is allocated by the L-GW.

Inmessage1, the SCS/AS starts inquiring about the local information of a given UE, to be provided by an LS, by sending a “Retrieve Local Information Request” (External ID, SCS Identifier, LS-PORT-NUM=X) API to the SCEF. The ‘LS-PORT-NUM’ IE is included to be used to send the local information over LS-PORT-NUM X.

Instep2, the SCEF checks to see if the SCS/AS is authorized to get the local server information about the requested UE. If the SCS/AS is authorized, the SCEF sendsmessage3. Otherwise, the flow stops and the SCEF reports the rejection and its cause to the SCS/AS.

Inmessage3, once the request is authorized, the SCEF sends “Subscriber Information Request” (External ID, SCS Identifier) to the HSS, over the Sh reference point, to obtain the UE's IMSI and to obtain the identities of the UE's serving nodes (e.g. MME).

Inmessage3a, the HSS replies by sending “Subscriber Information Response” (IMSI or External Identifier, Serving nodes) message to the SCEF. The HSS resolves the External Identifier to IMSI and retrieves the related HSS stored routing information including the identities of the UE's serving CN node(s) (MME, SGSN, 3GPP AAA server or MSC). Optionally, the HSS sends the IMSI to the SCEF.

Inmessage4, once the SCEF receives the MME address and UE's identity, the SCEF sends a “Create Bearer Request” (IMSI, Bind-To-LGW-Flag) message to the MME over the T6a reference point. Using a ‘Bind-To-LGW-Flag’ IE, the SCEF is able to inform the MME that this is a special request to create bearer between the L-GW and P-GW, which are associated with the UE, defined by its IMSI.

Instep5, once the MME receives the bearer request initiation, it allocates a new bearer ID, namely, LGW-Bearer-ID, to reference the bearer between the L-GW and P-GW.

In message5a, the MME sends a “Create Bearer Response” (LGW-Bearer-ID, L-GW Address or Local Home Network ID, P-GW ID) message to the SCEF over the Tx reference point. The MME stores the L-GW address or Local Home Network ID, which is periodically received from the eNB in every “Uplink NAS Transport” message.

Inmessage6, once the SCEF has received the P-GW ID, the SCEF sends a “Retrieve Local Information Request” (IMSI, Bind-To-LGW-Flag, LGW-Bearer-ID, L-GW Address or Local Home Network ID, LS-PORT-NUM=X) to the P-GW. In this way, the SCEF informs the P-GW that the SCEF is interested in receiving the local server information over LS-PORT-NUM X from the LS that has a LIPA connection with UE (identified via its IMSI).

The call flow ofFIG. 22 is continued inFIG. 23. Instep7, the P-GW forms an updated TFT indicating that any data packet assigned to LS-PORT-NUM X should be sent over the new dedicated bearer LGW-Bearer-ID received inmessage6.

Inmessage8, the P-GW initiates IP-CAN Session modification by sending a PCRF carrying TAD, Bind-To-LGW-Flag, and LGW-Bearer-ID information. The ‘Bind-To-LGW-Flag’ is included to indicate to the PCRF that the newly requested bearer is associated with an LS, rather than a UE.

Inmessage9, the P-GW initiates a “Dedicated Bearer Activation” procedure similar clause 5.4.1.1 of TS 23.401.Message9 includes a “Create Bearer Request” (IMSI, EPS Bearer QoS, TFT, P-GW S5 TEID, Bind-To-LGW-Flag, LGW-Bearer-ID, L-GW Address or Local Home Network ID, SCS-IP-ADDRESS).Message9 is sent to the S-GW (S-GW) over the S5 reference point. The SCS-IP-ADDRESS denotes the public IP address of the SCS, which is needed for the NAT at the L-GW.

Inmessage10, the S-GW sends the “Create Bearer Request” (IMSI, EPS Bearer QoS, TFT, S-GW TEID, P-GW TEID, Bind-To-LGW-Flag, LGW-Bearer-ID, SCS-IP-ADDRESS) information to the L-GW (defined using the L-GW Address or Local Home Network ID IE) over S5. The TFT is included to carry the TFT rules to the L-GW. Using the ‘Bind-To-LGW-Flag’ IE, the S-GW will be able to inform the L-GW that this is a special request to create bearer (with ID LGW-Bearer-ID) between the L-GW and P-GW.

Steps11-14 are similar to steps10-13 in ofFIG. 13. Here inFIG. 23, the L-GW additionally inserts the ‘LS-IP-ADDRESS’ IE, which is the local LIPA IP address of the LS, to the S-GW and P-GW. The ‘LS-IP-ADDRESS’ IP address is already available at the L-GW, and used over the existing LIPA connection.

The call flow ofFIG. 23 is continued inFIG. 24. Inmessage14, the S-GW informs the P-GW of a new NAT entry. If data is to be sent over LS-PORT-NUM X, and the destination IP address is the typical UE public IP address (IP-UE), in accordance with the NAT the address will now be changed to the local LS IP address (LS-IP-ADDRESS).

Instep15, as the new bearer is now established between the L-GW and P-GW, the PDN-GW indicates so by sending a “Retrieve Location Information Response” message to the SCEF.

Inmessage16, the P-GW sends a “Retrieve Local Information Response” to the SCEF.

Finally, inmessage17, the SCEF responds to the API instep1 by sending the “Retrieve Local Information Response” information to the SCS/AS.

FIGS. 25-27 are example call flows of a method by which an SCS may initiate LGW-PGW PDN connection. An SCS/AS requests the creation of a new PDN connection between the L-GW and P-GW, which are serving a particular user. InFIG. 25, prior to the sending ofmessage1, a default PDN connection is established between the UE and the P-GW, and a LIPA connection is established between the UE and the L-GW. Consequently, the UE has a public IP address that was allocated by the P-GW. Furthermore, the UE has a different local IP address that was allocated by the L-GW. The MME managed the LIPA connection, and therefore the MME is aware of the L-GW Address or Local Home Network ID and LIPA-APN.

InFIG. 25,message1,step2, and

messages

InFIGS. 25-27, the

messages

6,7,8,9A,10,12, and13, and steps9 and11 are similar to the counterpart operations described in connection to inFIGS. 22 and 23. Instep6, the MME sends the “Create Bearer Request” (IMSI, EPS Bearer QoS, TFT, S-GW TEID, P-GW TEID, Bind-To-LGW-Flag, LGW-Bearer-ID, SCS-IP-ADDRESS) information to the S-GW (defined using the L-GW Address or Local Home Network ID IE) over S11. The TFT is included to carry the TFT rules to the L-GW. Using the ‘Bind-To-LGW-Flag’ IE, the S-GW will be able to inform the L-GW that this is a special request to create bearer (with ID LGW-Bearer-ID) between the L-GW and P-GW. Instep7, the “Create Bearer Request” is forwarded to the P-GW over the S5 interface. Inmessage8, the P-GW initiates IP-CAN Session modification by sending a PCRF carrying TAD, Bind-To-LGW-Flag, and LGW-Bearer-ID information. The ‘Bind-To-LGW-Flag’ is included to indicate to the PCRF that the newly requested bearer is associated with an LS, rather than a UE. Instep9, the P-GW creates a new entry in its EPS bearer context table and generates a ‘LGW-Charging Id’ for the LGW-Bearer-ID Bearer. The new entry allows the P-GW to route user plane PDUs between the S-GW and the packet data network, and to start charging. Furthermore, the P-GW allocates a new IP address to be assigned to the LS, namely, ‘LS-IP-ADDRESS-new’. The P-GW may include the IP address of the SCS ‘SCS-IP-ADDRESS’, to be used in the NAT function at the L-GW. Inmessage9A, the P-GW returns to the S-GW a “Create Session Response” (L-GW Address or Local Home Network ID for the user plane, L-GW TEID of the user plane, L-GW TEID of the control plane, PDN Type, LGW-Bearer-ID, EPS Bearer QoS, Protocol Configuration Options, Prohibit Payload Compression, APN Restriction, Cause, APN-AMBR), establishing a GTP tunnel between the S-GW and P-GW. Inmessage10, the S-GW sends the “Create Bearer Request” (IMSI, EPS Bearer QoS, TFT, S-GW TEID, P-GW TEID, Bind-To-LGW-Flag, LGW-Bearer-ID, SCS-IP-ADDRESS) information to the L-GW (defined using the L-GW Address or Local Home Network ID IE) over S5. The TFT is included to carry the TFT rules to the L-GW. Using the ‘Bind-To-LGW-Flag’ IE, the S-GW will be able to inform the L-GW that this is a special request to create bearer (with ID LGW-Bearer-ID) between the L-GW and P-GW. Instep11, the L-GW creates a new NAT entry indicating that, if data is to be sent over the LIPA connection from the LS using LS-PORT-NUM X and the destination IP address is SCS (SCS-IP-ADDRESS), the source Address should be changed to the UE's public IP address (UE-IP-ADDRESS). Instep12, the L-GW will acknowledge the S-GW's request to create a bearer. Instep13, the S-GW responds to the MME's request instep6.

The MME sends a “Create Session Response” (LGW-Bearer-ID)message14 to the SCEF, since the new session is now established between the L-GW and P-GW.

Finally, the SCEF responds to the API the first step by sending “Retrieve Local Information Response”message15 to the SCS/AS.

If multiple UE or SCS entities initiate requests to establish the same LS-SCS (LGW-PGW) connection, the P-GW would only accept the first request. All the subsequent requests will not be executed by the P-GW, and an acknowledgement would be sent to the requesting entity indicating that the requested dedicated bearer or PDN connection is already established.

FIG. 28 is an example call flow of user plane communications for an AE initiated connection. The AE, which may be hosted on the UE, can inform both the LS and SCS, over the user plane, about the port number to use for the direct communication between each other. Inmessage1, the AE informs the LS over the existing LIPA connection that the AE needs to use port LS-PORT-NUM X to communicate with the SCS. Inmessage1a, the LS acknowledgesmessage1. Inmessage2, the AE informs the SCS over the default public PDN connection that the AE needs to use port LS-PORT-NUM X to communicate with the LS. Inmessage2a, the SCS acknowledgesmessage2. The AE may then communicate this port number to the network. The port number may then be used to configure NAT rules in the L-GW, P-GW, and/or S(G)i-LAN.

FIG. 29 is an example call flow of user plane communications for an SCS initiated connection. Inmessage1, the SCS initiates LGW-PGW connections establishment by sending a message in which SCS will choose an LS-PORT-NUM (=X) to be used for its communication with the LS. In order for the SCS to send the port number to the LS, it first sends the port number to the AE over the 3GPP default PDN connection. Inmessage1a, the AE acknowledges receipt ofmessage1. Then inmessage2, the AE forwards the port number to the LS over the LIPA connection. Inmessage2a, the LS acknowledgesmessage2. Using this method, the SCS does not need to know the local IP address of the LS.

FIG. 30 illustrates an example graphical user interface (GUI) that allows a user to view or adjust system operation. In the example ofFIG. 30, the user may use to approve or disapprove of the local server sending information to the SCS/AS.

FIG. 31 is a diagram of an example machine-to machine (M2M), Internet of Things (IoT), or Web of Things (WoT)communication system10 in which one or more disclosed embodiments may be implemented. Generally, M2M technologies provide building blocks for the IoT/WoT, and any M2M device, M2M gateway, M2M server, or M2M service platform may be a component or node of the IoT/WoT as well as an IoT/WoT Service Layer, etc. Any of the client, proxy, or server devices illustrated in any ofFIG. 2-14, 17-18, or21-29 may comprise a node of a communication system such as the ones illustrated inFIG. 8, 10, 11, 21, 31, or32.

The service layer may be a functional layer within a network service architecture. Service layers are typically situated above the application protocol layer such as HTTP, CoAP or MQTT and provide value added services to client applications. The service layer also provides an interface to core networks at a lower resource layer, such as for example, a control layer and transport/access layer. The service layer supports multiple categories of (service) capabilities or functionalities including a service definition, service runtime enablement, policy management, access control, and service clustering. Recently, several industry standards bodies, e.g., oneM2M, have been developing M2M service layers to address the challenges associated with the integration of M2M types of devices and applications into deployments such as the Internet/Web, cellular, enterprise, and home networks. A M2M service layer can provide applications and/or various devices with access to a collection of or a set of the above mentioned capabilities or functionalities, supported by the service layer, which can be referred to as a CSE or SCL. A few examples include but are not limited to security, charging, data management, device management, discovery, provisioning, and connectivity management which can be commonly used by various applications. These capabilities or functionalities are made available to such various applications via APIs which make use of message formats, resource structures and resource representations defined by the M2M service layer. The CSE or SCL is a functional entity that may be implemented by hardware and/or software and that provides (service) capabilities or functionalities exposed to various applications and/or devices (i.e., functional interfaces between such functional entities) in order for them to use such capabilities or functionalities.

As shown inFIG. 31, the M2M/IoT/WoT communication system10 includes acommunication network12. Thecommunication network12 may be a fixed network (e.g., Ethernet, Fiber, ISDN, PLC, or the like) or a wireless network (e.g., WLAN, cellular, or the like) or a network of heterogeneous networks. For example, thecommunication network12 may be comprised of multiple access networks that provide content such as voice, data, video, messaging, broadcast, or the like to multiple users. For example, thecommunication network12 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), and the like. Further, thecommunication network12 may comprise other networks such as a core network, the Internet, a sensor network, an industrial control network, a personal area network, a fused personal network, a satellite network, a home network, or an enterprise network for example.

As shown inFIG. 31, the M2M/IoT/WoT communication system10 may include the Infrastructure Domain and the Field Domain. The Infrastructure Domain refers to the network side of the end-to-end M2M deployment, and the Field Domain refers to the area networks, usually behind an M2M gateway. The Field Domain and Infrastructure Domain may both comprise a variety of different nodes (e.g., servers, gateways, device, and the like) of the network. For example, the Field Domain may includeM2M gateways14 anddevices18. It will be appreciated that any number ofM2M gateway devices14 andM2M devices18 may be included in the M2M/IoT/WoT communication system10 as desired. Each of theM2M gateway devices14 andM2M devices18 are configured to transmit and receive signals, using communications circuitry, via thecommunication network12 or direct radio link. AM2M gateway14 allows wireless M2M devices (e.g., cellular and non-cellular) as well as fixed network M2M devices (e.g., PLC) to communicate either through operator networks, such as thecommunication network12 or direct radio link. For example, theM2M devices18 may collect data and send the data, via thecommunication network12 or direct radio link, to anM2M application20 orother M2M devices18. TheM2M devices18 may also receive data from theM2M application20 or anM2M device18. Further, data and signals may be sent to and received from theM2M application20 via anM2M Service Layer22, as described below.M2M devices18 andgateways14 may communicate via various networks including, cellular, WLAN, WPAN (e.g., Zigbee, 6LoWPAN, Bluetooth), direct radio link, and wireline for example. Exemplary M2M devices include, but are not limited to, tablets, smart phones, medical devices, temperature and weather monitors, connected cars, smart meters, game consoles, personal digital assistants, health and fitness monitors, lights, thermostats, appliances, garage doors and other actuator-based devices, security devices, and smart outlets.

Referring toFIG. 32, the illustratedM2M Service Layer22 in the field domain provides services for theM2M application20,M2M gateways14, andM2M devices18 and thecommunication network12. It will be understood that theM2M Service Layer22 may communicate with any number of M2M applications,M2M gateways14,M2M devices18, andcommunication networks12 as desired. TheM2M Service Layer22 may be implemented by one or more nodes of the network, which may comprise servers, computers, devices, or the like. TheM2M Service Layer22 provides service capabilities that apply toM2M devices18,M2M gateways14, andM2M applications20. The functions of theM2M Service Layer22 may be implemented in a variety of ways, for example as a web server, in the cellular core network, in the cloud, etc.

Referring also toFIG. 32, the M2M Service Layers22 and22′ provide a core set of service delivery capabilities that diverse applications and verticals may leverage. These service capabilities enable

M2M applications

20 and20′ to interact with devices and perform functions such as data collection, data analysis, device management, security, billing, service/device discovery, etc. Essentially, these service capabilities free the applications of the burden of implementing these functionalities, thus simplifying application development and reducing cost and time to market. The Service Layers22 and22′ also enable

M2M applications

20 and20′ to communicate through various networks such asnetwork12 in connection with the services that the Service Layers22 and22′ provide.

The

M2M applications

20 and20′ may include applications in various industries such as, without limitation, transportation, health and wellness, connected home, energy management, asset tracking, and security and surveillance. As mentioned above, the M2M Service Layer, running across the devices, gateways, servers and other nodes of the system, supports functions such as, for example, data collection, device management, security, billing, location tracking/geofencing, device/service discovery, and legacy systems integration, and provides these functions as services to the

M2M applications

20 and20′.

Generally, a Service Layer, such as the Service Layers22 and22′ illustrated inFIG. 32, defines a software middleware layer that supports value-added service capabilities through a set of Application Programming Interfaces (APIs) and underlying networking interfaces. Both the ETSI M2M and oneM2M architectures define a Service Layer. ETSI M2M's Service Layer is referred to as the Service Capability Layer (SCL). The SCL may be implemented in a variety of different nodes of the ETSI M2M architecture. For example, an instance of the Service Layer may be implemented within an M2M device (where it is referred to as a device SCL (DSCL)), a gateway (where it is referred to as a gateway SCL (GSCL)) and/or a network node (where it is referred to as a network SCL (NSCL)). The oneM2M Service Layer supports a set of Common Service Functions (CSFs) (i.e., service capabilities). An instantiation of a set of one or more particular types of CSFs is referred to as a Common Services Entity (CSE) which may be hosted on different types of network nodes (e.g., infrastructure node, middle node, application-specific node). The Third Generation Partnership Project (3GPP) has also defined an architecture for machine-type communications (MTC). In that architecture, the Service Layer, and the service capabilities it provides, are implemented as part of a Service Capability Server (SCS). Whether embodied in a DSCL, GSCL, or NSCL of the ETSI M2M architecture, in a Service Capability Server (SCS) of the 3GPP MTC architecture, in a CSF or CSE of the oneM2M architecture, or in some other node of a network, an instance of the Service Layer may be implemented as a logical entity (e.g., software, computer-executable instructions, and the like) executing either on one or more standalone nodes in the network, including servers, computers, and other computing devices or nodes, or as part of one or more existing nodes. As an example, an instance of a Service Layer or component thereof may be implemented in the form of software running on a network node (e.g., server, computer, gateway, device or the like) having the general architecture illustrated inFIG. 32 orFIG. 34 described below.

Further, the methods and functionalities described herein may be implemented as part of an M2M network that uses a Service Oriented Architecture (SOA) and/or a Resource-Oriented Architecture (ROA) to access services.

FIG. 33 is a block diagram of an example hardware/software architecture of a node of a network, such as one of the clients, servers, or proxies illustrated inFIG. 2-14, 17-18, or21-29, which may operate as an M2M server, gateway, device, or other node in an M2M network such as that illustrated inFIG. 8, 10, 11, 21, 31, or32. As shown inFIG. 33, thenode30 may include aprocessor32,non-removable memory44,removable memory46, a speaker/microphone38, akeypad40, a display, touchpad, and/orindicators42, apower source48, a global positioning system (GPS)chipset50, andother peripherals52. Thenode30 may also include communication circuitry, such as atransceiver34 and a transmit/receiveelement36. It will be appreciated that thenode30 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment. This node may be a node that implements the connection initiation steps herein, e.g., in relation toFIG. 2-13, 17-18, or22-29, or in a claim.

Theprocessor32 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Array (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. In general, theprocessor32 may execute computer-executable instructions stored in the memory (e.g.,memory44 and/or memory46) of the node in order to perform the various required functions of the node. For example, theprocessor32 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables thenode30 to operate in a wireless or wired environment. Theprocessor32 may run application-layer programs (e.g., browsers) and/or radio access-layer (RAN) programs and/or other communications programs. Theprocessor32 may also perform security operations such as authentication, security key agreement, and/or cryptographic operations, such as at the access-layer and/or application layer for example.

As shown inFIG. 33, theprocessor32 is coupled to its communication circuitry (e.g.,transceiver34 and transmit/receive element36). Theprocessor32, through the execution of computer executable instructions, may control the communication circuitry in order to cause thenode30 to communicate with other nodes via the network to which it is connected. In particular, theprocessor32 may control the communication circuitry in order to perform the connection initiation steps herein, e.g., in relation toFIG. 2-13, 17-18, or22-29, or in a claim. WhileFIG. 33 depicts theprocessor32 and thetransceiver34 as separate components, it will be appreciated that theprocessor32 and thetransceiver34 may be integrated together in an electronic package or chip.

The transmit/receiveelement36 may be configured to transmit signals to, or receive signals from, other nodes, including M2M servers, gateways, device, and the like. For example, in an embodiment, the transmit/receiveelement36 may be an antenna configured to transmit and/or receive RF signals. The transmit/receiveelement36 may support various networks and air interfaces, such as WLAN, WPAN, cellular, and the like. In an embodiment, the transmit/receiveelement36 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example. In yet another embodiment, the transmit/receiveelement36 may be configured to transmit and receive both RF and light signals. It will be appreciated that the transmit/receiveelement36 may be configured to transmit and/or receive any combination of wireless or wired signals.

In addition, although the transmit/receiveelement36 is depicted inFIG. 33 as a single element, thenode30 may include any number of transmit/receiveelements36. More specifically, thenode30 may employ MIMO technology. Thus, in an embodiment, thenode30 may include two or more transmit/receive elements36 (e.g., multiple antennas) for transmitting and receiving wireless signals.

Thetransceiver34 may be configured to modulate the signals that are to be transmitted by the transmit/receiveelement36 and to demodulate the signals that are received by the transmit/receiveelement36. As noted above, thenode30 may have multi-mode capabilities. Thus, thetransceiver34 may include multiple transceivers for enabling thenode30 to communicate via multiple RATs, such as UTRA and IEEE 802.11, for example.

Theprocessor32 may access information from, and store data in, any type of suitable memory, such as thenon-removable memory44 and/or theremovable memory46. For example, theprocessor32 may store session context in its memory, as described above. Thenon-removable memory44 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. Theremovable memory46 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, theprocessor32 may access information from, and store data in, memory that is not physically located on thenode30, such as on a server or a home computer. Theprocessor32 may be configured to control lighting patterns, images, or colors on the display orindicators42 to reflect the status of an M2M Service Layer session migration or sharing or to obtain input from a user or display information to a user about the node's session migration or sharing capabilities or settings. In another example, the display may show information with regard to a session state.

Theprocessor32 may receive power from thepower source48, and may be configured to distribute and/or control the power to the other components in thenode30. Thepower source48 may be any suitable device for powering thenode30. For example, thepower source48 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.

Theprocessor32 may also be coupled to theGPS chipset50, which is configured to provide location information (e.g., longitude and latitude) regarding the current location of thenode30. It will be appreciated that thenode30 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment.

Theprocessor32 may further be coupled toother peripherals52, which may include one or more software and/or hardware modules that provide additional features, functionality and/or wired or wireless connectivity. For example, theperipherals52 may include various sensors such as an accelerometer, biometrics (e.g., finger print) sensors, an e-compass, a satellite transceiver, a sensor, a digital camera (for photographs or video), a universal serial bus (USB) port or other interconnect interfaces, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, and the like.

Thenode30 may be embodied in other apparatuses or devices, such as a sensor, consumer electronics, a wearable device such as a smart watch or smart clothing, a medical or eHealth device, a robot, industrial equipment, a drone, a vehicle such as a car, truck, train, or airplane. Thenode30 may connect to other components, modules, or systems of such apparatuses or devices via one or more interconnect interfaces, such as an interconnect interface that may comprise one of theperipherals52.

FIG. 34 is a block diagram of anexemplary computing system90 in which one or more apparatuses of the communications networks illustrated inFIGS. 2-14, 17-18, 21-29, 35, 37, 38 and 39 may be embodied, such as certain nodes or functional entities in theRAN103/104/105,Core Network106/107/109,PSTN108,Internet110, orOther Networks112.

Computing system

90 may comprise a computer or server and may be controlled primarily by computer readable instructions, which may be in the form of software, wherever, or by whatever means such software is stored or accessed. Such computer readable instructions may be executed within aprocessor91, to causecomputing system90 to do work. Theprocessor91 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Array (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. Theprocessor91 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables thecomputing system90 to operate in a communications network.Coprocessor81 is an optional processor, distinct frommain processor91, that may perform additional functions or assistprocessor91.Processor91 and/orcoprocessor81 may receive, generate, and process data related to the methods and apparatuses disclosed herein.

In operation,processor91 fetches, decodes, and executes instructions, and transfers information to and from other resources via the computing system's main data-transfer path,system bus80. Such a system bus connects the components incomputing system90 and defines the medium for data exchange.System bus80 typically includes data lines for sending data, address lines for sending addresses, and control lines for sending interrupts and for operating the system bus. An example of such asystem bus80 is the PCI (Peripheral Component Interconnect) bus.

Memories coupled tosystem bus80 include random access memory (RAM)82 and read only memory (ROM)93. Such memories include circuitry that allows information to be stored and retrieved.ROMs93 generally contain stored data that cannot easily be modified. Data stored inRAM82 can be read or changed byprocessor91 or other hardware devices. Access to RAM82 and/orROM93 may be controlled bymemory controller92.Memory controller92 may provide an address translation function that translates virtual addresses into physical addresses as instructions are executed.Memory controller92 may also provide a memory protection function that isolates processes within the system and isolates system processes from user processes. Thus, a program running in a first mode can access only memory mapped by its own process virtual address space; it cannot access memory within another process's virtual address space unless memory sharing between the processes has been set up.

In addition,computing system90 may containperipherals controller83 responsible for communicating instructions fromprocessor91 to peripherals, such asprinter94,keyboard84,mouse95, anddisk drive85.

Display

86, which is controlled bydisplay controller96, is used to display visual output generated by computingsystem90. Such visual output may include text, graphics, animated graphics, and video. The visual output may be provided in the form of a graphical user interface (GUI).Display86 may be implemented with a CRT-based video display, an LCD-based flat-panel display, gas plasma-based flat-panel display, or a touch-panel.Display controller96 includes electronic components required to generate a video signal that is sent to display86.

Further,computing system90 may contain communication circuitry, such as for example anetwork adapter97, that may be used to connectcomputing system90 to an external communications network, such asnetwork12 ofFIGS. 31 and 32, theRAN103/104/105,Core Network106/107/109,PSTN108,Internet110, orOther Networks112 ofFIGS. 35, 36, 37, 38, and 39, to enable thecomputing system90 to communicate with other nodes or functional entities of those networks. The communication circuitry, alone or in combination with theprocessor91, may be used to perform the transmitting and receiving steps of certain apparatuses, nodes, or functional entities described herein.

It is understood that any or all of the apparatuses, systems, methods and processes described herein may be embodied in the form of computer executable instructions (e.g., program code) stored on a computer-readable storage medium which instructions, when executed by a processor, such as

processors

118 or91, cause the processor to perform and/or implement the systems, methods and processes described herein. Specifically, any of the steps, operations or functions described herein may be implemented in the form of such computer executable instructions, executing on the processor of an apparatus or computing system configured for wireless and/or wired network communications. Computer readable storage media include volatile and nonvolatile, removable and non-removable media implemented in any non-transitory (e.g., tangible or physical) method or technology for storage of information, but such computer readable storage media do not includes signals. Computer readable storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other tangible or physical medium which can be used to store the desired information and which can be accessed by a computing system.

The 3rd Generation Partnership Project (3GPP) develops technical standards for cellular telecommunications network technologies, including radio access, the core transport network, and service capabilities—including work on codecs, security, and quality of service. Recent radio access technology (RAT) standards include WCDMA (commonly referred as 3G), LTE (commonly referred as 4G), and LTE-Advanced standards. 3GPP has begun working on the standardization of next generation cellular technology, called New Radio (NR), which is also referred to as “5G.” 3GPP NR standards development is expected to include the definition of next generation radio access technology (new RAT), which is expected to include the provision of new flexible radio access below 6 GHz, and the provision of new ultra-mobile broadband radio access above 6 GHz. The flexible radio access is expected to consist of a new, non-backwards compatible radio access in new spectrum below 6 GHz, and it is expected to include different operating modes that can be multiplexed together in the same spectrum to address a broad set of 3GPP NR use cases with diverging requirements. The ultra-mobile broadband is expected to include cmWave and mmWave spectrum that will provide the opportunity for ultra-mobile broadband access for, e.g., indoor applications and hotspots. In particular, the ultra-mobile broadband is expected to share a common design framework with the flexible radio access below 6 GHz, with cmWave and mmWave specific design optimizations.

3GPP has identified a variety of use cases that NR is expected to support, resulting in a wide variety of user experience requirements for data rate, latency, and mobility. The use cases include the following general categories: enhanced mobile broadband (e.g., broadband access in dense areas, indoor ultra-high broadband access, broadband access in a crowd, 50+ Mbps everywhere, ultra-low cost broadband access, mobile broadband in vehicles), critical communications, massive machine type communications, network operation (e.g., network slicing, routing, migration and interworking, energy savings), and enhanced vehicle-to-everything (eV2X) communications. Specific service and applications in these categories include, e.g., monitoring and sensor networks, device remote controlling, bi-directional remote controlling, personal cloud computing, video streaming, wireless cloud-based office, first responder connectivity, automotive ecall, disaster alerts, real-time gaming, multi-person video calls, autonomous driving, augmented reality, tactile internet, and virtual reality to name a few. All of these use cases and others are contemplated herein.

FIG. 35 illustrates one embodiment of anexample communications system100 in which the methods and apparatuses described and claimed herein may be embodied. As shown, theexample communications system100 may include wireless transmit/receive units (WTRUs)102a,102b,102c, and/or102d(which generally or collectively may be referred to as WTRU102), a radio access network (RAN)103/104/105/103b/104b/105b, acore network106/107/109, a public switched telephone network (PSTN)108, theInternet110, andother networks112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements. Each of the

WTRUs

102a,102b,102c,102d,102emay be any type of apparatus or device configured to operate and/or communicate in a wireless environment. Although each WTRU102a,102b,102c,102d,102eis depicted inFIGS. 35-39 as a hand-held wireless communications apparatus, it is understood that with the wide variety of use cases contemplated for 5G wireless communications, each WTRU may comprise or be embodied in any type of apparatus or device configured to transmit and/or receive wireless signals, including, by way of example only, user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a tablet, a netbook, a notebook computer, a personal computer, a wireless sensor, consumer electronics, a wearable device such as a smart watch or smart clothing, a medical or eHealth device, a robot, industrial equipment, a drone, a vehicle such as a car, truck, train, or airplane, and the like.

Thecommunications system100 may also include abase station114aand abase station114b.Base stations114amay be any type of device configured to wirelessly interface with at least one of the

WTRUs

102a,102b,102cto facilitate access to one or more communication networks, such as thecore network106/107/109, theInternet110, and/or theother networks112.Base stations114bmay be any type of device configured to wiredly and/or wirelessly interface with at least one of the RRHs (Remote Radio Heads)118a,118band/or TRPs (Transmission and Reception Points)119a,119bto facilitate access to one or more communication networks, such as thecore network106/107/109, theInternet110, and/or theother networks112.

RRHs

118a,118bmay be any type of device configured to wirelessly interface with at least one of theWTRU102c, to facilitate access to one or more communication networks, such as thecore network106/107/109, theInternet110, and/or theother networks112.

TRPs

119a,119bmay be any type of device configured to wirelessly interface with at least one of theWTRU102d, to facilitate access to one or more communication networks, such as thecore network106/107/109, theInternet110, and/or theother networks112. By way of example, the

base stations

114a,114bmay be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a site controller, an access point (AP), a wireless router, and the like. While the

base stations

114a,114bare each depicted as a single element, it will be appreciated that the

base stations

114a,114bmay include any number of interconnected base stations and/or network elements.

Thebase station114amay be part of theRAN103/104/105, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. Thebase station114bmay be part of theRAN103b/104b/105b, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. Thebase station114amay be configured to transmit and/or receive wireless signals within a particular geographic region, which may be referred to as a cell (not shown). Thebase station114bmay be configured to transmit and/or receive wired and/or wireless signals within a particular geographic region, which may be referred to as a cell (not shown). The cell may further be divided into cell sectors. For example, the cell associated with thebase station114amay be divided into three sectors. Thus, in an embodiment, thebase station114amay include three transceivers, e.g., one for each sector of the cell. In an embodiment, thebase station114amay employ multiple-input multiple output (MIMO) technology and, therefore, may utilize multiple transceivers for each sector of the cell.

Thebase stations114amay communicate with one or more of the

WTRUs

102a,102b,102cover anair interface115/116/117, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). Theair interface115/116/117 may be established using any suitable radio access technology (RAT).

Thebase stations114bmay communicate with one or more of the

RRHs

118a,118band/or TRPs119a,119bover a wired orair interface115b/116b/117b, which may be any suitable wired (e.g., cable, optical fiber, etc.) or wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). Theair interface115b/116b/117bmay be established using any suitable radio access technology (RAT).

The

RRHs

118a,118band/or TRPs119a,119bmay communicate with one or more of the

WTRUs

102c,102dover anair interface115c/116c/117c, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). Theair interface115c/116c/117cmay be established using any suitable radio access technology (RAT).

More specifically, as noted above, thecommunications system100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, thebase station114ain theRAN103/104/105 and the

WTRUs

102a,102b,102c, or

RRHs

118a,118band

TRPs

119a,119bin theRAN103b/104b/105band the

WTRUs

102c,102d, may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish theair interface115/116/117 or115c/116c/117crespectively using wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink Packet Access (HSDPA) and/or High-Speed Uplink Packet Access (HSUPA).

In an embodiment, thebase station114aand the

WTRUs

102a,102b,102c, or

RRHs

118a,118band

TRPs

119a,119bin theRAN103b/104b/105band the

WTRUs

102c,102d, may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish theair interface115/116/117 or115c/116c/117crespectively using Long Term Evolution (LTE) and/or LTE-Advanced (LTE-A). In the future, theair interface115/116/117 may implement 3GPP NR technology.

In an embodiment, thebase station114ain theRAN103/104/105 and the

WTRUs

102a,102b,102c, or

RRHs

118a,118band

TRPs

119a,119bin theRAN103b/104b/105band the

WTRUs

102c,102d, may implement radio technologies such as IEEE 802.16 (e.g., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000,CDMA2000 1×, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.

Thebase station114cinFIG. 35 may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, and the like. In an embodiment, thebase station114cand theWTRUs102e, may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, thebase station114cand theWTRUs102d, may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, thebase station114cand theWTRUs102e, may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish a picocell or femtocell. As shown inFIG. 35, thebase station114bmay have a direct connection to theInternet110. Thus, thebase station114cmay not be required to access theInternet110 via thecore network106/107/109.

TheRAN103/104/105 and/orRAN103b/104b/105bmay be in communication with thecore network106/107/109, which may be any type of network configured to provide voice, data, applications, and/or voice over internet protocol (VoIP) services to one or more of the

WTRUs

102a,102b,102c,102d. For example, thecore network106/107/109 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication.

Although not shown inFIG. 35, it will be appreciated that theRAN103/104/105 and/orRAN103b/104b/105band/or thecore network106/107/109 may be in direct or indirect communication with other RANs that employ the same RAT as theRAN103/104/105 and/orRAN103b/104b/105bor a different RAT. For example, in addition to being connected to theRAN103/104/105 and/orRAN103b/104b/105b, which may be utilizing an E-UTRA radio technology, thecore network106/107/109 may also be in communication with another RAN (not shown) employing a GSM radio technology.

Thecore network106/107/109 may also serve as a gateway for the

WTRUs

102a,102b,102c,102d,102eto access thePSTN108, theInternet110, and/orother networks112. ThePSTN108 may include circuit-switched telephone networks that provide plain old telephone service (POTS). TheInternet110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and the internet protocol (IP) in the TCP/IP internet protocol suite. Thenetworks112 may include wired or wireless communications networks owned and/or operated by other service providers. For example, thenetworks112 may include another core network connected to one or more RANs, which may employ the same RAT as theRAN103/104/105 and/orRAN103b/104b/105bor a different RAT.

Some or all of the

WTRUs

102a,102b,102c,102din thecommunications system100 may include multi-mode capabilities, e.g., the

WTRUs

102a,102b,102c,102d, and102emay include multiple transceivers for communicating with different wireless networks over different wireless links. For example, theWTRU102eshown inFIG. 35 may be configured to communicate with thebase station114a, which may employ a cellular-based radio technology, and with thebase station114c, which may employ an IEEE 802 radio technology.

FIG. 36 is a block diagram of an example apparatus or device configured for wireless communications in accordance with the embodiments illustrated herein, such as for example, aWTRU102. As shown inFIG. 36, theexample WTRU102 may include aprocessor118, atransceiver120, a transmit/receiveelement122, a speaker/microphone124, akeypad126, a display/touchpad/indicators128,non-removable memory130,removable memory132, apower source134, a global positioning system (GPS)chipset136, andother peripherals138. It will be appreciated that theWTRU102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment. Also, embodiments contemplate that the

base stations

114aand114b, and/or the nodes that

base stations

114aand114bmay represent, such as but not limited to, transceiver station (BTS), a Node-B, a site controller, an access point (AP), a home node-B, an evolved home node-B (eNodeB), a home evolved node-B (HeNB), a home evolved node-B gateway, and proxy nodes, among others, may include some or all of the elements depicted inFIG. 36 and described herein.

Theprocessor118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Array (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. Theprocessor118 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables theWTRU102 to operate in a wireless environment. Theprocessor118 may be coupled to thetransceiver120, which may be coupled to the transmit/receiveelement122. WhileFIG. 36 depicts theprocessor118 and thetransceiver120 as separate components, it will be appreciated that theprocessor118 and thetransceiver120 may be integrated together in an electronic package or chip.

The transmit/receiveelement122 may be configured to transmit signals to, or receive signals from, a base station (e.g., thebase station114a) over theair interface115/116/117. For example, in an embodiment, the transmit/receiveelement122 may be an antenna configured to transmit and/or receive RF signals. Although not shown inFIG. 35, it will be appreciated that theRAN103/104/105 and/or thecore network106/107/109 may be in direct or indirect communication with other RANs that employ the same RAT as theRAN103/104/105 or a different RAT. For example, in addition to being connected to theRAN103/104/105, which may be utilizing an E-UTRA radio technology, thecore network106/107/109 may also be in communication with another RAN (not shown) employing a GSM radio technology.

Thecore network106/107/109 may also serve as a gateway for the

WTRUs

102a,102b,102c,102dto access thePSTN108, theInternet110, and/orother networks112. ThePSTN108 may include circuit-switched telephone networks that provide plain old telephone service (POTS). TheInternet110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and the internet protocol (IP) in the TCP/IP internet protocol suite. Thenetworks112 may include wired or wireless communications networks owned and/or operated by other service providers. For example, thenetworks112 may include another core network connected to one or more RANs, which may employ the same RAT as theRAN103/104/105 or a different RAT.

Some or all of the

WTRUs

102a,102b,102c, and102dmay include multiple transceivers for communicating with different wireless networks over different wireless links. For example, theWTRU102cshown inFIG. 35 may be configured to communicate with thebase station114a, which may employ a cellular-based radio technology, and with thebase station114b, which may employ an IEEE 802 radio technology.

base stations

114aand114b, and/or the nodes that

base stations

114aand114bmay represent, such as but not limited to transceiver station (BTS), a Node-B, a site controller, an access point (AP), a home node-B, an evolved home node-B (eNodeB), a home evolved node-B (HeNB), a home evolved node-B gateway, and proxy nodes, among others, may include some or all of the elements depicted inFIG. 36 and described herein.

The transmit/receiveelement122 may be configured to transmit signals to, or receive signals from, a base station (e.g., thebase station114a) over theair interface115/116/117. For example, in an embodiment, the transmit/receiveelement122 may be an antenna configured to transmit and/or receive RF signals. In an embodiment, the transmit/receiveelement122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example. In yet an embodiment, the transmit/receiveelement122 may be configured to transmit and receive both RF and light signals. It will be appreciated that the transmit/receiveelement122 may be configured to transmit and/or receive any combination of wireless signals.

In addition, although the transmit/receiveelement122 is depicted inFIG. 36 as a single element, theWTRU102 may include any number of transmit/receiveelements122. More specifically, theWTRU102 may employ MIMO technology. Thus, in an embodiment, theWTRU102 may include two or more transmit/receive elements122 (e.g., multiple antennas) for transmitting and receiving wireless signals over theair interface115/116/117.

Thetransceiver120 may be configured to modulate the signals that are to be transmitted by the transmit/receiveelement122 and to demodulate the signals that are received by the transmit/receiveelement122. As noted above, theWTRU102 may have multi-mode capabilities. Thus, thetransceiver120 may include multiple transceivers for enabling theWTRU102 to communicate via multiple RATs, such as UTRA and IEEE 802.11, for example.

Theprocessor118 of theWTRU102 may be coupled to, and may receive user input data from, the speaker/microphone124, thekeypad126, and/or the display/touchpad/indicators128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit). Theprocessor118 may also output user data to the speaker/microphone124, thekeypad126, and/or the display/touchpad/indicators128. In addition, theprocessor118 may access information from, and store data in, any type of suitable memory, such as thenon-removable memory130 and/or theremovable memory132. Thenon-removable memory130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. Theremovable memory132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In an embodiment, theprocessor118 may access information from, and store data in, memory that is not physically located on theWTRU102, such as on a server or a home computer (not shown).

Theprocessor118 may receive power from thepower source134, and may be configured to distribute and/or control the power to the other components in theWTRU102. Thepower source134 may be any suitable device for powering theWTRU102. For example, thepower source134 may include one or more dry cell batteries, solar cells, fuel cells, and the like.

Theprocessor118 may also be coupled to theGPS chipset136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of theWTRU102. In addition to, or in lieu of, the information from theGPS chipset136, theWTRU102 may receive location information over theair interface115/116/117 from a base station (e.g.,

base stations

114a,114b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that theWTRU102 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment.

Theprocessor118 may further be coupled toother peripherals138, which may include one or more software and/or hardware modules that provide additional features, functionality and/or wired or wireless connectivity. For example, theperipherals138 may include various sensors such as an accelerometer, biometrics (e.g., finger print) sensors, an e-compass, a satellite transceiver, a digital camera (for photographs or video), a universal serial bus (USB) port or other interconnect interfaces, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, and the like.

TheWTRU102 may be embodied in other apparatuses or devices, such as a sensor, consumer electronics, a wearable device such as a smart watch or smart clothing, a medical or eHealth device, a robot, industrial equipment, a drone, a vehicle such as a car, truck, train, or airplane. TheWTRU102 may connect to other components, modules, or systems of such apparatuses or devices via one or more interconnect interfaces, such as an interconnect interface that may comprise one of theperipherals138.

FIG. 37 is a system diagram of theRAN103 and thecore network106 according to an embodiment. As noted above, theRAN103 may employ a UTRA radio technology to communicate with the

WTRUs

102a,102b, and102cover theair interface115. TheRAN103 may also be in communication with thecore network106. As shown inFIG. 37, theRAN103 may include Node-Bs140a,140b,140c, which may each include one or more transceivers for communicating with the

WTRUs

102a,102b,102cover theair interface115. The Node-Bs140a,140b,140cmay each be associated with a particular cell (not shown) within theRAN103. TheRAN103 may also include RNCs142a,142b. It will be appreciated that theRAN103 may include any number of Node-Bs and RNCs while remaining consistent with an embodiment.

As shown inFIG. 37, the Node-Bs140a,140bmay be in communication with the RNC142a. Additionally, the Node-B140cmay be in communication with the RNC142b. The Node-Bs140a,140b,140cmay communicate with the respective RNCs142a,142bvia an Iub interface. The RNCs142a,142bmay be in communication with one another via an Iur interface. Each of the RNCs142a,142bmay be configured to control the respective Node-Bs140a,140b,140cto which it is connected. In addition, each of the RNCs142a,142bmay be configured to carry out or support other functionality, such as outer loop power control, load control, admission control, packet scheduling, handover control, macro-diversity, security functions, data encryption, and the like.

Thecore network106 shown inFIG. 37 may include a media gateway (MGW)144, a mobile switching center (MSC)146, a serving GPRS support node (SGSN)148, and/or a gateway GPRS support node (GGSN)150. While each of the foregoing elements are depicted as part of thecore network106, it will be appreciated that any one of these elements may be owned and/or operated by an entity other than the core network operator.

The RNC142ain theRAN103 may be connected to theMSC146 in thecore network106 via an IuCS interface. TheMSC146 may be connected to theMGW144. TheMSC146 and theMGW144 may provide the WTRUs102a,102b,102cwith access to circuit-switched networks, such as thePSTN108, to facilitate communications between the

WTRUs

102a,102b,102cand traditional land-line communications devices.

The RNC142ain theRAN103 may also be connected to theSGSN148 in thecore network106 via an IuPS interface. TheSGSN148 may be connected to theGGSN150. TheSGSN148 and theGGSN150 may provide the WTRUs102a,102b,102cwith access to packet-switched networks, such as theInternet110, to facilitate communications between and the

WTRUs

102a,102b,102cand IP-enabled devices.

As noted above, thecore network106 may also be connected to thenetworks112, which may include other wired or wireless networks that are owned and/or operated by other service providers.

FIG. 38 is a system diagram of theRAN104 and thecore network107 according to an embodiment. As noted above, theRAN104 may employ an E-UTRA radio technology to communicate with the

WTRUs

102a,102b, and102cover theair interface116. TheRAN104 may also be in communication with thecore network107.

TheRAN104 may include eNode-

Bs

160a,160b,160c, though it will be appreciated that theRAN104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-

Bs

160a,160b,160cmay each include one or more transceivers for communicating with the

WTRUs

102a,102b,102cover theair interface116. In an embodiment, the eNode-

Bs

160a,160b,160cmay implement MIMO technology. Thus, the eNode-B160a, for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, theWTRU102a.

Each of the eNode-

Bs

160a,160b, and160cmay be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the uplink and/or downlink, and the like. As shown inFIG. 38, the eNode-

Bs

160a,160b,160cmay communicate with one another over an X2 interface.

Thecore network107 shown inFIG. 38 may include a mobility management gateway (MME)162, a servinggateway164, and a packet data network (PDN)gateway166. While each of the foregoing elements are depicted as part of thecore network107, it will be appreciated that any one of these elements may be owned and/or operated by an entity other than the core network operator.

TheMME162 may be connected to each of the eNode-

Bs

160a,160b, and160cin theRAN104 via an S1 interface and may serve as a control node. For example, theMME162 may be responsible for authenticating users of the

WTRUs

102a,102b,102c, bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the

WTRUs

102a,102b,102c, and the like. TheMME162 may also provide a control plane function for switching between theRAN104 and other RANs (not shown) that employ other radio technologies, such as GSM or WCDMA.

The servinggateway164 may be connected to each of the eNode-

Bs

160a,160b, and160cin theRAN104 via the S1 interface. The servinggateway164 may generally route and forward user data packets to/from the

WTRUs

102a,102b,102c. The servinggateway164 may also perform other functions, such as anchoring user planes during inter-eNode B handovers, triggering paging when downlink data is available for the

WTRUs

102a,102b,102c, managing and storing contexts of the

WTRUs

102a,102b,102c, and the like.

The servinggateway164 may also be connected to thePDN gateway166, which may provide the WTRUs102a,102b,102cwith access to packet-switched networks, such as theInternet110, to facilitate communications between the

WTRUs

102a,102b,102cand IP-enabled devices.

Thecore network107 may facilitate communications with other networks. For example, thecore network107 may provide the WTRUs102a,102b,102cwith access to circuit-switched networks, such as thePSTN108, to facilitate communications between the

WTRUs

102a,102b,102cand traditional land-line communications devices. For example, thecore network107 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between thecore network107 and thePSTN108. In addition, thecore network107 may provide the WTRUs102a,102b,102cwith access to thenetworks112, which may include other wired or wireless networks that are owned and/or operated by other service providers.

FIG. 39 is a system diagram of theRAN105 and thecore network109 according to an embodiment. TheRAN105 may be an access service network (ASN) that employs IEEE 802.16 radio technology to communicate with the

WTRUs

102a,102b, and102cover theair interface117. As will be further discussed below, the communication links between the different functional entities of the

WTRUs

102a,102b,102c, theRAN105, and thecore network109 may be defined as reference points.

As shown inFIG. 39, theRAN105 may include

base stations

180a,180b,180c, and anASN gateway182, though it will be appreciated that theRAN105 may include any number of base stations and ASN gateways while remaining consistent with an embodiment. The

base stations

180a,180b,180cmay each be associated with a particular cell in theRAN105 and may include one or more transceivers for communicating with the

WTRUs

102a,102b,102cover theair interface117. In an embodiment, the

base stations

180a,180b,180cmay implement MIMO technology. Thus, thebase station180a, for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, theWTRU102a. The

base stations

180a,180b,180cmay also provide mobility management functions, such as handoff triggering, tunnel establishment, radio resource management, traffic classification, quality of service (QoS) policy enforcement, and the like. TheASN gateway182 may serve as a traffic aggregation point and may be responsible for paging, caching of subscriber profiles, routing to thecore network109, and the like.

Theair interface117 between the

WTRUs

102a,102b,102cand theRAN105 may be defined as an R1 reference point that implements the IEEE 802.16 specification. In addition, each of the

WTRUs

102a,102b, and102cmay establish a logical interface (not shown) with thecore network109. The logical interface between the

WTRUs

102a,102b,102cand thecore network109 may be defined as an R2 reference point, which may be used for authentication, authorization, IP host configuration management, and/or mobility management.

The communication link between each of the

base stations

180a,180b, and180cmay be defined as an R8 reference point that includes protocols for facilitating WTRU handovers and the transfer of data between base stations. The communication link between the

base stations

180a,180b,180cand theASN gateway182 may be defined as an R6 reference point. The R6 reference point may include protocols for facilitating mobility management based on mobility events associated with each of the

WTRUs

102a,102b,102c.

As shown inFIG. 39, theRAN105 may be connected to thecore network109. The communication link between theRAN105 and thecore network109 may defined as an R3 reference point that includes protocols for facilitating data transfer and mobility management capabilities, for example. Thecore network109 may include a mobile IP home agent (MIP-HA)184, an authentication, authorization, accounting (AAA)server186, and agateway188. While each of the foregoing elements are depicted as part of thecore network109, it will be appreciated that any one of these elements may be owned and/or operated by an entity other than the core network operator.

The MIP-HA may be responsible for IP address management, and may enable the WTRUs102a,102b, and102cto roam between different ASNs and/or different core networks. The MIP-HA184 may provide the WTRUs102a,102b,102cwith access to packet-switched networks, such as theInternet110, to facilitate communications between the

WTRUs

102a,102b,102cand IP-enabled devices. TheAAA server186 may be responsible for user authentication and for supporting user services. Thegateway188 may facilitate interworking with other networks. For example, thegateway188 may provide the WTRUs102a,102b,102cwith access to circuit-switched networks, such as thePSTN108, to facilitate communications between the

WTRUs

102a,102b,102cand traditional land-line communications devices. In addition, thegateway188 may provide the WTRUs102a,102b,102cwith access to thenetworks112, which may include other wired or wireless networks that are owned and/or operated by other service providers.

Although not shown inFIG. 39, it will be appreciated that theRAN105 may be connected to other ASNs and thecore network109 may be connected to other core networks. The communication link between theRAN105 the other ASNs may be defined as an R4 reference point, which may include protocols for coordinating the mobility of the

WTRUs

102a,102b,102cbetween theRAN105 and the other ASNs. The communication link between thecore network109 and the other core networks may be defined as an R5 reference, which may include protocols for facilitating interworking between home core networks and visited core networks.

The core network entities described herein and illustrated inFIGS. 35, 37, 38, and39 are identified by the names given to those entities in certain existing 3GPP specifications, but it is understood that in the future those entities and functionalities may be identified by other names and certain entities or functions may be combined in future specifications published by 3GPP, including future 3GPP NR specifications. Thus, the particular network entities and functionalities described and illustrated inFIGS. 35, 36, 37, 38, and 39 are provided by way of example only, and it is understood that the subject matter disclosed and claimed herein may be embodied or implemented in any similar communication system, whether presently defined or defined in the future.

The5G core network170 shown inFIG. 40 may include an access and mobility management function (AMF)172, a session management function (SMF)174, a user plane function (UPF)176, a user data management function (UDM)178, an authentication server function (AUSF)180, a Network Exposure Function (NEF), a policy control function (PCF)184, a non-3GPP interworking function (N3IWF)192 and an application function (AF)188. While each of the foregoing elements are depicted as part of the5G core network170, it will be appreciated that any one of these elements may be owned and/or operated by an entity other than the core network operator. It should also be appreciated that a 5G core network may not consist of all of these elements, may consist of additional elements, and may consist of multiple instances of each of these elements.FIG. 40 shows that network functions directly connect to one another, however, it should be appreciated that they may communicate via routing agents such as diameter routing agents or message buses.

TheAMF172 may be connected to each of theRAN103/104/105/103b/104b/105bvia an N2 interface and may serve as a control node. For example, theAMF172 may be responsible for registration management, connection management, reachability management, access authentication, access authorization. TheAMF172 may generally route and forward NAS packets to/from the

WTRUs

102a,102b,102c.

TheSMF174 may be connected to theAMF172 via an N11 interface, maybe connected to aPCF184 via an N7 interface, and may be connected to theUPF176 via an N4 interface. TheSMF174 may serve as a control node. For example, theSMF174 may be responsible for Session Management,

WTRUs

102a,102b,102cIP address allocation & management and configuration of traffic steering rules in theUPF176, and generation of downlink data notifications.

TheSMF174 may also be connected to theUPF176, which may provide the WTRUs102a,102b,102cwith access to a data network (DN)190, such as theInternet110, to facilitate communications between the

WTRUs

102a,102b,102cand IP-enabled devices. TheSMF174 may manage and configure traffic steering rules in theUPF176 via the N4 interface. TheUPF176 may be responsible for interconnecting a packet data unit (PDU) session with a data network, packet routing and forwarding, policy rule enforcement, quality of service handling for user plane traffic, and downlink packet buffering.

TheAMF172 may also be connected to theN3IWF192 via an N2 interface. The N3IWF facilities a connection between the

WTRUs

102a,102b,102cand the5G core network170 via radio interface technologies that are not defined by 3GPP.

ThePCF184 may be connected to theSMF174 via an N7 interface, connected to theAMF172 via an N15 interface, and connected to an application function (AF)188 via an N5 interface. ThePCF184 may provide policy rules to control plane nodes such as theAMF172 andSMF174, allowing the control plane nodes to enforce these rules.

TheUDM178 acts as a repository for authentication credentials and subscription information. The UDM may connect to other functions such as theAMF172,SMF174, and AUSF180.

The AUSF180 performs authentication related operations and connects to theUDM178 via an N13 interface and to theAMF172 via an N12 interface.

The NEF exposes capabilities and services in the5G core network170. The NEF may connect to anAF188 via an interface and it may connect to other control plane and user plane functions (180,178,172,172,184,176, and N3IWF) in order to expose the capabilities and services of the5G core network170.

The5G core network170 may facilitate communications with other networks. For example, thecore network170 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the5G core network170 and thePSTN108. For example, thecore network170 may include, or communicate with a short message service (SMS) service center that facilities communication via the short message service. For example, the5G core network170 may facilitate the exchange of non-IP data packets between the

WTRUs

102a,102b,102cand servers. In addition, thecore network170 may provide the WTRUs102a,102b,102cwith access to thenetworks112, which may include other wired or wireless networks that are owned and/or operated by other service providers.