Methods and apparatus for establishing a group session in a mobile network for subscribers associated with a group

Methods and apparatus for use in establishing a group session in a mobile network for subscribers associated with a group are described. In one illustrative example, an access and mobility management function (AMF) entity receives, from a user equipment (UE), a request for registration which includes network slice selection assistance information (NSSAI). The NSSAI includes a group identifier associated with a group of subscribers. The AMF entity sends, to a unified data management (UDM) entity, a request for subscriber data which includes the group identifier. The AMF entity receives, from the UDM, a response to the request for subscriber data which includes a plurality of subscriber identifiers corresponding to the subscribers of the group. For a group session, the AMF entity creates a context associated with the group identifier and stores the context locally.

TECHNICAL FIELD

The present disclosure relates generally to methods and apparatus for use in establishing a group session in a mobile network for subscribers of a group, and more particularly to establishing a group session in a mobile network for subscribers of a group for reduced signaling load and simplified and improved subscriber management.

BACKGROUND

There is a need for reducing a signaling load in mobile networks, as well as simplifying subscriber management and control over subscribers of user equipment (UE) in such networks, especially when considering the very large and increasing number of devices (e.g. IoT devices) expected to be connected in such networks.

DESCRIPTION OF EXAMPLE EMBODIMENTS

Overview

What are described herein are methods and apparatus for use in establishing a group session for subscribers associated with a group in a mobile network. The mobile network may be, for example, a 4G or LTE-based mobile network or a 5G mobile network.

The establishment of a group session for subscribers associated with a group according to techniques of the present disclosure may be provided in addition to the establishment of sessions for subscribers individually as is conventional. From the perspective of the mobile network operator, the establishment of a group session in accordance with some implementations of the present disclosure may provide for a reduced signaling load in the mobile network, and/or a more simplified and efficient management and control over the subscribers. From the perspective of the owner or controller of the UEs/subscribers of a group, the establishment of a group session in accordance with some implementations of the present disclosure may provide for a more simplified management and oversight over the subscribers, as well as provide for a better understanding of the (combined) actual, communication needs for the subscriber group.

In an illustrative example for a 5G mobile network, an entity such as an access and mobility management function (AMF) entity may be configured for processing of subscribers of a group. A group of subscribers may be associated with a (unique) group identifier. A plurality of subscriber identifiers associated with subscribers/UEs that are members of the group may be stored in association with the group identifier.

The AMF entity may receive, from a UE, a request for registration which may include network slice selection assistance information (NSSAI). The NSSAI may include the group identifier associated with the group of subscribers. The AMF entity may send, to a unified data management (UDM) entity, a request for subscriber data which includes the group identifier. The AMF entity may receive, from the UDM, a response to the request for subscriber data which includes the plurality of subscriber identifiers corresponding to the group.

For a group session for the group, the AMF entity may create a context for a group session associated with the group identifier, and store this context locally. The AMF entity may store the plurality of subscriber identifiers in association with the context. Further, the AMF entity may obtain selected network functions (NF), selected policies or policy rules, and/or a selected set of assigned IP addresses for the group session, and store this information in association with the context. For one or more subsequently-registering UEs in the group, the AMF entity may retrieve the information from the locally-stored context for inclusion in the already-established group session.

In more detail, the AMF entity may send, to a policy and charging function (PCF) entity, a context establishment request which includes the group identifier. The AMF entity may receive, from the PCF entity, a response to the context establishment request which includes (e.g. group) access policies associated with the group identifier and for the group. The AMF entity may update the locally-stored group context with the group access polices. Note that, for subsequent UEs in the group, the AMF entity may obtain the access policies from the locally-stored context, without again having to receive the policies from the PCF entity.

Even further, the AMF entity may receive, from the UE, a PDU session establishment request which includes the group identifier. The AMF entity may send, to a network repository function (NRF) entity, a request for a session management function (SMF) entity. The AMF entity may receive, from the NRF entity, a response to the request for the SMF entity, where the response includes an SMF identifier of the SMF entity. The AMF entity may update the group context with the SMF identifier of the SMF entity. The AMF entity may send, to the SMF entity, a session request. The AMF entity may receive, from the SMF entity, a session acceptance which includes a plurality of IP addresses assigned to the plurality of subscriber identifiers corresponding to the group of subscribers. The AMF entity may update the locally-stored group context with the plurality of IP addresses assigned to the plurality of subscriber identifiers. Note that, for subsequent UEs in the group, the AMF entity may obtain assigned IP addresses from the locally-stored context, without again having to receive the IP addresses from the SMF entity.

In another illustrative example, a data session between a base station and a UPF is established for a UE. The UE is associated with a first-registering subscriber of a group of subscribers identified by a group identifier. Here, one or more additional UEs associated with one or more subsequently-registering subscribers of the group identified by the group identifier may be included in the data session. The data session may be a packet data unit (PDU) session between the base station and the UPF.

Further, a session between a session management function (SMF) and the UPF may established for the first-registering subscriber. Here, the one or more additional UEs associated with one or more subsequently-registering subscribers of the group identified by the group identifier may be included in the session between the SMF and the UPF. Also further, a session between an access and mobility management function (AMF) and the SMF may established for the UE associated with first-registering subscriber. Here, the one or more additional UEs associated with one or more subsequently-registering subscribers of the group identified by the group identifier may be included in the session between the AMF and the SMF. In addition, a session between the SMF and a policy and charging function (PCF) may established for the UE associated with first-registering subscriber. Here, the one or more additional UEs associated with one or more subsequently-registering subscribers of the group identified by the group identifier may be included in the session between the SMF and the PCF.

Example Embodiments

FIG. 1Ais an illustrative representation of a network architecture100aof a 5G mobile network. Network architecture100aof the 5G mobile network is configured to support network slicing. In general, network architecture100aincludes common control network functions (CCNF)105and a plurality of slice-specific core network functions106. A user equipment (UE)102may obtain access to the mobile network via an access network (AN)104, which may be a radio access network (RAN). In the present disclosure, the UEs operating in the 5G mobile network may be any suitable type of devices, such as cellular telephones, smart phones, tablet devices, Internet of Things (IoT) devices, and machine-to-machine (M2M) communication devices, to name but a few.

CCNF105includes a plurality of network functions (NFs) which commonly support all sessions for UE102. UE102may be connected to and served by a single CCNF105at a time, although multiple sessions of UE102may be served by different slice-specific core network functions106. CCNF105may include, for example, an access and mobility management function (AMF) and a network slice selection function (NSSF). UE-level mobility management, authentication, and network slice instance selection are examples of common functionalities provided by CCNF105.

Slice-specific core network functions of network slices106are separated into control plane (CP) NFs108and user plane (UP) NFs110. In general, the user plane carries user traffic while the control plane carries network signaling. CP NFs108are shown inFIG. 1Aas CP NF1through CP NF n, and UP NFs110are shown inFIG. 1Aas UP NF1through UP NF n. CP NFs108may include, for example, a session management function (SMF), whereas UP NFs110may include, for example, a user plane function (UPF).

FIG. 1Bis an illustration of a more detailed network architecture100bof the 5G mobile network ofFIG. 1A. As provided in 3GPP standards for 5G (e.g. 3GPP 23.501), network architecture100bfor a 5G mobile network may include an authentication server function (AUSF)116, a unified data management (UDM)118(having a unified data repository or UDR), an AMF112, a policy control function (PCF)114, an SMF120a, and a UPF122a. PCF114may connect with one or more application functions such as an application function (AF)124. UPF122amay connect with one or more data networks (DNs). A plurality of interfaces or reference points N1 through N15 shown inFIG. 1Bmay define the communications and/or protocols between each of the entities, as described in the relevant (evolving) standards documents.

UPF106ais part of the user plane and all other NFs (i.e. AMF112, SMF120a, PCF114, AUSF116, and UDM118) are part of the control plane. Separating user and control planes guarantees that each plane resource to be scaled independently. It also allows UPFs to be deployed separately from CP functions in a distributed fashion. The NFs in the CP are modularized functions; for example, AMF and SMF are independent functions allowing for independent evolution and scaling.

As illustrated inFIG. 1B, NFs such as SMF120aand UPF122aofFIG. 1Bmay be provided as specific instances in a first network slice (e.g. network slice1). Additional instances of NFs for additional network slices may be provided as well, as illustrated by SMF120band UPF122bprovided as additional specific instances in a second network slice (e.g. network slice2).

As described in the standards documents, the mobile network will generally deploy a network slice based on a network slice selection assistance information (NSSAI) provided by UE102. During an initial attach procedure by UE102, the NSSAI is used by RAN104to select the CCNF105. The NSSF in CCNF105selects a network slice instance. In general, network slice instance selection may be based on the NSSAI, the data network name (DNN) of the session, subscription data of UE102, and other parameters. An attach accept message from the network includes an accepted or allowed NSSAI for UE102.

There is a need for reducing a signaling load in mobile networks, such as 5G mobile networks ofFIGS. 1A-1B, as well as simplifying a subscriber management and control over subscribers of UEs in such networks, especially when considering the very large and increasing number of devices (e.g. IoT devices) expected to be connected in such networks.

According to preferred implementations of the present disclosure, the mobile network ofFIGS. 1A-1Bmay be configured for establishing a group session for subscribers associated with a group (i.e. for those subscribers that are provisioned for such group processing). The establishment of a group session according to the present disclosure may be provided in addition to the establishment of sessions for other subscribers individually as is conventional. From the perspective of the mobile network operator, the establishment of a group session in accordance with some implementations may provide for a reduced signaling load in the mobile network, as well as a more simplified and efficient management and control over the subscribers. From the perspective of the owner or controller of the UEs/subscribers of a group, establishment of a group session in accordance with some implementations of may provide for a more simplified and efficient management and oversight over the subscribers, as well as provide a better understanding of the (combined) actual, communication needs for the subscriber group.

Each group of subscribers may be associated with a (unique) group identifier. A plurality of identifiers of subscribers/UEs that are members of the group may be stored in association with the group identifier associated with the group (e.g. in memory or a DB). In some implementations, one or more policies or policy rules for the group may also be associated with the group, or stored in association with a group type identifier which indicates the type of group. The one or more policies or policy rules may indicate one or more parameters for control and management of the group. The one or more polices may indicate one or more parameters that provide an assurance on the level or extent of communications of the group, and/or one or more parameters that provide a limitation or restriction on the level or extent of communications of the group.

FIG. 2is a flowchart200for describing a method for use in establishing a group session for subscribers associated with a group according to some implementations of the present disclosure. The method described in relation toFIG. 2may be an overview and/or generalization of the techniques described in relation toFIGS. 3-12. The method ofFIG. 2may be performed by one or more entities or network function (NF) entities (e.g. an AMF) and/or provided in a server or network device or equipment. The method ofFIG. 2may be embodied as a computer program product including a non-transitory computer readable medium and instructions (e.g. instructions provided in a VNF or NFV module) stored in the non-transitory computer readable medium, where the instructions are executable on one or more processors of the server or network equipment for performing the steps of the method. The method ofFIG. 2, and related techniques described in relation toFIGS. 3-12, may be especially suitable in situations where a relatively large number of devices (e.g. IoT devices) are deployed and have the same or similar communication needs.

Beginning at a start block202ofFIG. 2, a message which includes a group identifier associated with a group is received (step204ofFIG. 2). The message may be associated with the establishment of a session for communications for a UE. The message may be a message from the UE of the subscriber, such as a message for registration of the UE. The message may include network slice selection assistance information (NSSAI) which includes the group identifier.

It is identified whether the message is associated with or from the first or initial subscriber of the group, and/or whether any stored context for the subscriber or group exists (step206ofFIG. 2). If the message is identified to be associated with or from the first or initial subscriber of the group, and/or if any stored context for the subscriber or group is identified to exist at step206, then the method proceeds to step208ofFIG. 2. Otherwise, if the message is identified to be associated with or from a subsequent subscriber of the group, and/or if it is identified that a stored context for the subscriber or group exists at step206, then the method proceeds to step218ofFIG. 2.

For an initial subscriber identified in step206, one or more network functions (NF) in a network slice may be selected or obtained for a group session associated with the initial subscriber/group of subscribers (step208ofFIG. 2). The selection of NFs for the initial subscriber in step208may be viewed as selection of NFs for or on behalf of the entire group of subscribers. The selected NFs may include, for example, an SMF, a PCF, a UPF, or any combination thereof.

One or more polices may be selected or obtained for the group session associated with the initial subscriber/group of subscribers based on the group identifier (step210ofFIG. 2). Further, a set of IP addresses assigned to a plurality of subscribers/UEs in the group may be selected or obtained (step212ofFIG. 2). That is, each IP address of the set is assigned to (or for assignment to) a respective one of the plurality of subscriber identifiers of the group. The selected IP addresses may be provided and/or stored in association with the identifiers of the subscriber/UEs in the group. The set of IP addresses includes an IP address assigned to the initial subscriber of the group, as well as IP addresses pre-assigned to subsequent subscribers of the group.

A context associated with the group session for the initial subscriber/group of subscribers may be created (step212ofFIG. 2). Information related to the group session for the initial subscriber/group of subscribers may be stored in this “group” context, upon or after creation of the context. In particular, the group context may include the group identifier and the identifiers of the subscribers/UEs in the group. In addition, the group context may include the one or more identifiers of the one or more selected NFs (e.g. obtain in relation to step208). Further, the group context may include the one or more selected policies or policy rules of the group (e.g. obtained in relation to step210). Even further, the group context may include the set of IP addressed stored in association with the identifiers of the subscriber/UEs in the group (e.g. obtained in relation to step212).

Processing for communications of the UE for the initial subscriber in the group session makes use of the selected NFs, the one or more selected policies or policy rules, and the selected assigned IP address (step216ofFIG. 2).

For a subsequent subscriber identified in step206, the stored context associated with the group identifier and group session is selected or identified (step218ofFIG. 2). The proper selection or identification of the group context may be made based on the group identifier and/or the identifier of the subsequent subscriber (e.g. performing a comparison of the group identifiers and/or subscriber identifiers for a match). Session establishment for communications of the UE for the subsequent subscriber makes reference and use of the information stored in the group context of the group session (step216ofFIG. 2). That is, session establishment for communications of the UE for the subsequent subscriber uses the selected NFs, the one or more selected policies or policy rules, and the selected assigned IP address from the stored group context.

Thus, processing for the subsequent subscriber involved steps204,206, and208, but not the more complex processing associated with steps208,210,212,214, and216. Processing for each remaining subsequent subscriber of the group may involve the same processing associated with steps204,206,218and220, but not the more complex processing associated with steps208,210,212,214, and216.

FIG. 3Ais a flowchart300for describing a method for use in establishing a group session for subscribers associated with a group according to some implementations of the present disclosure. Beginning at a start block302ofFIG. 3A, a Network Slice Selection Assistance Information (NSSAI) is generated or obtained (step304ofFIG. 3A). The NSSAI includes a group identifier or “Group ID” associated with a group of subscribers. A UE associated with a subscriber of the group may be provisioned with the NSSAI which includes the group identifier (step306ofFIG. 3A). In addition, network entities may be provisioned with the group identifier. The flowchart ends at a finish block308ofFIG. 3A, but may be repeated for additional groups of subscribers.

InFIG. 3B, an illustrative representation of a NSSAI310which includes a group identifier312is shown. Per 5G standards, a NSSAI is defined and intended to include a field for a slice/service type (SST) which refers to the expected network slice behavior in terms of features and services, and a field for a slice differentiator (SD) which is optional information that compliments the slice/service type to differentiate amongst multiple network slices of the same slice/service type. In some preferred implementations of techniques of the present disclosure, the group identifier of the present disclosure is included or encoded in the field for SD of the NSSAI, as indicated inFIG. 3B.

FIG. 4is a message flow diagram400of a method for use in processing a plurality of subscribers of a group according to some implementations of the present disclosure. Additional entities inFIG. 4that are not shown inFIGS. 1A-1Binclude a network repository function (NRF)404, a network exposure function (NEF)406, an application server (AS)408, and a business support system (BSS)410. Also indicated inFIG. 4is a base station or gNodeB (gNB)402for radio communications with UE102.

InFIG. 4, UE102is provisioned with a group identifier corresponding to a group of subscribers (step420ofFIG. 4). The group identifier may be included or encoded as part of the NSSAI (e.g. in the field for SD) associated with the UE102(see e.g. the method ofFIGS. 3A-3B).

In addition, BSS410or other suitable system may perform a group provisioning procedure in order to provision group provisioning information in the mobile network. The group provisioning information may include the group identifier and a plurality of subscriber identifiers associated with the group identifier. The plurality of subscriber identifiers correspond to a plurality of subscribers associated with the group. As illustrated inFIG. 4, BSS410provisions AS408(step422ofFIG. 4), NEF406(step424ofFIG. 4), and UDM/UDR120(step426ofFIG. 4) with the group provisioning information. Subsequently, AS408may perform a group activation procedure to activate a subscription for the group of subscribers. In particular, AS408may perform activation processes with respect to NEF428(step428ofFIG. 4) and UDM/UDR120(step430ofFIG. 4).

FIG. 5Ais a message flow diagram500afor describing a method for use in performing processing of subscribers of a group according to some implementations of the present disclosure.FIG. 5Arelates to processing of the first one of the group of subscribers (e.g. for the first-registered subscriber of the group).

To begin inFIG. 5A, UE102sends a request for registration to the mobile network (step502ofFIG. 5A). The request for registration is received by AMF110. The request for registration may include a subscriber identifier. The request for registration may further include the group identifier or, more specifically, the NSSAI which includes the group identifier.

It is identified whether UE102is the first subscriber of the group to register, and/or whether a group context has not yet been created for the group. If yes, then AMF110sends to UDM/UDR120a request for subscriber data associated with the group (step504ofFIG. 5). The request includes the group identifier or, more specifically, the NSSAI which includes the group identifier. In response, UDM/UDR120retrieves subscriber data associated with the group based on the group identifier. The retrieved subscriber data includes a plurality of subscriber identifiers associated with the group identifier. UDM/UDR120sends a response to the request to AMF110, where the response includes the plurality of subscriber identifiers associated with the group identifier (step506ofFIG. 5A). AMF110receives this information. AMF110creates a group context associated with the group identifier (step508ofFIG. 5A). AMF110associates or includes the plurality of subscriber identifiers with the group context. The group context is stored locally at the AMF110.

Next, AMF110sends to PCF entity114a context establishment request which includes the group identifier or, more particularly, the NSSAI which includes the group identifier (step510ofFIG. 5A). PCF entity114retrieves (e.g. group) access policies based on the group identifier. AMF110receives, from PCF entity114, a response to the context establishment request (step512ofFIG. 5). The response includes the access policies associated with the group identifier. AMF110updates the locally-stored group context with the access policies (step514ofFIG. 5A). AMF110sends to UE102an acceptance to the request for registration (step516ofFIG. 5A). The acceptance includes the access policies associated with the group.

FIG. 5Bis a message flow diagram500bfor describing a method for use in establishing a group session for subscribers associated with a group according to some implementations of the present disclosure. The method shown and described in relation to message flow diagram500bofFIG. 5Brelates to processing of the first one of the group of subscribers (e.g. for the first-session-requesting subscriber of the group). The method ofFIG. 5Bmay be performed (immediately) after the method ofFIG. 5Adescribed above.

To begin inFIG. 5B, UE102sends a PDU session establishment request to the mobile network (step518ofFIG. 5B). The PDU session establishment request, which includes the group identifier (or NSSAI which includes the group identifier), is received by AMF110. It is identified that UE102is the first subscriber of the group to request a PDU session to be established. In response, AMF110sends to session management function (SMF) selection request to NRF204(step520ofFIG. 5B). The request may include the group identifier or, more specifically, the NSSAI which includes the group identifier. In response, NRF204creates an instance of a SMF associated with an SMF identifier. NRF204sends to AMF110an SMF selection response which includes the SMF identifier (step522ofFIG. 5B). AMF110receives this response, and updates the group context with the SMF identifier of the SMF entity (step524ofFIG. 5B).

Subsequently, AMF110sends a session management request to SMF112identified by the SMF identifier (step526ofFIG. 5B). The session management request includes the group identifier or, more specifically, the NSSAI which includes the group identifier. In response, SMF112sends a corresponding PDU CAN session establishment request to PCF114(step528ofFIG. 5B). PCF114, in turn, sends to UDM/UDR120a get group membership request which includes the group identifier (step530ofFIG. 5B). In response, UDM/UDR120retrieves the plurality of subscriber identifiers using the group identifier. UDM/UDR120sends a get group membership response to the request to PCF114(step532ofFIG. 5B), where the response includes the plurality of subscriber identifiers associated with the group identifier. PCF114receives this response. PCF114sends to SMF112a PDU CAN session establishment response (step533ofFIG. 5B).

The response, which is received by SMF112, includes the set of subscriber identifiers associated with the group identifier. Then, SMF112assigns a unique IP address to each subscriber/subscriber identifier in the group (step534ofFIG. 5B). Thus, a set of IP addresses are assigned to the plurality of subscriber identifiers (e.g. IMSIs) associated with the entire group. Session establishment and acknowledgement messages are exchanged between SMF112and UPF106for establishing the PDU session (step536ofFIG. 5B). Step536may particularly include an N4 session establishment message.

SMF112sends to AMF110a session management response to AMF110identified by the SMF identifier (step526ofFIG. 5B). The session management response includes the set of assigned IP addresses associated with the plurality of subscriber identifiers (e.g. IMSIs). AF110receives the session management response, and updates the group context to associate the assigned IP addresses with their corresponding subscriber identifiers (step540ofFIG. 5B).

AMF110then sends a PDU session request to gNB402for establishing the PDU session (step542ofFIG. 5B). The PDU session request may include the IP address assigned to UE102for the PDU session. More particularly, the PDU session request in step542may be an N2 PDU Session Request, non-access stratum (NAS) message. The gNB402then allocates resources of the access network for UE102for the PDU session (step544ofFIG. 5B). AMF110receives from gNB402a PDU session ack (step546ofFIG. 5B).

FIG. 6is a message flow diagram600for describing a method for use in establishing a group session for subscribers associated with a group according to some implementations of the present disclosure.FIG. 6relates to processing of any subsequent one of the group of subscribers, subsequent to the first one of the subscribers of the group (e.g. for any subsequently-registering subscriber of the group). The method ofFIG. 6may be performed after the methods ofFIGS. 5A and 5Bare performed with the first UE102of the group.

To begin inFIG. 6, a subsequent UE602sends a request for registration to the mobile network (step604ofFIG. 6). The request for registration is received by AMF110. The request for registration may include a subscriber identifier. The request for registration may further include the group identifier or, more specifically, the NSSAI which includes the group identifier. It is identified whether UE602is the first subscriber of the group to register, and/or whether a group context has already been created for the group. If not (i.e. UE602is a subsequent subscriber, and/or a group context has already been created for the group), then AMF110accesses the group context (step606ofFIG. 6) and extracts the access policies from the group context (step608ofFIG. 6). Note that the access policies were already/previously obtained by AMF110via PCF entity114in response to the first registration of the first subscriber of the group. AMF110assigns a 5G globally unique temporary identifier (GUTI) to UE602(step610ofFIG. 6). AMF110sends to UE102an acceptance to the request for registration (step612ofFIG. 6). The acceptance includes the access policies associated with the group.

Next, UE602sends a PDU session establishment request to the mobile network (step614ofFIG. 6). The PDU session establishment request, which includes the group identifier (or the NSSAI which includes the group identifier), is received by AMF110. It is identified whether UE602is the first subscriber in the group to request a PDU session, and/or whether a PDU session has not yet been established for the group. If not (i.e. UE602is indeed a subsequent subscriber for the already-established PDU session), then AMF110accesses the group context (step616ofFIG. 6) and extracts from the group context the assigned IP address corresponding to the subscriber's identifier (step618ofFIG. 6). Note that the IP addresses for the entire group were already/previously obtained by AMF110via SMF112in response to the initial establishment of the PDU session.

AMF110then sends a PDU session request to gNB402for establishing the PDU session (step542ofFIG. 5B). The PDU session request may include the IP address assigned to UE102for the PDU session. More particularly, the PDU session request in step542may be an N2 PDU Session Request, non-access stratum (NAS) message. The gNB402then allocates resources of the access network for UE102for the PDU session (step544ofFIG. 5B). AMF110receives from gNB402a PDU session ack (step546ofFIG. 5B).

FIG. 7Ais a flowchart700afor describing a method for use in performing processing of subscribers of a group according to some implementations of the present disclosure. The method ofFIG. 7Amay be performed by a network entity or device in a mobile network, such as an access and mobility management function (AMF) entity in a 5G mobile network.FIG. 7Amay relate to processing of the first one of the group of subscribers (e.g. for the first-registered subscriber of the group).

Beginning at a start block702ofFIG. 7A, an AMF entity may receive, from a user equipment (UE), a request for registration (step704ofFIG. 7A). The request for registration may include a subscriber identifier. The request for registration may further include the group identifier or, more specifically, the NSSAI which includes the group identifier. The AMF entity may send, to a unified data management (UDM) entity, a request for subscriber data (step706ofFIG. 7A). The request for subscriber data includes the group identifier or the NSSAI which includes the group identifier. The AMF entity may receive, from the UDM, a response to the request for subscriber data, where the response includes a plurality of subscriber identifiers associated with the group identifier (step708ofFIG. 7A). The AMF entity may create a group context associated with the group identifier and the plurality of subscriber identifiers (step710ofFIG. 7A). Note that the group identifier in this method may be encoded and communicated in network slice selection assistance information (NSSAI) associated with the UE. The method may continue through a connector A to the method ofFIG. 7B, described below.

FIG. 7Bis a flowchart700bfor describing a method for use in processing of subscribers of a group according to some implementations of the present disclosure. The method ofFIG. 7Bmay be performed by a network entity or device in a mobile network, such as AMF entity in a 5G mobile network.FIG. 7Bmay relate to processing of the first one of the group of subscribers (e.g. for the first-registered subscriber of the group). The method ofFIG. 7Bmay be a separate method, or a continuation of the method ofFIG. 7Avia the connector A.

To begin inFIG. 7B, an AMF entity may send, to a policy and charging function (PCF) entity, a context establishment request which includes the group identifier (step712ofFIG. 7B). The AMF entity may receive, from the PCF entity, a response to the context establishment request, where the response includes access policies associated with the group identifier (step714ofFIG. 7B). The AMF entity may update the group context with the access policies (step716ofFIG. 7B). The AMF entity may send, to the UE, an acceptance to the request for registration, where the acceptance including the access policies (step718ofFIG. 7B). Note that the group identifier in this method may be encoded and communicated in network slice selection assistance information (NSSAI) associated with the UE. The method may continue through a connector B to the method ofFIG. 7C, described below.

FIG. 7Cis a flowchart700cfor describing a method for use in establishing a group session for subscribers associated with a group according to some implementations of the present disclosure. The method ofFIG. 7Cmay be performed by a network entity or device in a mobile network, such as AMF entity in a 5G mobile network.FIG. 7Cmay relate to processing of the first one of the group of subscribers (e.g. for the first-registered or first-session-establishing subscriber of the group). The method ofFIG. 7Cmay be a separate method, or a continuation of the method ofFIG. 7Bvia the connector B.

To begin inFIG. 7C, the AMF entity may receive, from the UE, a PDU session establishment request which includes the group identifier (step720ofFIG. 7C). The AMF entity may send, to a network repository function (NRF) entity, a request for a session management function (SMF) entity (step722ofFIG. 7C). The AMF entity may receive, from the NRF entity, a response to the request for the SMF entity, where the response includes an SMF identifier of the SMF entity (step724ofFIG. 7C). The AMF entity may update the group context with the SMF identifier of the SMF entity (step726ofFIG. 7C). Note that the group identifier in this method may be encoded and communicated in network slice selection assistance information (NSSAI) associated with the UE. The method may continue through a connector C to the method ofFIG. 7D, described below.

FIG. 7Dis a flowchart700dfor describing a method for use in establishing a group session for subscribers associated with a group according to some implementations of the present disclosure. The method ofFIG. 7Dmay be performed by a network entity or device in a mobile network, such as AMF entity in a 5G mobile network.FIG. 7Dmay relate to processing of the first one of the group of subscribers (e.g. for the first-registered or first-session-establishing subscriber of the group). The method ofFIG. 7Dmay be a separate method, or a continuation of the method ofFIG. 7Cvia the connector C.

To begin inFIG. 7D, the AMF entity may send, to the SMF entity, a session request (step728ofFIG. 7D). The session request may include the group identifier or, more specifically, the NSSAI which includes the group identifier. The AMF entity may receive, from the SMF entity, a session acceptance which includes a set of IP addresses assigned to the plurality of subscriber identifiers corresponding to the group of subscribers (step730FIG. 7D). Each IP address of the set is assigned to (or for assignment to) a respective one of the plurality of subscriber identifiers of the group. The AMF entity may update the group context with the plurality of IP addresses assigned to the plurality of subscriber identifiers (step732ofFIG. 7D). Note that the group identifier in this method may be encoded and communicated in network slice selection assistance information (NSSAI) associated with the UE.

FIG. 8Ais a flowchart800afor describing a method for use in establishing a group session for subscribers associated with a group according to some implementations of the present disclosure. The method ofFIG. 8Amay be performed by a network entity or device in a mobile network, such as an AMF entity in a 5G mobile network.FIG. 8Amay relate to processing of any subsequent one of the group of subscribers, subsequent to the first one of the subscribers of the group (e.g. for any subsequently-registering subscriber of the group). The method ofFIG. 8Amay be performed after the methods ofFIGS. 7A-7Dare performed with the first one in the group of subscribers.

Beginning at a start block802ofFIG. 8A, an AMF entity may receive, from a user equipment (UE), a request for registration (step804ofFIG. 8A). The request for registration may include a subscriber identifier. The request for registration may further include the group identifier or, more specifically, the NSSAI which includes the group identifier. The AMF entity may identify, with use of the group identifier, an existing group context stored in association with the group identifier at the AMF entity (step806ofFIG. 8A). The AMF entity may obtain the access policies from the identified group context (step808ofFIG. 8A). Recall that the obtained access policies were previously obtained by the AMF entity via the PCF entity in response to a first registration of a first subscriber of the group of subscribers (step808ofFIG. 8). See e.g. steps714and716ofFIG. 7B. The AMF entity may send, to the UE, an acceptance to the request for registration, where the acceptance includes the obtained group policies (step812ofFIG. 8A). Note that the group identifier in this method may be encoded and communicated in network slice selection assistance information (NSSAI) associated with the UE. The method may continue through a connector A to the method ofFIG. 8B, described below.

FIG. 8Bis a flowchart800bfor describing a method for use in establishing a group session for subscribers associated with a group according to some implementations of the present disclosure. The method ofFIG. 8Bmay be performed by a network entity or device in a mobile network, such as AMF entity in a 5G mobile network.FIG. 8Amay relate to processing of any subsequent one of the group of subscribers, subsequent to the first one of the subscribers of the group (e.g. for any subsequently-registering subscriber of the group). The method ofFIG. 8Bmay be performed after the methods ofFIGS. 7A-7Dare performed with the first one in the group of subscribers. The method ofFIG. 8Bmay be a separate method, or a continuation of the method ofFIG. 8Avia the connector A.

To begin inFIG. 8B, the AMF entity receives, from the UE, a PDU session establishment request which includes the group identifier (step816ofFIG. 8B). The AMF identifies, with use of the group identifier, an existing group context stored in association with the group identifier at the AMF entity (step818ofFIG. 8B). The AMF entity obtains an IP address for the UE from the identified group context (step820ofFIG. 8B). Recall that a plurality of IP addresses associated with a plurality of subscribers identifiers, including the IP address associated with the UE, were previously obtained by the AMF entity via a session management function (SMF) entity in response to a first PDU establishment request of the first subscriber of the group of subscribers (step822ofFIG. 8B). See e.g. steps730and732ofFIG. 7D. Note that the group identifier in this method may be encoded and communicated in network slice selection assistance information (NSSAI) associated with the UE.

FIG. 9is a flowchart900for describing a method for use in establishing a group session for subscribers associated with a group according to some implementations of the present disclosure. The method ofFIG. 9may be performed by a network entity or device in a mobile network, such as an SMF entity in a 5G mobile network.FIG. 9may relate to processing of the first one of the group of subscribers (e.g. for the first-registered or first-session-establishing subscriber of the group).

Beginning at a start block902ofFIG. 9, the SMF entity may receive, from an AMF entity, a session management request associated with a PDU session establishment request from a user equipment (UE) (step904ofFIG. 9). The session management request may include a group identifier. The SMF entity may send, to a policy and charging function (PCF) entity, a corresponding PDU session establishment request which includes the group identifier (step906ofFIG. 9). The SMF entity may receive, from the PCF entity, a response to the corresponding PDU session establishment request, where the response includes the plurality of subscriber identifiers associated with the group identifier (step908ofFIG. 9). The SMF entity may assign a set of IP addresses to a plurality of subscriber identifiers associated with the group identifier (step910ofFIG. 9). The SMF entity may send, to the AMF, a session management response to the session management request, where the response includes the plurality of IP address in association with the plurality of subscriber identifiers (step912ofFIG. 9). Note that the group identifier in this method may be encoded and communicated in network slice selection assistance information (NSSAI) associated with the UE. The method ends at a finish block914ofFIG. 9.

FIG. 10is a message flow diagram1000for describing a method for use in communicating mobile-terminating data to a plurality of subscribers of a group according to some implementations of the present disclosure. The mobile-terminating data may be any suitable data that needs to be sent to the entire group of subscriber/UEs.

InFIG. 10, one or more data packets for the communication of data to a group of subscribers of UEs may be sent from AS408to UPF122(step1002ofFIG. 10). In response, UPF122may send to SMF120a message which includes a data notification for communicating the data (step1004ofFIG. 10). The message may include a group identifier associated with the group of subscribers. In response, SMF120may send to AMF112a message indicating the data notification for communicating the data (step1006ofFIG. 6). Again, the message may include the group identifier.

In response, AMF112may obtain a list of subscriber identifiers for UEs associated with the group identifier. The AMF112may then determine a list of one or more base stations (i.e. gNBs) currently serving the UEs associated with the obtained list of subscriber identifiers of the group (step1008ofFIG. 10). The AMF112may create a list of UEs served by each one of the one or more base stations (step1010ofFIG. 10). For each base station, AMF112may send to the base station a paging list of UEs to page. For example, AMF112may send to gNB402a first paging list of UEs to page (step1012ofFIG. 10) which results in gNB402paging each UE in the list (step1014ofFIG. 10) through one or more paging messages (1016ofFIG. 10). Similarly, for example, AMF112may send to gNB403a second paging list of UEs to page (step1018ofFIG. 10) which results in gNB403paging each UE in the list (step1020ofFIG. 10) through one or more paging messages (step1021ofFIG. 10).

As a UE responds to the paging, a UE service request procedure may be performed for the UE. The UE service request procedure may be, for example, the procedure provided in TS 23.502, section 4.2.3.3. As a result, downlink data may be communicated from AS408to UE102via UPF122(step1022ofFIG. 10). The process is repeated for each UE responding to the paging (e.g. UE103) (step1024ofFIG. 10).

FIG. 11is an illustrative diagram1100of session establishment made for two or more UEs where entities of the mobile network ofFIGS. 1A-1Bare not configured with techniques of the present disclosure described in relation toFIGS. 2-10. Note that, inFIG. 11, the reference numbers include apostrophes for indicating the same entities, devices, functions, or equipment as described above but without incorporation of any of the techniques of the present disclosure.

InFIG. 11, UE102′ communicates with the mobile network for establishing a data session for communicating data. In particular, UE102′ communicates with AMF112′ via gNB402with a communication signaling (i.e. NAS signaling)1102over the N1 interface. AMF112′ communicates with SMF120′ in a session1104over the N11 interface, SMF120′ communicates with PCF114′ in a session1106over the N7 interface and with UPF122′ in a session1140over the N4 interface. A radio bearer1120is established between UE102′ and gNB402′. Data packets of an IP traffic flow1122for UE102′ are communicated in a PDU session11211between gNB402′ and UPF122′ via the N3 interface. The data packets/user data1124are communicated between UPF122′ and a data network (DN)1150′.

Similarly inFIG. 11, UE602′ communicates with the mobile network for establishing a data session for communicating data. In particular, UE602′ communicates with AMF112′ via gNB402with a communication signaling (i.e. NAS signaling)1108over the N1 interface. AMF112′ communicates with SMF120′ in a session1110over the N11 interface, SMF120′ communicates with PCF114′ in a session1112over the N7 interface and with UPF122′ in a session1132over the N4 interface. A radio bearer1130is established between UE602′ and gNB402′. Data packets of an IP traffic flow1131for UE602′ are communicated in a PDU session1132between gNB402′ and UPF122′ via the N3 interface. The data packets/user data1134are communicated between UPF122′ and DN1150′.

FIG. 12is an illustrative diagram1200of session establishment made for two or more UEs of a group, established in accordance with techniques of the present disclosure described in relation toFIGS. 2-10, provided especially for comparison withFIG. 11.

InFIG. 12, UE102communicates with the mobile network for session establishment for the communication of data. UE102is a member of a group of subscribers for group processing by the mobile network. In particular, UE102communicates with AMF112via gNB402with a communication signaling (i.e. NAS signaling)1202over the N1 interface. AMF112communicates with SMF120in a group session1204over the N11 interface, SMF120communicates with PCF114in a group session1206over the N7 interface and with UPF122in a group session1280over the N4 interface. A radio bearer1220is established between UE102and gNB402. Data packets of an IP traffic flow1224for UE102are communicated in a PDU group session1222between gNB402and UPF12via the N3 interface. The data packets/user data1226are communicated between UPF122and the DN1150.

Similarly inFIG. 12, an additional UE602of the group communicates with the mobile network for the communication of data. In particular, UE602communicates with AMF112via gNB402with a communication signaling (i.e. NAS signaling)1208over the N1 interface. Here, AMF112communicates with SMF120over the N11 interface for UE602in the same group session1206, SMF120communicates with PCF114over the N7 interface for UE602using the group session1206, and SMF120communicates with UPF122over the N4 interface for UE602using the same group session1280. A radio bearer1230is established between UE602and gNB402. Data packets of an IP traffic flow1232for UE602are communicated in the same PDU group session1222between gNB402and UPF122via the N3 interface. The data packets/user data1234are communicated between UPF122and DN1150.

Further inFIG. 12, additional UEs603and604of the group communicate with the mobile network for the communication of data. In particular, UEs603and604communicate with AMF112via a (different) gNB403with communication signaling (i.e. NAS signaling)1140and1142, respectively, over the N1 interface. The NFs in the mobile network may use the same group sessions1204,1206,1280for processing these additional UEs603and604. A radio bearer1252is established between UE603and gNB403, and a radio bearer1256is established between UE604and gNB403. Data packets of an IP traffic flow1254for UE603are communicated in a PDU group session1252between gNB403and the UPF122via the N3 interface, and similarly, data packets of an IP traffic flow1258for UE604are communicated in the same PDU group session1252between gNB403and the UPF122via the N3 interface.

Thus, in viewFIG. 12, a technique according to some implementations of the present disclosure may involve maintaining a single session (e.g. a PDU session) between a base station and a UPF for IP data traffic of two or more subscribers of a plurality of subscribers of a group. Put another way, a technique according to some implementations of the present disclosure may involve establishing a session (e.g. a PDU session) between a base station and a UPF for IP data traffic of a first subscriber of a group, and including a second subscriber of the group (e.g. and subsequent subscribers in the group) in the session between a base station and the UPF for IP data traffic of the second subscriber (e.g. and subsequent subscribers in the group).

Similarly, a technique according to some implementations of the present disclosure may involve maintaining a single session or signaling communication between NFs (e.g. between AMF and SMF, between SMF and PCF, and/or between SMF and UPF) for two or more subscribers of a plurality of subscribers of a group. Put another way, a technique according to some implementations of the present disclosure may involve establishing a session or communication signaling between NFs for managing IP data traffic of a first subscriber of a group, and including a second subscriber of the group (e.g. and subsequent subscribers in the group) in the same session or communication signaling between the NFs for managing IP data traffic of the second subscriber (e.g. and subsequent subscribers in the group).

In some alternative implementations of the techniques ofFIGS. 2-12, the subscriber identifier is used to identify (at least the initial) association between the subscriber and the group instead of the group identifier.

FIG. 13is an illustrative representation of a basic network architecture1300of a (4G) Long Term Evolution (LTE)-based mobile network. Network architecture1300of the LTE-based network ofFIG. 13includes a mobility management entity (MME)1308, a serving GPRS support node (SGSN)1310, a home subscriber server (HSS)1312, a service capability exposure function (SCEF)1318, a policy and charging rules function (PCRF)1316, a serving gateway (GW)1306, and a packet data network (PDN) gateway1314. A business support system (BSS)1328may also be connected to the network. A plurality of interfaces shown in network architecture130ofFIG. 13(e.g. LTE-Uu, S1-U, S1-MME, S3, S4, S5, S6a, S10, S11, S12, Gx, Rx, SGi, S6t, an NB REpresentational State Transfer (REST) Application Programming Interface (API)) may define the communications and/or protocols between each of the entities, as described in the relevant standards documents for LTE. An operator may provide an IP service network1320with connection to the network via PCRF1316and PDN gateway1314. The IP service network1320may provide IP services such as IP multimedia subsystem (IMS), packet switched stream (PSS), etc. An application server (AS)1326may connect to the mobile network via SCEF1318.

A user equipment (UE)1302may obtain access to the mobile network via a Universal Terrestrial Radio Access Network (eUTRAN) which may include one or more base stations (eNodeBs or eNBs) and one or more radio network controllers (RNCs). In the present disclosure, the UEs operating in the LTE-based mobile network may be any suitable type of devices, such as cellular telephones, smart phones, tablet devices, Internet of Things (IoT) devices, and machine-to-machine (M2M) communication devices, to name but a few. For additional network access for UEs, one or more additional UTRANs1322and one or more GSM edge radio access networks (GERAN)1324may be connected in the network.

FIG. 14is a process flow diagram1400for describing a method for use in establishing a group session for subscribers associated with a group in the mobile network ofFIG. 13according to some implementations of the present disclosure. Here, the entities, functions, and interfaces of the LTE mobile network represented inFIGS. 13-14may be configured in accordance with the relevant LTE-based standards, with modification, adaptation, and/or additions provided in accordance with the techniques of the present disclosure. The method ofFIG. 14may be especially suitable in situations where a relatively large number of devices (e.g. IoT devices) are deployed and have the same or similar communication needs.

The mobile network ofFIG. 13may be configured for establishing a group session for subscribers associated with a group (i.e. for those subscribers that are provisioned for a group and/or group processing). The processing of subscribers of a group in the mobile network may be provided in addition to the processing of subscribers individually as is conventional. From the perspective of the mobile network operator, the processing of subscribers of a group in accordance with some implementations of the present disclosure may provide for a reduced signaling load in the mobile network, and/or a more simplified and efficient management and control over the subscribers. From the perspective of the owner or controller of the UEs/subscribers of a group, the processing of subscribers of a group in accordance with some implementations of the present disclosure may provide for a more simplified and efficient management and oversight over the subscribers, as well as provide a better understanding of the (combined) actual, communication needs for the subscriber group.

Each group of subscribers may be associated with a (unique) group identifier. A plurality of identifiers of subscribers/UEs that are members of the group may be stored in association with the group identifier associated with the group (e.g. in memory or a DB). In some implementations, one or more policies or policy rules for the group may also be stored in association with the group identifier of the group. The one or more policies or policy rules stored in associated with the group identifier may indicate one or more parameters for control and management of the group. The one or more policies may indicate, for example, one or more quality of service (QoS) parameters for the group, and/or a total bandwidth (e.g. uplink/downlink bandwidth) of the group. More generally, the one or more polices may indicate one or more parameters that provide an assurance on the level or extent of communications of the group, and/or one or more parameters that provide a limitation or restriction on the level or extent of communications of the group.

With reference now to the process flow inFIG. 14, a provisioning system, such as BSS1328, may provision one or more groups of subscribers at each one of a plurality of network entities of the mobile network (process step “0” ofFIG. 14). More particularly, BSS1328may provision the HSS132, the SCEF1318, and the AS1326with one or more groups of subscribers. For example, the network entities may be provisioned with a group identifier and its associated plurality or list of subscriber identifiers of subscribers/UEs that are members of the group. Once a group is provisioned, the group may be referenced by the group identifier over the S6a, S11, S8, and Gx interfaces, as well as the Northbound REST interface between SCEF1318and the AF. AS1326may initiate activation procedures of the group that is provisioned in the network (process step “1” inFIG. 14). In turn, SCEF1318may activate the group in HSS1312(process step “2” inFIG. 14) ad PCRF1316(process step “3” inFIG. 14).

Sometime after group provisioning and activation in the network, UE1302associated with a subscriber of the group may perform an attach to the mobile network (process step “4” inFIG. 14). The performing of the attach may alternatively be referred to performing a registration with a registration message. The attach includes a subscriber identifier (e.g. IMSI). In response, MME1308may request profile and/or subscription data of UE1302from HSS1312, per existing procedures (process step “5” inFIG. 14). Process step “5” may include communicating a message which includes a location update with the subscriber identifier (e.g. IMSI). In response, MME1308may receive from HSS1312the group identifier associated with the group and its associated plurality of subscriber identifiers (process step “6” inFIG. 14).

MME1308may then initiate the creation a group session for the subscriber/group of subscribers by communicating with S/P GW1306/1314(process step “7” inFIG. 14). In turn, P-GW1314may initiate a Gx group session establishment which includes the group identifier (process step “8” inFIG. 14). The Gx group session establishment may be performed with PCRF1316. In response, PCRF1316may respond to P-GW1314with the list of subscriber identities of the group, as well as policy and charging control (PCC) rules associated with the group (process step “9” inFIG. 14).

In response, S/P GW1306/1314may assign a set of IP addresses to the subscriber identifiers (e.g. IMSIs) in the list and send this information to MME1308(process step “10” inFIG. 14). That is, each IP address of the set is assigned to (or for assignment to) a respective one of the plurality of subscriber identifiers of the group. This step may be performed by sending the list to MME1308using Protocol Configuration Options (PCO). The communication to MME1308may include an identifier, such as a tunnel endpoint identifier (TEID), which is assigned to a user plane for the group session. MME1308may retrieve or obtain the IP address associated with the subscriber identifier (e.g. IMSI) from the previous UE attach (i.e. process step “4”), and send to eNB1402an initial context setup message that includes the NAS message for UE1302and the TEID for the selected user plane (process step “11” inFIG. 14). eNB1402may return a NAS message indicating an attach accept, which includes an identifier of a bearer (i.e. an EPS bearer) and the assigned IP address for UE1302(process step “12” inFIG. 14). UE1302may begin sending data packets to eNB1402(process step “13” inFIG. 14), and eNB1402maps the data packets into a GPRS tunneling protocol (GTP-U) tunnel per the TEID received in process step “10” (process step “14” inFIG. 14).

An additional UE1303associated with another subscriber of the group may subsequently perform an attach to the mobile network (process step “15” inFIG. 14). The attach may include a subscriber identifier (e.g. IMSI) of the subscriber. Notably, process steps 5-10 for this additional UE1303need not be performed. Rather, MME1308may identify that UE1303is associated with the group based on its subscriber identifier (process step “16” inFIG. 14). MME1308may retrieve or obtain the IP address associated with the subscriber identifier (e.g. IMSI) from the UE attach (i.e. process step “15”), and send to eNB1402an initial context setup message that includes the NAS message for UE1303and the TEID for the selected user plane (process step “16” inFIG. 14). eNB1402may return a NAS message indicating an attach accept, which includes an identifier of a bearer (i.e. an EPS bearer) and the assigned IP address for UE1303(process step “17” inFIG. 14). UE1303may begin sending data packets to eNB1402(process step “18” inFIG. 14), and eNB1402maps the data packets into the GTP-U tunnel per the TEID previously received in process step “10” (process step “14” inFIG. 14).

FIG. 15is a message flow diagram1500for describing a method for use in communicating mobile-terminating data to a plurality of subscribers of a group in the mobile network described in relation toFIGS. 13-14. The mobile-terminating data may be any suitable data that needs to be sent to the entire group of subscriber/UEs.

InFIG. 15, one or more data packets for the communication of data to a group of subscribers of UEs may be sent from AS408to S/P-GW-U (User Plane)1306/1314(step1502ofFIG. 15). In response, S/P-GW-U1306/1315may send to S/P-GW-C(Control Plane)1306/1314a message which includes a data notification for communicating the data (step1504ofFIG. 15). The message may include a group identifier associated with the group of subscribers. In response, S/P-GW-C1306/1314may send to MME1308a message indicating the data notification for communicating the data (step1506ofFIG. 15). Again, the message may include the group identifier.

In response, MME1308may obtain a list of subscriber identifiers for UEs associated with the group identifier. The MME1308may then determine a list of one or more base stations (i.e. eNBs) currently serving the UEs associated with the obtained list of subscriber identifiers of the group (step1508ofFIG. 15). The MME1308may then create a list of UEs served by each one of the one or more base stations (step1510ofFIG. 15). For each base station, MME1308may send to the base station a paging list of UEs to page. For example, MME1308may send to eNB1402a first paging list of UEs to page (step1512ofFIG. 15) which results in eNB1402paging each UE in the list (step1514ofFIG. 15) through one or more paging messages (1516ofFIG. 15). Similarly, for example, MME1308may send to eNB1403a second paging list of UEs to page (step1518ofFIG. 15) which results in eNB1403paging each UE in the list (step1520ofFIG. 15) through one or more paging messages.

As a UE responds to the paging, a UE service request procedure is performed for the UE. The UE service request procedure may be, for example, the procedure provided in TS 23.502, section 4.2.3.3. As a result, downlink data is communicated from S/P-GW-U1306/1314to UE102(step1522ofFIG. 15). The process is repeated for each UE responding to the paging (e.g. UE103) (step1524ofFIG. 15).

FIG. 16is an illustrative diagram1600of session establishment made for two or more UEs where entities of the mobile network ofFIG. 13are not configured with techniques of the present disclosure described in relation toFIGS. 14-16. Note that, inFIG. 16, the reference numbers include apostrophes for indicating the same entities, devices, functions, or equipment as described above but without incorporation of any of the techniques of the present disclosure.

InFIG. 16, UE1302′ communicates with the mobile network for session establishment for the communication of data. In particular, UE1302′ communicates with MME1308′ via eNB1402′ with a communication signaling (i.e. NAS signaling)1602over the S1/AP interface. MME1308′ communicates with S-GW1306′ in a session1604over the S11(C) interface, S-GW1306′ communicates with P-GW1314′ in a session1606over the S5/GTP-C interface, and P-GW1314′ communicates with PCRF1316′ in a session1608over the Gx interface. A radio bearer1620is established between UE1302′ and eNB1402′. Data packets of an IP traffic flow1624for UE1302′ are communicated over a bearer1622(i.e. an S1 bearer) established between eNB1402′ and S-GW1306′ via the S1-U interface, and communicated over a bearer1626(i.e. an S5 bearer) between S-GW1306′ and P-GW1314′ via the S5/GTP-U interface. The data packets/user data1628are communicated between P-GW1314′ and AS1326′.

Similarly inFIG. 16, UE1303′ communicates with the mobile network for session establishment for the communication of data. In particular, UE1303′ communicates with MME1308′ via eNB1402′ with a communication signaling (i.e. NAS signaling)1610over the S1/AP interface. MME1308′ communicates with S-GW1306′ in a session1612over the S11(C) interface, S-GW1306′ communicates with P-GW1314′ in a session1614over the S5/GTP-C interface, and P-GW1314′ communicates with PCRF1316′ in a session1616over the Gx interface. A radio bearer1630is established between UE1303′ and eNB1402′. Data packets of an IP traffic flow1634for UE1303′ are communicated over a bearer1632(i.e. an S1 bearer) established between eNB1402′ and S-GW1306′ via the S1-U interface, and communicated over a bearer1636(i.e. an S5 bearer) between S-GW1306′ and P-GW1314′ via the S5/GTP-U interface. The data packets/user data1638are communicated between P-GW1314′ and AS1326′.

FIG. 17is an illustrative diagram1700of session establishment made for two or more UEs of a group, established in accordance with techniques of the present disclosure described in relation toFIGS. 14-15, provided especially for comparison withFIG. 11.

InFIG. 17, UE1302communicates with the mobile network for session establishment for the communication of data. UE1302is a member of a group of subscribers for group processing by the mobile network. In particular, UE1302communicates with MME1308via eNB1402with a communication signaling (i.e. NAS signaling)1702over the S1/AP interface. MME1308communicates with S-GW1306for UE1302over the S11 interface in a group session1704, S-GW1306communicates with P-GW1314for UE1302over the S5/GTP-C interface in a group session1706, and P-GW1314communicates with PCRF1316for UE1302over the Gx interface in a group session1708. A radio bearer1720is established between UE1302and eNB1402. Data packets of an IP traffic flow1724for UE1302are communicated over a bearer1722(i.e. an S1 bearer) established between eNB1402and S-GW1306via the S1-U interface, and communicated over a bearer1726(i.e. an S5 bearer) between S-GW1306and P-GW1314via the S5/GTP-U interface. The data packets/user data1728are communicated between P-GW1314and AS1326.

Similarly inFIG. 17, an additional UE1303of the group communicates with the mobile network for the communication of data. In particular, UE1302communicates with MME1308via eNB1402with a communication signaling (i.e. NAS signaling)1710over the S1/AP interface. MME1308communicates with S-GW1306over the S11 interface for UE1303in the same group session1704, S-GW1306communicates with P-GW1314over the S5/GTP-C interface for UE1303in the same group session1706, and P-GW1314communicates with PCRF1316over the Gx interface for UE1303in the sa,e group session1708. A radio bearer1730is established between UE1302and eNB1402. Data packets of an IP traffic flow1732for UE1303are communicated over the same bearer1722(i.e. the S1 bearer) established between eNB1402and S-GW1306via the S1-U interface, and communicated over the same bearer1726(i.e. the S5 bearer) established between S-GW1306and P-GW1314via the S5/GTP-U interface. The data packets/user data1734are communicated between P-GW1314and AS1326.

Thus, in viewFIG. 17, a technique according to some implementations of the present disclosure may involve maintaining a single bearer (e.g. an S1 bearer) between a base station and a gateway for IP data traffic of two or more subscribers of a plurality of subscribers of a group. Put another way, a technique according to some implementations of the present disclosure may involve establishing a bearer (e.g. an S1 bearer) between a base station and a gateway for IP data traffic of a first subscriber of a group, and including IP data traffic of a second subscriber of the group (e.g. and subsequent subscribers in the group) over the same bearer. The IP data traffic flow for the two or more subscribers may be established and maintained via a single tunnel (e.g. the GTP-U tunnel) from use of the same TEID (e.g. mapping the data packets to the same tunnel).

Even further, a technique according to some implementations of the present disclosure may involve maintaining a single session or signaling communication between network entities (e.g. between MME and S-GW, between S-GW and P-GW, and between P-GW and PCRF) for two or more subscribers of a plurality of subscribers of a group. Put another way, a technique according to some implementations of the present disclosure may involve establishing a session or communication signaling between the network entities for managing IP data traffic of a first subscriber of a group, and including a second subscriber of the group (e.g. and subsequent subscribers in the group) in the same session or communication signaling between the network entities for managing IP data traffic of the second subscriber (e.g. and subsequent subscribers in the group).

FIG. 18is a block diagram of a server, network device or equipment1800which may be used in some implementations of the present disclosure. Network equipment1800ofFIG. 18has components which may include one or more processors1812which are coupled to memory1808and to communication interface1806. Interface1806is configured to connect to one or more networks for communications. The one or more processors1812of the network equipment are configured to operate according to instructions1808stored in memory1804, in order to perform techniques of the present disclosure as described above in relation to the Figures. The instructions may be provided as a virtual network function (VNF) or a network function virtualization (NFV) entity.

Thus, methods and apparatus for use in establishing a group session in a mobile network for subscribers of a group are described herein. In an illustrative example of techniques in a 5G mobile network, an entity such as an access and mobility management function (AMF) entity may receive, from a UE, a request for registration which may include network slice selection assistance information (NSSAI). The NSSAI may include the group identifier associated with a group of subscribers. The AMF entity may send, to a unified data management (UDM) entity, a request for subscriber data which includes the group identifier. The AMF entity may receive, from the UDM, a response to the request for subscriber data which includes the plurality of subscriber identifiers corresponding to the group. The AMF entity may create, for a group session, a group context associated with the group identifier and the plurality of subscriber identifiers, and locally store this group context. The AMF entity may obtain selected network functions (NF), selected policies or policy rules, and/or a selected set of assigned IP address for the group, and stores the information in association with the group context. For one or more remaining UEs in the group, the AMF entity may retrieve the information from the locally-stored context for use in session establishment in the group session.

In another illustrative example, an entity of a 5G mobile network such as a session management function (SMF) entity may perform a technique which involves receiving, from an access and mobility management function (AMF) entity (or other suitable entity), a session management request associated with a PDU session establishment request from a user equipment (UE), the session management request including a group identifier; assigning a plurality of IP address to a plurality of subscriber identifiers associated with the group identifier; and sending, to the AMF, a session management response to the session management request, the plurality of IP address in association with the plurality of subscriber identifiers. The technique may further involve sending, to a policy and charging function (PCF) entity, a corresponding PDU session establishment request which includes the group identifier; and receiving, from the PCF entity, a response to the corresponding PDU session establishment request, the response including the plurality of subscriber identifiers associated with the group identifier. The plurality of subscriber identifiers may be a plurality of International Mobile Subscriber Identities (IMSIs). The group identifier may be included and communicated in network slice selection assistance information (NSSAI) associated with the UE. The group of subscribers may be associated with a plurality of Internet of Things (IoT) devices.

As another illustrative example, a technique according to some implementations of the present disclosure may involve generating or obtaining a NSSAI which includes a group identifier associated with a group of subscribers; and provisioning one or more UEs associated with one or more subscribers of the group with the NSSAI which includes the group identifier. Here, the group identifier may be provided as a slice differentiator (SD) or as information in a SD field of the NSSAI.

As yet another illustrative example, a technique according to some implementations of the present disclosure may be performed by an entity (e.g. a MME or AMF) and involve receiving, from a user equipment (UE) associated with a subscriber, a registration message for registration which includes a subscriber identifier of the subscriber; obtaining a plurality of subscriber identifiers which identify a plurality of subscribers of a group of subscribers, the group of subscribers including the subscriber and identified by a group identifier; and creating a context for a group session for the group of subscribers, the context including the group identifier and the plurality of subscriber identifiers. The context may be used for session establishment in the group session for one or more subsequent UEs associated with one or more remaining subscribers of the group. The technique may involve obtaining and storing policy data for the group session in association with the context. In addition, or alternatively, the method may involve obtaining and storing a set of IP addresses in association with the context, the set of IP addresses being respectively assigned to (or for assignment to) the plurality of subscribers of the group. In some implementations, the obtaining comprises obtaining from a home subscriber server (HSS) the plurality of subscriber identifiers which identity the plurality of subscribers of the group based on the subscriber identifier, and in other implementations the registration message includes the group identifier and the obtaining comprises obtaining from a unified data management (UDM) entity the plurality of subscriber identifiers which identify the plurality of subscribers of the group based on the group identifier.

Even another illustrative example includes a technique which may involve maintaining a single session (e.g. a PDU session) between a base station and a UPF for IP data traffic of two or more subscribers of a group, with use of the techniques described herein. A related technique may involve establishing such a session between a base station and a UPF for IP data traffic of a first subscriber of a group, and including a second subscriber of the group (e.g. and one or more subsequent subscribers of the group) in the session between the base station and the UPF for IP data traffic of the second subscriber (e.g. and one or more subsequent subscribers of the group). Even another technique may involve maintaining a single session or signaling communication between network functions (NFs) (e.g. between AMF and SMF, between SMF and PCF, and/or between SMF and UPF) for two or more subscribers of a plurality of subscribers of a group, with use of the techniques herein. A related technique may involve establishing a session or communication signaling between NFs for managing IP data traffic of a first subscriber of a group, and including a second subscriber of the group (e.g. and one or more subsequent subscribers of the group) in the same session for communication signaling between the NFs for managing IP traffic of the second subscriber (e.g. and one or more subsequent subscribers of the group).

Another illustrative example of a technique may involve maintaining a single bearer between a base station and a gateway for IP data traffic of two or more subscribers of a plurality of subscribers of a group, with use of the techniques herein. A related technique may involve establishing a bearer between a base station and a gateway for IP data traffic of a first subscriber of a group, and including IP data traffic of a second subscriber of the group (e.g. and subsequent subscribers in the group) over the same bearer. The IP data traffic flow for the two or more subscribers may be established and maintained via a single tunnel (e.g. mapping the data packets for two or more subscribers over the same tunnel), with use of the techniques herein.

Yet even another illustrative example includes a technique which may involve maintaining a single session or signaling communication between network entities (e.g. between MME and S-GW, between S-GW and P-GW, and/or between P-GW and PCRF) for two or more subscribers of a plurality of subscribers of a group, with use of the techniques herein. A related technique may involve establishing a session or communication signaling between the network entities for managing IP data traffic of a first subscriber of a group, and including a second subscriber of the group (e.g. and subsequent subscribers in the group) in the same session or communication signaling between the network entities for managing IP data traffic of the second subscriber (e.g. and subsequent subscribers in the group).

Note that the components and techniques shown and described in relation to the separate figures may indeed be provided as separate components and techniques, and alternatively one or more (or all of) the components and techniques shown and described in relation to the separate figures are provided together for operation in a cooperative manner.

It will also be understood that, although the terms “first,” “second,” etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first subscriber or UE could be termed a second subscriber or UE, and similarly, a second subscriber or UE could be termed a first subscriber or UE, without changing the meaning of the description, so long as all occurrences of the “first subscriber or UE” are renamed consistently and all occurrences of the “second subscriber or UE” are renamed consistently. The first subscriber or UE and the second subscriber or UE are both subscribers or UEs, but they are not the same subscriber or UE.