Apparatus and method for determining group operating mode on wireless network

Abstract

An operating mode from a plurality of operating modes can be determined (310) based on at least one traffic type originating from a UE. The plurality of operating modes can include at least one group operating mode and an individual operating mode. The at least one group operating mode can support a plurality of UEs grouped into a group of UEs. The at least one group operating mode can support communicating at least one network entity associated message associated with the group of UEs including the UE. The associated message can be associated with the group of UEs. The determined operating mode can be notified (320) to a network entity.

Description

Technical Field

[0001] This disclosure relates to an apparatus and method for determining an operating mode on a wireless network. Background Technology

[0002] Currently, wireless communication devices, such as UEs, use wireless signals to communicate with other communication devices. In IIoT applications, AI inference engines and / or ML algorithms can use real-time datasets collected from a group of sensors / devices to generate a set of real-time control parameters for desired actions at machines or other objects. Similarly, in XR applications such as games, latency-sensitive datasets collected from numerous sensors / devices (e.g., motion devices, cameras, and audio devices) can be used for real-time rendering and virtual control. Attached Figure Description

[0003] To describe how the advantages and features of this disclosure are obtained, the description of this disclosure will be presented with reference to specific embodiments illustrated in the accompanying drawings. These drawings depict only exemplary embodiments of this disclosure and should therefore not be construed as limiting the scope of this disclosure. For clarity, the drawings may have been simplified and are not necessarily drawn to scale.

[0004] Figure 1 This is an example block diagram of a system according to a possible embodiment;

[0005] Figure 2 This is an illustration of an example of a group of associated devices according to possible embodiments;

[0006] Figure 3 Example flowchart illustrating the operation of a device according to a possible embodiment;

[0007] Figure 4 Example flowchart illustrating the operation of a device according to a possible embodiment; and

[0008] Figure 5 This is an example block diagram of a device according to a possible embodiment. Detailed Implementation

[0009] Embodiments provide a method and apparatus for communicating over a wireless network. At least some embodiments provide apparatus and methods for determining operating modes over a wireless network. At least some embodiments provide group communication for IIoT and XR. According to possible embodiments, an operating mode from multiple operating modes can be determined based on at least one service type originating from a UE. The multiple operating modes may include at least one group operating mode and individual operating modes. The at least one group operating mode may support multiple UEs grouped into a UE group. The at least one group operating mode may support at least one network entity conveying messages associated with the UE group containing the UE. The associated messages may be associated with the UE group. The determined operating mode may be notified to the network entity.

[0010] Figure 1 This is an example block diagram of system 100 according to a possible embodiment. System 100 may include a UE 110, at least one network entity 120 and 125, and a network 130. UE 110 may be a wireless wide area network device, user device, wireless terminal, portable wireless communication device, smartphone, cellular phone, flip phone, personal digital assistant, smartwatch, personal computer, tablet computer, laptop computer, selective call receiver, IoT device, or any other user device capable of transmitting and receiving communication signals on a wireless network. At least one network entity 120 and 125 may be a wireless wide area network base station, a NodeB, an eNB, a gNB (e.g., a 5G NodeB), an unlicensed network base station, an access point, a base station controller, a network controller, a TRP, a network entity of a different type from the other network entity, and / or any other network entity that provides wireless access between the UE and the network.

[0011] Network 130 may include any type of network capable of transmitting and receiving wireless communication signals. For example, network 130 may include wireless communication networks, cellular telephone networks, TDMA-based networks, CDMA-based networks, OFDMA-based networks, LTE networks, NR networks, 3GPP-based networks, 5G networks, satellite communication networks, high-altitude platform networks, the Internet, and / or other communication networks.

[0012] In operation, UE 110 can communicate with network 130 via at least one network entity 120. For example, UE 110 can send and receive control signals on a control channel and send and receive user data signals on a data channel.

[0013] For large-scale MTCs with smaller packet sizes, such as smart meter or power grid applications, a network architecture is possible where an aggregator collects data from sensor groups via sidelink communication and relays the data to network entities in the cellular network, rather than directly connecting sensor groups to network entities. Furthermore, 3GPP Rel-16 NR specifies wake-up signals based on group common PDCCH.

[0014] In real-time control and XR applications with AI / ML, the size of packets and the amount of data generated by each sensor / device can be significantly larger (e.g., ultra-high-definition video) compared to low-cost MTC devices such as smart meter sensors. Furthermore, new applications may require data collected from a collection of physically disjoint / remote (i.e., devices located outside the sidelink communication range) yet associated devices (in terms of application-level data). Therefore, network architectures that consider large-scale MTC and some physical layer characteristics (e.g., group common signaling) without considering application-level associations may not fully address the new challenges of real-time control and rendering.

[0015] The following descriptions are excerpts from the 3GPP specification texts 3GPP TS 23.501 (Release 16) and 3GPP TS 33.501 (Release 16), detailing the various identifiers supported in 5G systems, the use of external and internal group IDs to support 5G LAN type services, and updates to subscription temporary identifiers.

[0016] According to 3GPP TS 23.501 (Release 16), 5.9 Identifiers, 5.9.1 General, each subscriber in a 5G system should be assigned a 5G SUPI for use within the 3GPP system. The 5G system supports subscription identification independent of the user equipment identification. Each UE accessing the 5G system should be assigned a PEI.

[0017] 5G systems support the allocation of temporary identifiers (5G-GUTI) to support user confidentiality protection.

[0018] According to 5.9.2, Subscription Permanent Identifier, a globally unique 5G subscription permanent identifier (SUPI) shall be assigned to each subscriber in the 5G system and provided in the UDM / UDR. The SUPI is used only within the 3GPP system and its privacy is specified in TS 33.501

[29] .

[0019] SUPI may contain: IMSI, as defined in TS 23.003

[19] ; ​​or network-specific identifier for private networks, as defined in TS 22.261[2]; operator identifiers for GLI and 5GC operators for supporting FN-BRG, as further described in TS 23.316

[84] ; and operator identifiers for GCI and 5GC operators for supporting FN-CRG and 5G-CRG, as further described in TS 23.316

[84] .

[0020] The SUPI containing a network-specific identifier should take the form of a NAI based on NAIRFC7542

[20] , as defined in TS 23.003

[19] . When the UE needs to indicate its SUPI to the network (e.g., as part of the registration process), the UE provides a hidden form of the SUPI as defined in TS 23.003

[19] . For roaming scenarios, the SUPI should contain the address of the home network (e.g., MCC and MNC in the case of an IMSI-based SUPI). For interoperability with the EPC, the SUPI assigned to a 3GPP UE should always be based on the IMSI so that the UE can present the IMSI to the EPC. The use of the SUPI for W-5GAN is further specified in TS 23.316

[84] .

[0021] According to 5.9.2a, the Subscription Concealed Identifier (SUCI) is a privacy-preserving identifier containing a hidden SUPI. This content is specified in TS 33.501

[29] . The use of SUCI for W-5GAN is further specified in TS 23.316

[84] .

[0022] According to 5.9.3, the Permanent Equipment Identifier (PEI) defines the 3GPP UE used to access the 5G system. The PEI can use different formats for different UE types and use cases. The UE should present its PEI to the network along with an indication of the PEI format it is using. If the UE supports at least one 3GPP access technology (i.e., NG-RAN, E-UTRAN, UTRAN, or GERAN), then the UE must be assigned a PEI in IMEI or IMEISV format.

[0023] Within this scope, the PEI may be one of the following: for a UE that supports at least one 3GPP access technology, such as the IMEI or IMEISV defined in TS 23.003

[19] ; ​​the PEI used in the W-5GAN access scenario further specified in TS 23.316

[84] ; or for a UE that does not support any 3GPP access technology, the IEEE Extended Unique Identifier EUI-64

[113] used by the UE to connect to the 5GC access technology.

[0024] According to 5.9.4, the 5G Globally Unique Temporary Identifier (GUTI) shall be assigned by the AMF to UEs that share both 3GPP and non-3GPP access. The same 5G-GUTI shall be available for accessing both 3GPP and non-3GPP access security contexts within the AMF of a given UE. The AMF may reassign a new 5G-GUTI to the UE at any time. The AMF shall provide the new 5G-GUTI to the UE in accordance with the conditions specified in Clause 6.12.3 of TS 33.501

[29] . When the UE is in CM-IDLE, the AMF may delay providing the new 5G-GUTI to the UE until the next NAS transaction.

[0025] The structure of 5G-GUTI should be:

[0026] <5G-GUTI>:= <guami><5G-TMSI>

[0027] GUAMI identifies one or more AMFs.

[0028] When a GUAMI identifies only one AMF, the 5G-TMSI uniquely identifies the UE within that AMF. However, when an AMF assigns a 5G-GUTI to a GUAMI value that is used by more than one AMF, the AMF should ensure that the 5G-TMSI value used within the assigned 5G-GUTI has not yet been used by other AMFs sharing that GUAMI value. The structure of a globally unique AMF ID (GUAMI) should be as follows:

[0029] <guami> :＝ <mcc> <mnc><AMF Region ID><AMF Set ID><AMF Pointer>

[0030] The AMF Region ID identifies the region, the AMF Set ID uniquely identifies the AMF Set within the AMF Region, and the AMF Pointer identifies one or more AMFs within the AMF Set. Note 1: The AMF Region ID addresses the situation where there are more AMFs in the network than can be supported by the AMF Set ID and AMF Pointer by enabling operators to reuse the same AMF Set ID and AMF Pointer in different regions. Note 2: In the case of SNPN, the PLMN ID can be shared between SNPNs, making the constructed GUAMI not globally unique. However, the PLMN ID is provided together with the NID, separate from the GUAMI, to uniquely identify the selected or supported SNPN in the RRC and N2. Note 3: For details on the structure of the GUAMI field, see TS 23.003

[19] .

[0031] 5G-S-TMSI is a shortened form of GUTI to enable more efficient radio signaling procedures (e.g., during paging and service requests), and is defined as follows:

[0032] <5G-S-TMSI>:=<AMF Set ID><AMF Pointer> <5G-TMSI>

[0033] As specified in TS 38.304

[50] and TS 36.304

[52] for 3GPP access, NG-RAN uses the 10 least significant bits of the 5G-TMSI when determining the time when different UEs are paged. Therefore, the AMF should ensure that the 10 least significant bits of the 5G-TMSI are evenly distributed. As specified in TS 38.331

[28] and TS 36.331

[51] for 3GPP access, the contention resolution procedure for NG-RAN RRC connection establishment assumes a low probability that the same 5G-TMSI is assigned to different UEs by different AMFs. The procedure of the AMF used to assign the 5G-TMSI should take this into account. Note 4: To achieve this, the AMF may, for example, use a random seed number for any procedure it uses when selecting the 5G-TMSI of a UE.

[0034] According to 5.9.5, the AMF Name identifies the AMF. The AMF Name is a globally unique FQDN, and the structure of the AMF Name FQDN is defined in TS 23.003

[19] . An AMF can be configured with one or more GUAMIs. At any given time, a GUAMI with a different AMF Pointer value is associated with only one AMF Name.

[0035] According to 5.9.6, the Data Network Name (DNN) is equivalent to the APN as defined in TS 23.003

[19] . Both identifiers have equivalent meanings and carry the same information. The DNN can be used, for example, to: select the SMF and UPF for a PDU session; select the N6 interface for a PDU session; and determine the policy applied to the PDU session. The wildcard DNN is the value of the DNN field in the list of Subscribed DNNs for Session Management Subscription data as defined in Clause 5.2.3.3 of TS 23.502[3]. The wildcard DNN can be used with the operator’s S-NSSAI to allow subscribers to access any data network supported within a network slice associated with the S-NSSAI.

[0036] According to 5.9.7, the Internal-Group Identifier allows users to associate subscribers with groups in the UDR's subscription data. Groups are identified by the internal-group identifier. Note 1: UEs can belong to a limited number of groups; the exact number is defined in the Phase 3 specification. Note 2: In this version of the specification, group support is defined only in non-roaming scenarios.

[0037] The internal group identifier corresponding to the UE is provided by the UDM to the SMF as part of the session management subscription data, and (when PCC is applied to a PDU session) by the SMF to the PCF. The SMF can use this information to apply local policies and store this information in the CDR. The PCF can use this information to enforce AF requests, as described in clause 5.6.7. The internal group identifier corresponding to the UE is provided by the UDM to the AMF as part of the Access and Mobility Subscription data. The AMF can use this information to apply local policies (e.g., group-specific NAS level congestion control as defined in clause 5.19.7.5).

[0038] According to 5.9.8, the Generic Public Subscription Identifier (GPSI) is required to address 3GPP subscriptions in different data networks outside the 3GPP system. The 3GPP system stores the association between the GPSI and the corresponding SUPI within the subscription data. The GPSI is a public identifier used both inside and outside the 3GPP system. The GPSI is either an MSISDN or an external identifier, see TS 23.003

[19] . If the MSISDN is included in the subscription data, it should be possible to support the same MSISDN value in both 5GS and EPS. Note: There is no implicit one-to-one relationship between the GPSI and SUPI.

[0039] According to 5.9.9, the AMF UE NGAP ID is an identifier used to identify the UE in the AMF at the N2 reference point. The AMF assigns the AMF UE NGAP ID and sends it to the 5G-AN. For the following N2 signaling interactions sent from the 5G-AN to the AMF, the AMF UE NGAP ID is used to identify the UE at the AMF. The AMF UE NGAP ID is unique for each AMF set. The AMF UE NGAP ID may be updated without a change in the AMF or in the event of a change in the AMF, as specified in clause 5.21.2.2.

[0040] According to 5.9.10, the UE Radio Capability ID is a short pointer with the format defined in TS23.003

[19] , which is used to uniquely identify a set of UE radio capabilities (i.e., UE radio capability information). The UE radio capability ID is assigned by the serving PLMN or by the UE manufacturer as follows: - UE manufacturer assignment: The UE radio capability ID may be assigned by the UE manufacturer, in which case it contains the UE manufacturer identification (i.e., vendor ID). In this case, the UE radio capability ID uniquely identifies the set of UE radio capabilities provided by the manufacturer to the UE in any PLMN. - PLMN assignment: If the UE radio capability ID assigned by the UE manufacturer is not used by the UE or the serving network, or is not identified by the serving PLMN UCMF, then the UCMF may assign a UE radio capability ID to the UE corresponding to each different set of UE radio capabilities that can be received from the UE at different times with the PLMN. In this case, the UE radio capability ID received by the UE is applicable to the serving PLMN and uniquely identifies the corresponding set of UE radio capabilities in the PLMN. The PLMN-assigned UE radio capability ID contains a version ID in its format. The version ID value is the value configured in the UCMF when assigning UE radio capability ID values. The version ID value makes it possible to detect whether the UE radio capability ID is current or outdated. Note: If the PLMN is configured to store the PLMN allocation ID in the list requested by the UE manufacturer's allocation operation as defined in clause 5.4.4.1a, then the algorithm used to assign PLMN-allocated UE radio capability IDs should assign different UE radio capability IDs to UEs with different TAC values.

[0041] When the UE radio capability ID is sent, the type of UE radio capability ID is distinguished (assigned by the UE manufacturer or assigned by the PLMN).

[0042] In 5.29, support for 5G LAN-type service is outlined in 5.29.1, and the service requirements for 5G LAN-type service are specified in TS 22.261[2]. A 5G Virtual Network (VN) group consists of a set of UEs using dedicated communications for 5G LAN-type service.

[0043] According to 5.29.2, 5G VN group management supports the management of 5G VN group identification and membership (i.e., the definition of 5G VN group identifiers and membership) and 5G VN group data (i.e., the definition of 5G VN group data). 5G VN group management can be configured by the network administrator or dynamically managed by the AF.

[0044] The characteristics of a 5G VN group are as follows: - 5G VN group identifier: External group ID and internal group ID are used to identify the 5G VN group. - 5G VN group membership: 5G VN group members are uniquely identified by GPSI. Groups as described in clause 5.2.3.3.1 of TS23.502[3] are applicable to 5G LAN type services. - 5G VN group data. 5G VN group data may contain the following parameters: PDU session type, DNN, S-NSSAI and application descriptor, and information related to secondary authentication / authorization (e.g., implementation of allocation via DN-AAA). The information related to secondary authentication / authorization corresponds to the procedure described in clause 5.6.6; which allows, for example, the AF to provide DN-AAA server addressing information and may request the SMF to obtain the UE IP address from the DN-AAA server.

[0045] To support dynamic management of 5G VN group identification and membership, the NEF exposes a set of services to manage (e.g., add / delete / modify) 5G VN groups and 5G VN members. The NEF also exposes services to dynamically manage 5G VN group data. 5G VN groups are identified using an external group ID via the AF. The NEF provides the external group ID to the UDM. The UDM maps the external group ID to an internal group ID. For newly created 5G VN groups, the internal group ID is assigned by the UDM. The NEF can retrieve the internal group ID from the UDM via the Nudm_SDM_Get service operation (external group ID, group identifier translation). The external group ID used for a 5G VN group corresponds to a unique set of 5G VN group data parameters. 5G VN group configuration is provided by the OA&M or by the AF to the NEF.

[0046] When the configuration is provided by the AF, the procedure described in clause 4.15.6.2 of TS 23.502[3] applies to storing 5G VN group identifiers, group membership information, and group data in the UDR as follows: - The NEF provides the external group ID, 5G VN group membership information, and 5G VN group data to the UDM. - The UDM updates the list of subscription data for the corresponding UE in the internal group ID-UDR, if necessary. - The UDM updates the group identifier translation in the group subscription data with the internal group ID, external group ID, and list of group members, if necessary. - The UDM stores / updates the 5G VN group data (PDU session type, DNN and S-NSSAI, application descriptor, information related to secondary authentication / authorization) in the UDR. Note: It is assumed that all members of the 5G VN group belong to the same UDM group ID. The NEF may select a UDM instance that supports any of the UDM group IDs of the members of the 5G VN group.

[0047] If the UE is a member of a 5G VN group, the UDM retrieves the UE subscription data and corresponding 5G VN group data from the UDR and provides the AMF and SMF with the UE subscription data containing the 5G VN group data. The PCF generates URSP rules based on the 5G VN group data. The PCF retrieves the 5G VN group data from the UDR. For modifications to the subscribed 5G VN group data, the PCF receives a Nudr_DM_Notify notification of the data change from the UDR. At the UE policy association establishment point, the PCF receives the internal group ID from the AMF, making the PCF identifier required for generating URSP rules for the UE. The AF can update the UE identifier of the 5G VN group at any time after the initial deployment. In this specification version, only a 1:1 mapping between the DNN and the 5G VN group is supported.

[0048] The PCF delivers 5G VN group configuration information (DNN, S-NSSAI, PDU session type) to each UE belonging to the 5G-LAN group. As described in TS 23.502[3] section 4.2.4.3 and TS 23.503

[45] section 6.1.2.2, the 5G VN group configuration information is delivered from the PCF to the UE in the URSP using the UE configuration update procedure for transparent UE policy delivery.

[0049] According to 5.29.3, PDU session management, as defined for 5GS in clause 5.6, applies to 5G LAN type services and has the following descriptions and enhancements: - The UE accesses 5G LAN type services via a PDU session of IP PDU session type or Ethernet PDU session type. - The PDU session provides access to one and only one 5G VN group. - A dedicated SMF is responsible for all PDU sessions for communication for a given 5G VN group. SMF selection is described in clause 6.3.2. Note 1: The network is configured such that the same SMF is always selected for a given 5G VN group. Note 2: Having a dedicated SMF serving 5G VN does not conflict with the redundancy solution available for achieving high availability. DNN and S-NSSAI are associated with the 5G VN group. The UE uses the PDU session establishment procedure described in TS 23.502[3], clause 4.3.2, to provide a DNN associated with the 5G VN group for access to 5G LAN type services for 5G VN. - During the establishment of a PDU session, secondary authentication as described in Clause 5.6.6 and TS23.502[3], Clause 4.3.2.3, may be performed to authenticate and authorize the UE to access the DNN associated with the 5G VN group. Authentication and authorization of the DNN using secondary authentication means authentication and authorization of the associated 5G VN group. There is no defined 5G VN group-specific authentication or authorization. - SM class subscription data for the DNN and S-NSSAI available in the UDM as described in Clause 5.6.1 applies to the DNN and S-NSSAI associated with the 5G VN group. - Session management related policy controls for the DNN and S-NSSAI as described in TS 23.502[3] apply to the DNN and S-NSSAI associated with the 5G VN group. This also includes the use of URSP for the UE to determine how to route outgoing traffic to the PDU session for the DNN and S-NSSAI associated with the 5G VN group. - Session and service continuity SSC modes 1, 2, and 3, as described in clause 5.6.9, are applicable to N6-based service forwarding for 5G VN communications within associated 5G VN groups. - The PDU session provides unicast, broadcast, and multicast communications for DNN and S-NSSAI associated with the 5G VN group. The PSA UPF determines whether the communication is for unicast, broadcast, or multicast based on the destination address of the received data and performs the unicast, broadcast, or multicast communication processing. - During the PDU session establishment procedure, the SMF retrieves SM subscription data related to 5GLAN type services from the UDM as part of the UE subscription data used for DNN.- To enable N19 service routing, SMF associates PDU sessions established to the same 5G VN group and uses this to configure UPF with group-level N4 sessions containing packet detection and forwarding rules for N19 tunneling forwarding.

[0050] According to 5.29.4, User Plane handling, as defined in item 5.8 for 5GS, applies to 5G LAN type services and has the following description:

[0051] There are three types of service forwarding methods allowed for 5G VN communication: - Based on N6, where UL / DL services for 5G VN communication are forwarded to / from DN; - Based on N19, where UL / DL services for 5G VN group communication are forwarded between PSA UPFs of different PDU sessions via N19. N19 is a shared user plane tunnel based on a PSA UPF connecting a single 5G VN group. - Local switch, where if this UPF is a public PSA UPF for different PDU sessions of the same 5G VN group, then services are transmitted locally through a single UPF.

[0052] The SMF handles the user plane path for 5G VN groups, including: - The SMF can prefer to select a single PSA UPF (for the same 5G VN group) for as many PDU sessions as possible to implement local handover on the UPF. - (If necessary) Establishing N19 tunnels between PSA UPFs to support N19-based service forwarding.

[0053] For Ethernet PDU sessions, the SMF may instruct the UPF to classify frames based on VLAN tags and to add and remove VLAN tags on frames received and transmitted on the N6, as described in clause 5.6.10.2. Note 1: For VLAN tags that handle services on the N6, the TSP ID may also be used as described in clause 6.2.2.6 of TS 23.503

[45] . Further description of user plane management for 5G VN groups is given in clause 5.8.2.13.

[0054] When N6-based service forwarding is anticipated, after the creation of a 5G VN group, the AF can influence service routing for all members of the 5G VN group by providing information identifying the service, a suitable DNAI for selection, and an optional indication of service relevance, along with the 5G VN external group ID identifying the 5G VN group, in the AF request sent to the PCF, as described in 5.6.7. If an optional indication of service relevance is provided, this means that the PDU sessions of 5G VN group member UEs should be relevance via the common DNAI in the user plane of the service. The PCF translates the AF request into a policy applicable to the PDU sessions of the 5G VN group and sends the policy to the SMF. Based on the policy, the SMF (re)selects the DNAI for the PDU sessions and configures its UP path to route services to the selected DNAI. If the policy includes a service relevance indication, then the SMF (re)selects the common DNAI for the PDU sessions, such that services of the 5G VN group are routed to the common DNAI. Note 2: When receiving a new PDU session establishment request for a 5G VN group, to avoid unnecessary N19 tunnels between UPFs, the SMF can check the previously selected UPF for the same 5G VN group and determine whether the previously selected UPF can serve the requested PDU session. Note 3: When a new UPF is selected for a 5G VN group during PDU session establishment, N19 tunnels can be established between the new UPF and other UPFs belonging to the 5G VN group. When there are no more PDU sessions in the 5G VN group within the UPF, the N19 tunnel to the UPF can be released during or after the PDU session release. The establishment or release of N19 tunnels at the UPF is performed within the group level N4 session.

[0055] According to TS 33.501 (version-16), based on 6.12.3, a new 5G-GUTI should only be sent to the UE after successful NAS security activation. The 5G-GUTI is defined in TS 23.003

[19] . Upon receiving a Registration Request message of type "Initial Registration" or "Mobility Registration Update" from the UE, the AMF should send the new 5G-GUTI to the UE during the registration procedure. Upon receiving a Registration Request message of type "Periodic Registration Update" from the UE, the AMF should send the new 5G-GUTI to the UE during the registration procedure.

[0056] After receiving a service request message sent by the UE in response to a paging message, the AMF should send a new 5G-GUTI to the UE. This new 5G-GUTI should be sent before the current NAS signaling connection is released. Note 1: More frequent 5G-GUTI reallocation is required compared to the above-mentioned situation, such as after a service request message from the UE is not triggered by the network. Note 2: It is necessary to implement the generation of a 5G-GUTI containing a 5G-TMSI that uniquely identifies the UE within the AMF. The generation of the 5G-TMSI should follow best practices for unpredictable identifier generation. The new I-RNTI should only be sent to the UE after successful activation of AS security. During the RRC recovery procedure or RNAU procedure, when the UE transitions to the RRC inactive state requested by the gNB, the gNB should assign a new I-RNTI to the UE.

[0057] In the descriptions of the various solutions, the UE, sensors, and devices are used interchangeably. Additionally, 'group operation mode' and 'group communication mode' are used interchangeably.

[0058] To support multiple ID assignments for various group communication modes, according to one embodiment, each device in an associated device group can execute an RRC connection procedure (and additional registration procedure) including a separate random access procedure to the cell, and can receive information of at least one temporary identifier associated with the group communication mode, in addition to a temporary identifier associated with the individual communication mode. During RRC connection establishment, reconstruction, or recovery procedures, devices in the associated device group can send group identification information (i.e., at least one temporary identifier associated with the group communication mode). Once all devices in the group are registered and connected, and identified as related based on group identification information and / or user subscription information, one or more network entities (e.g., gNBs) can coordinate and configure the device group in a group-specific DRX mode. All or part of an associated device group connected to the same cell can be configured with a group-specific RNTI for delivering group-specific DL messages.

[0059] Figure 2 Figure 200 illustrates an example of an associated device group according to a possible embodiment. Depending on the location and cell coverage of the associated device group, the associated device group may be connected to the same or different cells, such as cells A and B. In one example, all devices are connected to the same cell. In another example shown in Figure 200, some devices are connected to one cell, and other devices are connected to another cell. In other examples, some devices are in carrier aggregation and / or dual connectivity mode, and the serving cell containing the SpCell (PCell of MCG and SGC) may be different for different devices.

[0060] In one implementation, group identification information based on subscription identifiers (e.g., IMSI, SUPI, GPSI) of the associated device group is pre-configured and recorded / stored in the 3GPP system (and / or other networks). Alternatively, group identification information based on permanent device identifiers (e.g., IMEI) is pre-defined and recorded in the 3GPP system (and / or other networks). Once devices in the associated device group complete the registration process (i.e., establish a user context in the network), information about the device's association with the group is retrieved from one or more network function entities (e.g., UDRs) for synchronization operations (e.g., synchronization paging of the associated device group).

[0061] In another implementation, when a device in an associated device group performs a registration procedure, the AMF assigns multiple temporary identifiers, such as 5G-GUTI, 5G-TMSI, 5G-S-TMSI, or I-RNTI, to the device. A particular temporary identifier among these multiple temporary identifiers is associated with a specific group operating mode or individual operating mode of a specific subgroup of devices from the associated device group. The device may explicitly and / or implicitly receive information about the multiple temporary identifiers. For example, the device may explicitly receive an indication of a temporary identifier and derive other temporary identifiers from the indicated temporary identifier.

[0062] In one instance, the device receives a modified 5G-GUTI structured from 'N' 5G-TMSIs, as follows:

[0063] <5G-GUTI>:= <guami><5G-TMSI_1><5G-TMSI_2>…<5G-TMSI_N>

[0064] Where 5G-TIMSI_n represents a temporary identifier associated with the nth group operation mode.

[0065] The 5G-S-TMSI_n used for the nth group operation mode is a shortened form of GUTI to enable more efficient radio signaling procedures (e.g., during paging and service requests) and is defined as follows:

[0066] <5G-S-TMSI_n>:=<AMF Set ID><AMF Pointer> <5G-TMSI_n>

[0067] The higher layers of the device (e.g., the application layer) select a specific group communication mode 'x', and the device's RRC layer includes a temporary identifier 5G-S-TMSI_x associated with the group communication mode 'x' in an RRC message (e.g., an RRCSetupRequest message).

[0068] As specified in TS 38.304 and TS 36.304 for 3GPP access, NG-RAN uses the 10 least significant bits of the 5G-TMSI when determining the paging time for different UEs. In other words, the paging frame (PF) and paging timing (PO) for a particular device are determined based on the UE_ID, where the UE_ID is set to 5G-S-TMSI mod 1024. For power savings at the device, AMF ensures that the 'N' 5G-TMSIs allocated to the device have a common 10 least significant bits, resulting in the same UE_ID, and therefore the same PF and PO for the N 5G-TMSIs.

[0069] In another instance, the device receives information about multiple fullI-RNTI values ​​and / or multiple shortI-RNTI values ​​(e.g., the RRC parameter 'SuspendConfig') in the RRC_INACTIVE state configuration, where each fullI-RNTI value and / or each shortI-RNTI value is associated with a specific group operation mode. In the RRC_Inactive state, the device includes a temporary identifier, a fullI-RNTI, or a shortI-RNTI value associated with the selected group communication mode in the RRC recovery request message to request the recovery of the selected group communication mode.

[0070] In other instances, the device receives information on multiple C-RNTI values, each associated with a specific group operation mode. Devices in the RRC_Connected state include the C-RNTI value associated with the selected group communication mode in Msg3 during a 4-step random access procedure or in MsgA PUSCH during a 2-step random access procedure.

[0071] Regarding the indication of the preferred communication mode, according to one embodiment, the device can operate in either a group communication mode or an individual communication mode, and the preferred operating mode can be indicated based on the service type initiated by one or more devices. The group communication mode can support both synchronous group communication and individual communication of multiple devices, while the individual communication mode only supports individual communication.

[0072] In one implementation, the device may, for example, notify a specific operating mode during an RRC connection or RRC recovery procedure by including an indication of a specific operating mode in an RRC establishment request message, RRC reconstruction request message, or RRC recovery request message, as illustrated in Examples 1, 2, and 3 below. If the device indicates a group communication mode, one or more network entities may send paging messages to other devices in the group.

[0073] Example 1: RRCSetupRequest message

[0074]

[0075] Example 2: RRCReestablishmentRequest message

[0076]

[0077]

[0078] Example 3: RRCResumeRequest message

[0079]

[0080]

[0081] In another embodiment, the device may be configured with separate RLC bearer configurations (e.g., RRC parameter RLC-BearerConfig), separate logical channel configurations (e.g., RRC parameter LogicalChannelConfig), and / or separate RLC mode configurations within the RLC bearer configurations (e.g., RRC parameter RLC-Config), separate SR configurations within the logical channel configurations (e.g., RRC parameter SchedulingRequestToAddMod), and / or separate random access configurations for group communication modes and individual communication modes, respectively.

[0082] In one instance, the device may notify a specific operating mode by selecting an SR resource of an SR configuration associated with that specific operating mode and transmitting an SR on the selected SR resource. In another instance, the device may notify a specific operating mode by selecting a random access resource of a random access configuration associated with that specific operating mode (e.g., a PRACH preamble and / or PRACH time and frequency resources) and performing a RACH procedure on the selected random access resource. In still other instances, the device may explicitly indicate the specific operating mode in the MsgA PUSCH or Msg3 PUSCH during the random access procedure.

[0083] For paging, UL timing alignment, and wake-up for group communications, according to one embodiment, for event-triggered group communications (e.g., event-triggered real-time data collection), an RRC connection attempt by one device may invoke the RRC connection procedures of other devices in the associated device group. That is, a network entity initiates paging of other devices in the group in response to the receipt of an RRC connection request or RRC recovery request from one device in the group. The network entity may include an AMF, one or more gNodeBs, and / or one or more other network function entities.

[0084] In one implementation, the device initiating the RRC connection establishment or RRC connection restoration procedure includes its own UE identifier (e.g., 5G-S-TMSI, I-RNTI) associated with a specific group operating mode in the RRC connection request message or RRC restoration request message. Upon receiving an RRC message containing the UE identifier associated with the specific group operating mode, the network entity determines a subset of devices from the associated device group that need to be paged and sends one or more paging messages to the subset of devices. At the paging record of the specific paged UE in the paging message, the network entity includes the UE identifier associated with the specific group operating mode of the paged UE (e.g., NG-5G-S-TMSI-modeX, I-RNTI-Value-modeX as shown in Example 4 below).

[0085] It should be noted that the sensor / device may be part of multiple groups. Including a UE identifier associated with a specific group operating mode allows specific functionality within the paging UE to be "activated," such as audio only being activated via paging (i.e., the UE should only provide audio data in response to paging, even if video data may also be available).

[0086] Example 4: Paging message

[0087]

[0088] In another implementation, the device initiating the RRC connection establishment procedure or the RRC connection restoration procedure indicates a group communication mode. In response to receiving a request for a group communication mode, the network entity sends one or more paging messages to the associated device group. The network entity includes in the paging message an indication of the group communication mode at the paging record of the specific paging UE in the associated device group, as shown in Example 5 below.

[0089] Example 5: Paging Message

[0090]

[0091] According to another embodiment, if all devices in the associated device group are in DRX mode with RRC_Connected state, then after receiving an SR from a device in the group, or after receiving a random access pre-synchronization code and subsequent Msg3PUSCH (or after receiving a 2-step RACH pre-synchronization code and MsgA PUSCH), a network entity containing one or more gNodeBs may trigger a random access procedure based on PDCCH order for other devices in the group that are not uplink synchronized (i.e., the UL timing alignment timer has expired). Alternatively or additionally, the network entity may transmit a wake-up signal / channel to other devices in the group.

[0092] In one implementation, the PDCCH of the command random access procedure and / or wake-up signal / channel may include an indication of the communication mode, such as a specific group communication mode or an individual communication mode.

[0093] In other embodiments, if the group of associated devices is located in several adjacent cells, the network entity can configure the group of associated devices using a group area smaller than the tracking area (for idle state) or the RAN notification area (for inactive state). If the network entity performs paging according to a "group communication mode," that is, paging the group of associated devices for group communication, the network entity sends one or more paging messages intended for the group of associated devices only in the cell corresponding to the group area. In one instance, if all devices in the group are connected to the same cell, the network entity sends a paging message in only one cell.

[0094] In another embodiment, the UE may indicate a specific group communication mode along with its corresponding access priority in the RRC parameter 'EstablishmentCause' (for RRC establishment request messages) or 'ResumeCause' (for RRC recovery request messages). Depending on the priority of the data in the specific group communication mode, each group communication mode may be assigned a different access priority.

[0095] Figure 3 A flowchart 300 illustrates an example of the operation of a wireless communication device, such as UE 110, according to a possible embodiment. At 310, an operating mode from multiple operating modes can be determined based on at least one service type originating from the UE. The multiple operating modes may include at least one group operating mode and individual operating modes. The at least one group operating mode may support multiple UEs grouped into a UE group. The at least one group operating mode may support at least one network entity conveying messages associated with the UE group containing the UE. The associated messages may be associated with the UE group. Communication may include transmission and / or reception. The at least one network entity may be the same as or different from the network entity notified of the determined operating mode. For example, in the group operating mode, the UE group may be in the same or different cells. At 320, the determined operating mode may be notified to the network entity.

[0096] According to possible embodiments, information from multiple identifiers can be received. A first identifier among the multiple identifiers may be associated with a specific group operating mode among multiple different group operating modes. A second identifier among the multiple identifiers may be associated with an individual operating mode. Notifying the network entity of the determined operating mode may include transmitting an indication of the identifier associated with the determined operating mode to the network entity. According to possible embodiments, a specific group operating mode may be associated with a UE group.

[0097] According to possible implementations, receiving information from multiple identifiers may include receiving an extended 5G-GUTI. The extended 5G-GUTI may include multiple 5G-TMSIs. According to possible implementations, receiving information from multiple identifiers may include receiving multiple I-RNTIs. According to possible implementations, receiving information from multiple identifiers may include receiving multiple C-RNTIs.

[0098] According to possible implementations, the transmission indication may include an indication of an identifier associated with the determined operating mode transmitted in the RRC message. The RRC message may contain an RRC establishment request message, an RRC recovery request message, and / or an RRC reconstruction request message.

[0099] According to a possible implementation, an SR resource associated with the determined operating mode can be selected. The network entity is then notified that the determined operating mode can include SR transmission on the selected SR resource.

[0100] According to possible embodiments, random access resources associated with the determined operating mode can be selected. Notifying the network entity of the determined operating mode may include performing a random access procedure based on the selected random access resources. For example, multiple RA configurations may exist, each of which can be associated with an operating mode. Furthermore, a single RA configuration may exist with different RA resources, where different RA resources can be associated with different operating modes.

[0101] According to possible embodiments, each of the multiple operating modes may correspond to a specific access priority. Notifying the network entity of the determined operating mode may include sending an RRC message containing the determined operating mode along with the corresponding access priority in the RRC parameters of the RRC message. According to possible embodiments, the RRC parameters may include the 'EstablishmentCause' parameter in the RRC Establishment Request message and / or the 'ResumeCause' parameter in the RRC Resume Request message.

[0102] According to possible embodiments, a paging message intended for a UE can be received. The paging message may contain information about a specific operating mode from multiple operating modes. For example, after an event, a UE may send a message that can trigger paging messages to other UEs. According to possible embodiments, for event-triggered group communication (e.g., event-triggered real-time data collection), an RRC connection attempt by one device may invoke the RRC connection procedures of other devices in the associated device group. That is, a network entity initiates paging of other devices in the group in response to the receipt of an RRC connection request or RRC recovery request from one device in the group.

[0103] According to a possible embodiment, a physical downlink control channel (PDCCH) can receive commands to the UE's random access procedure. The PDCCH may contain information about a specific operating mode from multiple operating modes. The operating mode may be explicitly or implicitly indicated. For example, a specific RACH resource may implicitly indicate the operating mode.

[0104] According to a possible embodiment, a PDCCH indicating wake-up for PDCCH monitoring can be received. The PDCCH indicating wake-up can indicate a specific operating mode from multiple operating modes.

[0105] According to possible embodiments, at least one group operation mode can support both group communication of multiple UEs including a UE and individual communication of individual UEs among the multiple UEs. An individual operation mode can support only individual communication.

[0106] Figure 4 A flowchart 400 illustrates an example of the operation of a wireless communication device, such as network entity 120, according to a possible embodiment. At 410, information about a preferred operating mode can be received from a UE. The preferred operating mode may be determined to be a group operating mode. The group operating mode may include multiple UEs grouped into a UE group. The group operating mode may be associated with a UE group and UEs. The group operating mode may support at least one network entity conveying messages associated with a UE group containing UEs. The associated messages may be associated with the UE group. At 420, an indication of the group operating mode can be transmitted to the UE group in response to the preferred operating mode for the UE being a group operating mode.

[0107] According to possible embodiments, the group operation mode may be a first group operation mode. The UE group may be a first UE group. A preferred operation mode for the UE may be determined to be a second group operation mode. In response to the preferred operation mode for the UE being the second group operation mode, an indication of the second group operation mode may be transmitted to the second UE group. The second group operation mode may be associated with the second UE group and the UE. The second UE group may be different from the first UE group because at least one UE in each group may be different.

[0108] According to possible embodiments, transmitting an indication of a group operating mode to a UE group may include transmitting a paging message containing the indication of the group operating mode to the UE group. The paging message may be at least one paging message. According to possible embodiments, an RRC message may be received from a UE in the UE group. It may be determined that the RRC message invokes a connection procedure for a UE in the UE group. Transmitting the paging message may include transmitting the paging message in response to determining that the RRC message invokes a connection procedure in the UE group. For example, after an event, a UE may send a message that can trigger a paging message to other UEs. According to possible embodiments, for event-triggered group communication (e.g., event-triggered real-time data collection), an RRC connection attempt by one device may invoke the RRC connection procedure of other devices in the associated device group. That is, a network entity initiates paging of other devices in the group in response to receiving an RRC connection request or RRC recovery request from one device in the group.

[0109] It should be understood that, regardless of the specific steps shown in the figures, various additional or different steps may be performed depending on the embodiment, and one or more of the specific steps may be rearranged, repeated, or completely eliminated depending on the embodiment. Furthermore, some of the steps being performed may be repeated simultaneously on an ongoing or continuous basis while other steps are being performed. Additionally, different steps may be performed through different elements or in a single element of the disclosed embodiments. Furthermore, network entities such as base stations, transmission and reception points, mobility management entities, or other network entities may perform reciprocal operations of the UE. For example, a network entity may transmit signals received by the UE and may receive signals transmitted by the UE. The network entity may also process and manipulate the transmitted and received signals.

[0110] Figure 5 This is an example block diagram of a device 500, such as UE 110, network entity 120, or any other wireless communication device disclosed herein, according to possible embodiments. Device 500 may include: a housing 510; a controller 520 coupled to the housing 510; an audio input and output circuitry 530 coupled to the controller 520; a display 540 coupled to the controller 520; a memory 550 coupled to the controller 520; a user interface 560 coupled to the controller 520; a transceiver 570 coupled to the controller 520; at least one antenna port 575, such as at least one antenna, coupled to the transceiver 570; and a network interface 580 connected to the controller 520. Device 500 may not necessarily include all the illustrated elements used in the different embodiments of this disclosure. Device 500 may perform the methods described in all embodiments.

[0111] Display 540 may be a viewfinder, LCD, LED display, OLED display, plasma display, projection display, touchscreen, or any other device for displaying information. Transceiver 570 may be one or more transceivers that may include a transmitter and / or receiver. Audio input and output circuitry 530 may include a microphone, speaker, transducer, or any other audio input and output circuitry. User interface 560 may include a keypad, keyboard, buttons, touchpad, joystick, touchscreen display, another additional display, or any other device suitable for providing an interface between a user and an electronic device. Network interface 580 may be a USB port, Ethernet port, infrared transmitter / receiver, IEEE 1394 port, wireless transceiver, WLAN transceiver, or any other interface that can connect the device to a network, device, and / or computer and can transmit and receive data communication signals. Memory 550 may include RAM, ROM, EPROM, optical memory, solid-state memory, flash memory, removable memory, hard disk drive, cache memory, or any other memory that can be coupled to the device.

[0112] Device 500 or controller 520 can run any operating system, such as Microsoft. Android TM Or any other operating system. The device operating software can be written in any programming language, such as C, C++, Java, or Visual Basic. The device software can also run on an application framework, for example, frame,. The framework or any other application framework. The software and / or operating system may be stored in memory 550, elsewhere on device 500, in cloud storage, and / or anywhere the software and / or operating system can be stored. For example, the coding for operation may be implemented as firmware programmed into ROM. Device 500 or controller 520 may also use hardware to implement the disclosed operations. For example, controller 520 may be any programmable processor. Furthermore, controller 520 may perform some or all of the disclosed operations. For example, cloud computing may be used to perform at least some operations, and controller 520 may perform other operations. At least some operations may also be performed by computer-executable instructions executed by at least one computer processor. The disclosed embodiments may also be implemented on general-purpose or special-purpose computers, programmable microprocessors or microprocessors, peripheral integrated circuit elements, application-specific integrated circuits or other integrated circuits, hardware / electronic logic circuits such as discrete element circuits, programmable logic devices such as programmable logic arrays, field-programmable gate arrays, etc. Generally, controller 520 may be any controller or one or more processor devices capable of operating the device and implementing the disclosed embodiments. Some or all of the additional components of device 500 may also perform some or all of the operations of the disclosed embodiments.

[0113] In operation, device 500 can perform the methods and operations of the disclosed embodiments. Transceiver 570 can transmit and receive signals, including data signals and control signals that may contain corresponding data and control information. Controller 520 can generate and process the transmitted and received signals and information.

[0114] In operation according to a possible embodiment, controller 520 may determine an operating mode of multiple operating modes based on at least one service type originating from device 500. The multiple operating modes may include at least one group operating mode and an individual operating mode. The at least one group operating mode may support multiple UEs grouped into a UE group. The at least one group operating mode may support at least one network entity conveying messages associated with the UE group containing the device. The associated messages may be associated with the UE group. Transceiver 570 may notify the network entity of the determined operating mode.

[0115] According to possible implementations, transceiver 570 may receive information from multiple identifiers. A first identifier among the multiple identifiers may be associated with a specific group operating mode among multiple different group operating modes. A second identifier among the multiple identifiers may be associated with an individual operating mode. Notifying the network entity of the determined operating mode may include transmitting an indication of the identifier associated with the determined operating mode to the network entity.

[0116] Depending on the possible implementation, controller 520 may select the SR resource of the SR configuration associated with the determined operating mode. The network entity is then notified that the determined operating mode may include SR transmission on the selected SR resource.

[0117] According to possible implementations, controller 520 may select random access resources of a random access configuration associated with the determined operating mode. Notifying network entities of the determined operating mode may include performing a random access procedure based on the selected random access resources.

[0118] According to a possible implementation, transceiver 570 can receive paging messages intended for a device. The paging message may contain information about a specific operating mode from multiple operating modes.

[0119] In AI / ML-based IIoT and XR applications, real-time datasets collected from a group of devices can be used to generate a set of real-time control parameters and / or desired actions at machines or other objects. For real-time control and / or real-time rendering of machines or other objects, all or most of the necessary data from the group of devices must be successfully received within a certain time window. Additionally, the group of devices can simultaneously return to sleep or wake up for synchronized operation.

[0120] The network architecture in which the aggregator collects data from a group of devices via sidelink communication and relays the data to the cellular network is suitable for low-cost MTC devices with small packet sizes. The wake-up signal based on the group common PDCCH specified in 3GPP Rel-16 NR may not be directly applicable to one or more remote devices associated with an application layer level. At least some embodiments provide methods for efficient communication with groups of devices / UEs associated at the application layer level.

[0121] A group of one or more associated devices is directly connected to one or more network entities, and the network entities coordinate to synchronous or pseudo-synchronous connection management and DRX operation services for the associated device group. This can effectively handle use cases such as real-time control and XR applications, where the size of packets and the amount of data generated by each device can be much larger than that generated by low-cost MTC devices, but the device group needs to operate in a coordinated manner.

[0122] According to at least some embodiments, each device in the associated device group individually executes the RRC connection procedure to the cell. Furthermore, during the registration procedure of devices from the group, the AMF assigns multiple temporary identifiers, such as 5G-TMSI, to the devices, wherein a particular temporary identifier among the multiple temporary identifiers is associated with a specific group operating mode of a specific subgroup of devices from the group or with an individual operating mode.

[0123] According to at least some embodiments, the device can operate in a group communication mode or an individual communication mode, and can select the preferred operating mode based on service type notifications initiated by one or more devices.

[0124] According to at least some embodiments, for event-triggered group communication, an RRC connection attempt by one device may invoke the RRC connection procedures of other devices in the group. A network entity initiates paging of other devices in the group in response to receiving an RRC connection request or RRC recovery request from one device.

[0125] At least some embodiments may provide a method in a UE. The method may include determining an operating mode from multiple operating modes based on at least one service type derived from the UE. The method may include notifying a network entity of the determined operating mode. The multiple operating modes may include at least one group operating mode and an individual operating mode.

[0126] According to possible embodiments, the method may include receiving information about a plurality of identifiers. A specific identifier among the plurality of identifiers may be associated with a specific group of operating modes, and an identifier among the plurality of identifiers may be associated with an individual operating mode. Notifying a network entity of the determined operating mode may include transmitting an indication of the identifier associated with the determined operating mode to the network entity.

[0127] According to possible implementations of the above embodiments, a specific group operating mode is associated with a specific device group. According to possible implementations of the above embodiments, receiving information about multiple identifiers includes receiving an extended 5G-GUTI, wherein the extended 5G-GUTI includes multiple 5G-TMSIs. According to possible implementations of the above embodiments, receiving information about multiple identifiers includes receiving multiple I-RNTIs. According to possible implementations of the above embodiments, receiving information about multiple identifiers includes receiving multiple C-RNTIs. According to possible implementations of the above embodiments, an indication of the identifier associated with the determined operating mode is transmitted in the RRC message. According to possible examples of the above implementations, the RRC message includes at least one of an RRC establishment request message, an RRC recovery request message, and an RRC reconstruction request message.

[0128] According to a possible embodiment, notifying a network entity of the determined operating mode includes selecting a scheduling request (SR) resource of an SR configuration associated with the determined operating mode and transmitting the SR on the selected SR resource. According to a possible embodiment, notifying a network entity of the determined operating mode includes selecting a random access resource of a random access configuration associated with the determined operating mode and executing a random access procedure based on the selected random access resource.

[0129] According to possible embodiments, each of the plurality of operating modes corresponds to a specific access priority. Notifying the network entity of the determined operating mode includes indicating the determined operating mode along with the corresponding access priority in the RRC parameters. According to a possible implementation of the above embodiments, the RRC parameters include at least one of the parameter 'EstablishmentCause' in the RRC Establishment Request message and the parameter 'ResumeCause' in the RRC Resume Request message.

[0130] According to possible embodiments, the method may include receiving a paging message intended for a UE, wherein the paging message includes indications of operating modes from a plurality of operating modes. According to possible embodiments, the method may include receiving a command to the Physical Downlink Control Channel (PDCCH) of the UE's Random Access Procedure, wherein the PDCCH includes indications of operating modes from a plurality of operating modes. According to possible embodiments, the method may include receiving a wake-up PDCCH indicating PDCCH monitoring, wherein the wake-up PDCCH includes indications of operating modes from a plurality of operating modes. According to possible embodiments, at least one group operating mode includes both synchronous group communication of multiple UEs including the UE and individual communication. Individual operating modes include only individual communication.

[0131] At least some embodiments provide methods in a network entity. The method may include receiving information about a preferred operating mode from a UE. The method may include transmitting an indication of a first group operating mode to a first UE group in response to receiving information that the preferred operating mode for the UE is a first group operating mode. The first group operating mode is associated with the first UE group and the UE. According to a possible embodiment, the method may include transmitting an indication of a second group operating mode to a second UE group in response to receiving information that the preferred operating mode for the UE is a second group operating mode. The second group operating mode is associated with the second UE group and the UE. According to a possible embodiment, transmitting the indication of the first group operating mode to the first UE group includes transmitting at least one paging message containing the indication of the first group operating mode to the first UE group.

[0132] At least some of the methods disclosed herein can be implemented on a programmable processor. However, the controller, flowchart, and module can also be implemented on general-purpose or special-purpose computers, programmable microprocessors or microcontrollers and peripheral integrated circuit elements, integrated circuits, hardware electronics or logic circuits such as discrete element circuits, programmable logic devices, etc. Generally, any device residing as a finite state machine capable of implementing the flowcharts shown in the figures can be used to implement the processor functions of this disclosure.

[0133] At least some embodiments may improve the operation of the disclosed apparatus. Furthermore, although this disclosure has been described with reference to specific embodiments, it will be apparent to those skilled in the art that many alternatives, modifications, and variations will be readily apparent. For example, various components of the embodiments may be interchanged, added, or replaced in other embodiments. Moreover, not all elements in each figure are essential for the operation of the disclosed embodiments. For example, those of ordinary skill in the art of the disclosed embodiments will be able to make and use the teachings of this disclosure by simply employing the elements of the independent claims. Therefore, the embodiments of this disclosure as set forth herein are intended to be illustrative rather than restrictive. Various changes may be made without departing from the spirit and scope of this disclosure.

[0134] In this document, relational terms such as "first," "second," etc., may be used only to distinguish one entity or action from another, and do not necessarily require or imply any actual such relationship or order between such entities or actions. The phrases "at least one of," "at least one of a group of," or "at least one of," followed by a list, are defined to mean one, some, or all, but not necessarily all, of the elements in the list. The terms "comprises," "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not necessarily include only those elements, but may include other elements not expressly listed or not inherent to such process, method, article, or apparatus. Without further constraints, an element preceded by "a / an," etc., does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes said element. Furthermore, the term "another" is defined as at least a second or more. The terms "comprising," "having," etc., as used herein, are defined as "including." Furthermore, the background section is not recognized as prior art, but is written at the time of submission as the inventor's own understanding of the background of some embodiments, and includes the inventor's own identification of any problems with the prior art and / or problems experienced in the inventor's own work.

[0135] List of abbreviations

[0136] 3GPP 3rd Generation Partnership Project

[0137] 5G fifth-generation mobile communication technology

[0138] 5G-CRG 5G Cable Home Gateway

[0139] 5G-GUTI 5G Globally Unique Temporary Identifier

[0140] 5G-S-TMSI 5G Short Temporary Mobile Subscription Identifier

[0141] 5G-TMSI 5G Temporary Mobile Subscription Identifier

[0142] ACK confirmation

[0143] A-CSI (Aperiodic CSI)

[0144] AMF access and mobility management functions

[0145] BFD Beam Fault Detection

[0146] AF Application Functions

[0147] AI (Artificial Intelligence)

[0148] BWP bandwidth portion

[0149] CA carrier aggregation

[0150] CC component carrier

[0151] CCCH SDU (Common Control Channel Service Data Unit)

[0152] CCE Control Channel Element

[0153] CDMA Code Division Multiple Access

[0154] CM Connection Management

[0155] CORESET Control Resource Set

[0156] CRC Cyclic Redundancy Check

[0157] CRI CSI-RS Resource Index

[0158] C-RNTI Community RNTI

[0159] CSI-RS Channel State Information Reference Signal

[0160] CSI Channel State Information

[0161] CSS Public Search Space

[0162] DCI Downlink Control Information

[0163] DL downlink

[0164] DMRS demodulation reference signal

[0165] DNAI Data Network Access Identifier

[0166] DRX discontinuous reception

[0167] E-UTRAN evolved universal terrestrial radio access network

[0168] eNB enhances NodeB

[0169] FDD (Frequency Division Duplex)

[0170] FN-BRG Fixed Broadband RG

[0171] FN-CRG Fixed Network Cable RG

[0172] GCI Global Cable Identifier

[0173] GERAN GSM EDGE wireless access network

[0174] GLI Global Line Identifier

[0175] gNB New Wireless NodeB

[0176] GPSI General Public Subscription Identifier

[0177] GUAMI's globally unique AMF identifier

[0178] GUTI (Globally Unique Temporary Identifier)

[0179] HARQ-ACK Hybrid Automatic Repeat Request Acknowledgment

[0180] HST High-Speed ​​Railway

[0181] ID identifier

[0182] IE Information Elements

[0183] IIoT (Industrial Internet of Things)

[0184] IMEI International Mobile Equipment Identity

[0185] IMEISV International Mobile Equipment Identity Software Version

[0186] IMSI International Mobile Subscriber Identity

[0187] IoT (Internet of Things)

[0188] I-RNTI Inactive Wireless Network Temporary Identifier

[0189] LTE Long Term Evolution

[0190] MAC Media Access Control

[0191] MAC CE Media Access Control Element

[0192] MCG Main Cell Group

[0193] MCS modulation and coding strategy

[0194] ML Machine Learning

[0195] MPE Maximum Permissible Exposure

[0196] MPO MsgA PUSCH timing

[0197] MsgA Message A

[0198] MsgB Message B

[0199] mMTC (Mass Machine Type Communication)

[0200] MTC Machine Type Communication

[0201] NACK (Negative Acknowledgment)

[0202] NAI Network Access Identifier

[0203] NEF Network Exposure Function

[0204] NG-RAN (Next Generation Radio Access Network)

[0205] NR New Wireless

[0206] NUL Non-Secondary Uplink

[0207] OAM Operation, Management and Maintenance

[0208] OFDMA (Orthogonal Frequency Division Multiple Access)

[0209] PCell main cell

[0210] PDCCH (Physical Downlink Control Channel)

[0211] PDSCH (Physical Downlink Shared Channel)

[0212] PDU Protocol Data Unit

[0213] PEI Permanent Device Identifier

[0214] PF paging frame

[0215] PHR Power Headroom Report

[0216] P-MPR power management maximum power reduction

[0217] PO paging timing

[0218] PRACH Physical Random Access Channel

[0219] PSCell Primary and Secondary Communities

[0220] PS-RNTI Power Saving RNTI

[0221] PUCCH (Physical Uplink Control Channel)

[0222] PUSCH Physical Uplink Shared Channel

[0223] QCL Quasi-common Positioning

[0224] RAN (Radio Access Network)

[0225] RAR Random Access Response

[0226] RG Home Gateway

[0227] RLF wireless link failure

[0228] RLM Wireless Link Monitoring

[0229] RM Registration Management

[0230] RNA-based notification region

[0231] RNTI (Non-Real-Time Identifier for Wireless Networks)

[0232] RRC (Radio Resource Control)

[0233] RRM Wireless Resource Management

[0234] RS reference signal

[0235] RSRP reference signal received power

[0236] SAR specific absorption rate

[0237] SCell Auxiliary Community

[0238] SCG auxiliary community group

[0239] SCS Subcarrier Spacing

[0240] SFI Slot Format Indicator

[0241] SFN Single Frequency Network

[0242] S-NSSAI Single Network Slice Selection Auxiliary Information

[0243] SpCell Special Cell (i.e., PCell of MCG or SCG)

[0244] SP-CSI Semi-static CSI

[0245] SR scheduling request

[0246] SRI SRS resource indicator

[0247] SRS Detection Reference Signal

[0248] SPS Semi-Static Scheduling

[0249] SS Search Space

[0250] SS / PBCH Synchronization Signal / Physical Broadcast Channel

[0251] SSBRI SS / PBCH Block Resource Index

[0252] SUL Assisted Uplink

[0253] SUPI subscription permanent identifier

[0254] TB transfer block

[0255] TCI Transport Configuration Indicator

[0256] TC-RNTI Temporary Cell RNTI

[0257] TDD (Time Division Duplex)

[0258] TDMA (Time Division Multiple Access)

[0259] TMSI Temporary Mobile Subscriber Identity

[0260] UCI uplink control information

[0261] UDM Unified Data Management

[0262] UDR Unified Data Repository

[0263] UE User Equipment

[0264] UL uplink

[0265] UPF User Plane Functions

[0266] URLLC Ultra-Reliable Low-Latency Communication

[0267] TRP Transmit and Receive Points

[0268] USS UE-specific search space

[0269] W-5GAN Wired 5G Access Network

[0270] XR Extended Reality.< / guami> < / mnc> < / mcc> < / guami> < / guami>

Claims

1. A method in a user equipment, the method comprising: determining an operating mode from a plurality of operating modes based on at least one traffic type originating from the user equipment; and informing a network entity of the determined operating mode, wherein the plurality of operating modes comprises at least one group operating mode and an individual operating mode, wherein the at least one group operating mode supports a plurality of user equipments grouped into a user equipment group, wherein the at least one group operating mode supports at least one network entity communicating a message associated with the user equipment group including the user equipment, and wherein the associated message is associated with the user equipment group, wherein each of the plurality of operating modes corresponds to a particular access priority, and wherein informing the network entity of the determined operating mode includes sending a radio resource control message including the determined operating mode along with a corresponding access priority in a radio resource control parameter of the radio resource control message.

2. The method of claim 1, further comprising receiving information of a plurality of identifiers, wherein a first identifier of the plurality of identifiers is associated with a particular group operating mode of a plurality of different group operating modes, and wherein a second identifier of the plurality of identifiers is associated with an individual operating mode, and wherein informing the network entity of the determined operating mode includes transmitting an indication of an identifier associated with the determined operating mode to the network entity.

3. The method of claim 2, wherein the particular group operating mode is associated with the user equipment group.

4. The method of claim 2, wherein receiving the information of the plurality of identifiers includes receiving an extended 5G globally unique temporary identifier, wherein the extended 5G globally unique temporary identifier includes a plurality of 5G temporary mobile subscription identifiers.

5. The method of claim 2, wherein receiving the information of the plurality of identifiers includes receiving a plurality of inactive radio network temporary identifiers.

6. The method of claim 2, wherein receiving the information of the plurality of identifiers includes receiving a plurality of cell radio network temporary identifiers.

7. The method of claim 2, wherein transmitting the indication includes transmitting the indication of the identifier associated with the determined operating mode in the radio resource control message, wherein the radio resource control message includes at least one selected from a radio resource control setup request message, a radio resource control resume request message, and a radio resource control reestablishment request message.

8. The method of claim 1, further comprising selecting a scheduling request resource of a scheduling request configuration associated with the determined operating mode, wherein informing the network entity of the determined operating mode includes transmitting a scheduling request on the selected scheduling request resource.

9. The method of claim 1, further comprising selecting a random access resource of a random access configuration associated with the determined operating mode, wherein informing the network entity of the determined operating mode includes performing a random access procedure based on the selected random access resource.

10. The method of claim 1, wherein the radio resource control parameter comprises at least one selected from a ‘EstablishmentCause’ parameter in a radio resource control setup request message and a ‘ResumeCause’ parameter in a radio resource control resume request message.

11. The method of claim 1, further comprising receiving a paging message intended for the user equipment, wherein the paging message comprises information of a particular operating mode from the plurality of operating modes.

12. The method of claim 1, further comprising receiving a physical downlink control channel that commands a random access procedure to the user equipment, wherein the physical downlink control channel comprises information of a particular operating mode from the plurality of operating modes.

13. The method of claim 1, further comprising receiving a physical downlink control channel that indicates a wake-up for physical downlink control channel monitoring, wherein the physical downlink control channel that indicates the wake-up indicates a particular operating mode from the plurality of operating modes.

14. The method of claim 1, wherein the at least one group operating mode supports both group communications of a plurality of user equipments including the user equipment and individual communications of individual user equipments in the plurality of user equipments, and wherein the individual operating mode supports only individual communications.

15. An apparatus comprising: a controller that determines an operating mode from a plurality of operating modes based on at least one traffic type originating from the apparatus; and a transceiver coupled to the controller, wherein the transceiver informs a network entity of the determined operating mode, wherein the plurality of operating modes comprises at least one group operating mode and an individual operating mode, wherein the at least one group operating mode supports a plurality of user equipments grouped into a user equipment group, wherein the at least one group operating mode supports at least one network entity that communicates a message associated with the user equipment group including the apparatus, and wherein the associated message is associated with the user equipment group, wherein each of the plurality of operating modes corresponds to a particular access priority, and wherein informing the network entity of the determined operating mode comprises sending a radio resource control message including the determined operating mode along with a corresponding access priority in a radio resource control parameter of the radio resource control message.

16. The apparatus of claim 15, wherein the transceiver receives information of a plurality of identifiers, wherein a first identifier in the plurality of identifiers is associated with a particular group operating mode in a plurality of different group operating modes, and wherein a second identifier in the plurality of identifiers is associated with an individual operating mode, and wherein informing the network entity of the determined operating mode comprises transmitting an indication of an identifier associated with the determined operating mode to the network entity.

17. The apparatus of claim 15, wherein the controller selects a scheduling request resource of a scheduling request configuration associated with the determined operating mode, and wherein notifying the network entity of the determined mode of operation comprises transmitting a scheduling request on a selected scheduling request resource.

18. The apparatus of claim 15, wherein the controller selects a random access resource of a random access configuration associated with the determined mode of operation, and wherein notifying the network entity of the determined mode of operation comprises performing a random access procedure based on a selected random access resource.

19. The apparatus of claim 15, wherein the transceiver receives a paging message intended for the apparatus, wherein the paging message includes information of a particular mode of operation from the plurality of modes of operation.

20. The apparatus of claim 15, wherein the radio resource control parameter comprises at least one selected from a 'EstablishmentCause' parameter in a radio resource control setup request message and a 'ResumeCause' parameter in a radio resource control resume request message.

Images