Adjusting use of paging during emergency session in telecommunications network

Abstract

In some examples, a network apparatus in a telecommunications network is provided. The telecommunications network comprises at least one core network and at least one network node. In one embodiment, a network device may be configured to receive data including an indication for use of at least one network operation of the network device to disable, enable, or reactivate a user equipment (UE), the UE being in a radio resource control (RRC) idle or inactive operating state, and the UE being in a radio resource control (RRC) idle or inactive operating state, and the UE being in a radio resource control (RRC) idle or inactive operating state, and the UE being in a radio resource control (RRC) idle or inactive operating state, and the UE being in a radio resource control (RRC) idle or inactive operating state, and the UE being in a radio resource control (RRC) idle or inactive operating state, and the UE being in a radio resource control (RRC) idle or inactive operating state, and the UE being in a radio resource control (RRC) idle or inactive operating state. The present invention relates to a method for receiving at least one network operation, in which a user equipment (UE) is participating in an activated packet data unit (PDU) session for an emergency call or an evolved universal terrestrial radio access network (E-UTRAN) radio access bearer (E-RAB) session, and the at least one network operation is disabled, enabled or reactivated using the received data.

Description

Technical Field

[0001] The present disclosure relates generally to paging in telecommunications networks. Various aspects relate to regulating paging during an emergency session between user equipment and a network. Background Art

[0002] The Third Generation Partnership Project (3GPP) and fifth generation (5G) New Radio (NR) mobile telecommunication networks offer high data rates, low latency, and improved system performance. In 3GPP NR, the 5G terrestrial NR access network includes multiple network devices, such as network nodes or base stations (e.g., Next Generation NodeBs (gNBs)), that communicate with mobile stations called user equipment (UE).

[0003] To establish a communication channel between the UE and the gNB, a process called paging is used, in which the telecommunications network determines the UE's location before actually establishing a connection. Paging is used to alert the UE of an incoming session (e.g., a call). In most cases, the paging process is implemented while the UE is in Radio Resource Control (RRC) Idle mode. During RRC Idle mode, the UE can be in a dormant (i.e., low-power) mode defined by a discontinuous reception (DRX) or extended DRX (eDRX) cycle, in which the UE periodically wakes up and monitors the network's Physical Downlink Control Channel (PDCCH), used for downlink scheduling, to check for paging messages. If the PDCCH indicates that a paging message was sent in a subframe, the UE demodulates the paging channel to see if the paging message is directed to the UE. This means that the UE needs to monitor whether the network is sending a paging message to the UE.

[0004] For example, in a 5G network, a packet data unit (PDU) session is used to provide an end-to-end user plane connection between the UE and a specific data network (DN) through a user plane function (UPF). Conceptually similar to the packet data network (PDN) connection in a 4G evolved packet core (EPC) network. A PDU session provides a connection between an application on the UE and a DN (e.g., the "Internet" or a private enterprise network). An emergency PDU session provides a connection between the UE and emergency services. For example, an emergency PDU session can enable the UE to communicate with an emergency service or call center. In an active state, the emergency PDU session between the UE and the emergency service or call center is maintained, and during the emergency PDU session, the UE can initiate and / or receive multiple calls to and / or from the emergency service or call center. That is, in addition to the initial call (which may include the call or communication that triggered the emergency PDU session), the emergency PDU session can also include subsequent communications between the UE and the emergency service or call center. For example, emergency services may contact the UE after the initial call to obtain more information about the emergency from the UE's user, for example. Any subsequent communications (e.g., subsequent calls) belong to the same active emergency PDU session. After the UE enters the RRC idle or inactive operating state, the network may initiate such communications by paging the UE. For example, once the initial emergency call is terminated, the UE may enter the RRC idle or inactive operating state. To establish subsequent communications, the network may page the UE to establish subsequent communications. Summary of the Invention

[0005] An object of the present disclosure is to provide an apparatus and method to regulate the use of network operations (eg, paging operations) in a telecommunications network, particularly during emergency packet data unit sessions.

[0006] These and other objects are achieved by the features claimed in the independent claims.

[0007] Further implementations are apparent from the dependent claims, the description and the drawings.

[0008] A first aspect of the present disclosure provides a network device in a telecommunications network. The telecommunications network includes at least one core network and at least one network node. The network device is configured to: receive data including an indication, wherein the indication is used to disable, enable, or re-enable use of at least one network operation of the network device for a user equipment (UE), the user equipment (UE) being in a radio resource control (RRC) idle or inactive operating state, and the user equipment (UE) being involved in an active packet data unit (PDU) session or an evolved universal terrestrial radio access network (E-UTRAN) radio access bearer (E-RAB) session for an emergency call, and use the received data to disable, enable, or re-enable the at least one network operation.

[0009] With an emergency PDU session established, subsequent calls can be initiated after the initial emergency call. Disabling, enabling, or re-enabling the use of at least one network operation (e.g., paging) may inform a network device (e.g., a gNB or eNB) that, when it receives paging from a CN component during an active emergency PDU session, the network device should not use, for example, a Paging Early Indication (PEI) and a subgroup-based User Equipment Identifier (UE ID). This resolves the issue of a network device, such as a gNB / eNB, being unaware that an emergency PDU session is active and, therefore, being able to avoid using the PEI and subgroup-based UE ID when receiving paging from the CN during such an active emergency PDU session.

[0010] In an implementation of the first aspect, the network operation may include at least one of the following: paging early indication (PEI), extended discontinuous reception (eDRX), wake-up signal (WUS), or group wake-up signal (GWUS), wherein the paging early indication (PEI) includes a subgroup-based user equipment (UE) identifier (UE identifier, UE ID). The network device may receive the data from the at least one core network or the at least one network node of the telecommunications network. The network device may receive the data as part of a paging message from the at least one core network of the telecommunications network.

[0011] In one example, the network device can receive the data as part of a paging message for an emergency call back from at least one core network of the telecommunications network, wherein the emergency call back is received by the UE as part of the activated Packet Data Unit (PDU) session or Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Radio Access Bearer (E-RAB) session for the emergency call.

[0012] The network apparatus may send a paging message to the user equipment (UE) as part of the Packet Data Unit (PDU) session or Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Radio Access Bearer (E-RAB) session for the emergency call, wherein the paging message is sent without a paging early indication (PEI) and / or a user equipment (UE) identifier (UE ID) associated with a subgroup of the user equipment (UE). The data may include part of a downlink (DL) non-access stratum (NAS) message from the at least one core network of the telecommunications network.

[0013] The network device may, when establishing the emergency call for the user equipment (UE), receive the data including an indication as part of a packet data unit (PDU) session or an evolved universal terrestrial radio access network (E-UTRAN) radio access bearer (E-RAB) session accept message sent by at least one core network of the telecommunications network, wherein the indication is used to disable the use of paging early indication (PEI), extended discontinuous reception (eDRX), wake-up signal (WUS) or group wake-up signal (GWUS) for the user equipment (UE). The network device may, when releasing the emergency call for the user equipment (UE), receive the data including an indication as part of a packet data unit (PDU) session or an evolved universal terrestrial radio access network (E-UTRAN) radio access bearer (E-RAB) session release message sent by at least one core network of the telecommunications network, wherein the indication is used to re-enable the use of paging early indication (PEI), extended discontinuous reception (eDRX), wake-up signal (WUS) or group wake-up signal (GWUS) for the user equipment (UE).

[0014] In one example, the network device may include a functionally separated network device, wherein the functionally separated network device includes a centralized unit (CU) and a distributed unit (DU), and the network device is used to: receive the data from the at least one core network of the telecommunications network using an F1 interface configured between the CU and the DU.

[0015] Therefore, a network device (e.g., a gNB) can be functionally divided into two or more parts. For example, a radio hardware unit (RU) can be used to convert wireless signals sent to and from the network device's antenna into digital signals for transmission over a packet network. Thus, the RU can handle the digital front end (DFE) and lower physical (PHY) layers, as well as digital beamforming functionality.

[0016] A distributed unit (DU) may include components for a network device, which may be deployed, for example, on-site near the RU and execute portions of the radio link control (RLC) layer, the medium access control (MAC) layer, and the PHY layer. A centralized unit (CU) may include a radio resource control (RRC) protocol layer, a service data adaptation protocol (SDAP) protocol layer, and a packet data convergence protocol (PDCP) protocol layer, and may be responsible for non-real-time RRC and PDCP protocol stack functions. In one example, the CU may be deployed in a cloud environment to support the integrated deployment of core network user plane function (UPF) sinking and edge computing. The CU and DU may be connected via the F1 interface. The F1 interface is a functional division of 3GPP between the CU (centralized unit: PDCP, RRC, SDAP) and the DU (distributed unit: RLC, MAC, PHY). It is standardized in TS 38.470 to 38.473 of 5G NR.

[0017] A CU can manage one or more DUs. Typically, a DU is responsible for the real-time Layer 1 (L1, physical layer) and lower Layer 2 (L2), which includes the data link layer and scheduling functions. The CU is responsible for the non-real-time higher-level L2 and L3 (network layer) functions.

[0018] A second aspect of the present disclosure provides a core network device of a telecommunications network. The telecommunications network includes at least one core network and at least one network node. The core network device is configured to send data including an indication to a network device of the telecommunications network, wherein the indication is configured to disable, enable, or re-enable use of at least one network operation for user equipment (UE), the UE being in a radio resource control (RRC) idle or inactive operating state and the UE being involved in an active session for an emergency call.

[0019] For example, the core network device may include an access mobility function (AMF) or a mobility management entity (MME) of the network. The activated session for the emergency call may include an activated packet data unit (PDU) session or an evolved universal terrestrial radio access network (E-UTRAN) radio access bearer (E-RAB) session for the emergency call; the network operation includes at least one of the following: paging early indication (PEI), extended discontinuous reception (eDRX), wake up signal (WUS), or group wake up signal (GWUS), wherein the paging early indication (PEI) includes a user equipment (UE) identifier (UE identifier, UE ID) based on a subgroup.

[0020] In an implementation of the second aspect, the core network device may send the data as part of a paging message for an emergency call back, wherein the emergency call back is received by the user equipment (UE) as part of the packet data unit (PDU) session or evolved universal terrestrial radio access network (E-UTRAN) radio access bearer (E-RAB) session for the emergency call. The core network device may send the data including the indication as part of a downlink (DL) non-access stratum (NAS) message, wherein the indication is used to disable, enable or re-enable the at least one network operation.

[0021] A third aspect of the present disclosure provides a user equipment (UE). The user equipment (UE) is participating in an activated Packet Data Unit (PDU) session or an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Radio Access Bearer (E-RAB) session for an emergency call, and the user equipment (UE) is configured to: receive data from a network device in a telecommunications network, wherein the telecommunications network includes at least one core network and at least one network node, the data representing an indication of establishment or release of the emergency call; and send data to the at least one core network and the at least one network node of the telecommunications network to disable or enable use of paging early indication and paging subgroups for the user equipment (UE), wherein the data is provided as part of a user equipment (UE) capability information message.

[0022] These and other aspects of the present disclosure will be apparent from one or more embodiments described below. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order that the present disclosure may be more readily understood, embodiments are now described by way of example with reference to the accompanying drawings, in which:

[0024] Figure 1is a communication flow between a UE, at least one core network function of a telecommunications network, and at least one network node of the telecommunications network according to an example;

[0025] Figure 2 According to an example communication flow, when a UE is in an RRC inactive mode of operation, a CN function (e.g., AMF) uses an indication in a DL NAS transmission message when sending a DL NAS message to a network device (e.g., a gNB);

[0026] Figure 3 is a communication flow according to an example, wherein a CN function (e.g., AMF or MME) uses an indication in a DL NAS transport message when establishing or releasing an emergency PDU session for a UE in an RRC idle (IDLE) operating state;

[0027] Figure 4 is a communication flow according to an example, wherein a CN function (e.g., AMF) uses an indication in a DL NAS transport message when establishing or releasing an emergency PDU session for a UE in an RRC inactive running state;

[0028] Figure 5 is a communication flow according to an example, wherein a UE-initiated dynamic capability update is used during an emergency PDU session before the UE switches to an RRC idle running state;

[0029] Figure 6 is a communication flow according to an example, wherein a UE-initiated dynamic capability update is used during an emergency PDU session before the UE switches to an RRC inactive running state;

[0030] Figure 7 is a schematic diagram of a machine according to an example. DETAILED DESCRIPTION

[0031] The exemplary embodiments are described below in sufficient detail to enable one of ordinary skill in the art to implement and realize the systems and processes described herein.It is important to understand that the embodiments can be provided in many alternative forms and should not be construed as limited to only the examples set forth herein.

[0032] Therefore, while the embodiments may be modified in various ways and take various alternative forms, specific embodiments thereof are shown in the drawings and described in detail below as examples. It is not intended to be limited to the particular forms disclosed. On the contrary, all modifications, equivalents, and alternatives falling within the scope of the appended claims are intended to be included therein. Throughout the drawings and, where appropriate, the detailed description, elements of the exemplary embodiments are consistently represented by the same reference numerals.

[0033] The terms used to describe the embodiments herein are not intended to limit the scope. The articles "a" and "the" are singular forms because they have only one referent, but the use of the singular form in this article should not exclude the presence of multiple referents. In other words, unless the context clearly indicates otherwise, the elements mentioned in the singular can be one or more in number. It should also be understood that the term "comprising" used herein indicates the presence of stated features, projects, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, projects, steps, operations, elements, components and / or combinations thereof. The term "and / or" is merely an association relationship describing associated objects, indicating that three relationships can exist, so that A and / or B can represent that A exists alone, A and B exist simultaneously, or B exists alone. The symbol " / " usually represents that the associated objects are in an "or" relationship.

[0034] Unless otherwise defined, all terms (including technical and scientific terms) used in this article should be interpreted as customary usage in the field. It should also be understood that unless explicitly defined herein, terms in common usage should also be interpreted as customary usage in the relevant field and should not be interpreted as idealized or overly formal meanings.

[0035] The following includes specific information related to the implementation of the present disclosure. The accompanying drawings and the detailed disclosure thereof are directed only to the implementation. However, the present disclosure is not limited to these implementations. Other variations and implementations of the present disclosure will be apparent to those skilled in the art.

[0036] The phrases "in one implementation" and "in some implementations" may each refer to one or more of the same or different implementations. The term "coupled" is defined as connected directly or indirectly through intermediate components and is not necessarily limited to physical connections. The phrase "at least one of A, B, and C" or "at least one of: A, B, and C" means "only A, or only B, or only C, or any combination of A, B, and C."

[0037] The terms "system" and "network" are used interchangeably.

[0038] For the purpose of explanation and non-limiting, specific details such as functional entities, technologies, protocols and standards are set forth to provide an understanding of the present disclosure. In other examples, detailed disclosure of well-known methods, technologies, systems and architectures is omitted to avoid obscuring the present disclosure with unnecessary details.

[0039] Those skilled in the art will recognize that any disclosed network function or algorithm can be implemented by hardware, software, or a combination of software and hardware. The disclosed functions can correspond to modules, which can be software, hardware, firmware, or any combination thereof.

[0040] Software implementations may include machine- and / or computer-readable and / or executable instructions stored in a machine- and / or computer-readable medium such as a memory or other type of storage device. One or more microprocessors or general-purpose computers with communication processing capabilities may be programmed with the corresponding executable instructions and execute the disclosed network functions or algorithms.

[0041] The microprocessor or general-purpose computer may include an Applications Specific Integrated Circuitry (ASIC), a programmable logic array, and / or use one or more digital signal processors (DSPs). Although some of the disclosed implementations are directed to software installed and executed on computer hardware, alternative implementations implemented as firmware or hardware, or as a combination of hardware and software, are fully within the scope of this disclosure. Computer-readable media include, but are not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, compact disc read-only memory (CD-ROM), magnetic cassettes, magnetic tape, disk storage, or any other equivalent medium capable of storing computer-readable instructions.

[0042] A wireless communication network architecture, such as a Long-Term Evolution (LTE) system, LTE-Advanced (LTE-A) system, LTE-Advanced Pro (LTE-Advanced Pro) system, or a 5G NR radio access network (RAN), typically includes at least one base station (BS), at least one user equipment (UE), and one or more optional network elements (NEs) that provide connectivity within the network. The UE communicates with a network, such as the Core Network (CN), Evolved Packet Core (EPC), Evolved Universal Terrestrial RAN (E-UTRAN), 5G Core (5GC), or the Internet, through the RAN established by one or more BSs.

[0043] A UE may include, but is not limited to, a mobile station, a mobile terminal or device, or a user communication wireless terminal. A UE may be a portable wireless device, including, but not limited to, a mobile phone, a tablet, a wearable device, a sensor, a vehicle, or a personal digital assistant (PDA) with wireless communication capabilities. A UE is configured to receive and transmit signals over an air interface using one or more signaling radio bearers with one or more cells in a RAN using one or more component carriers from among multiple component carriers.

[0044] The BS may provide communication services based on at least one of the following radio access technologies (RATs): Worldwide Interoperability for Microwave Access (WiMAX), Global System for Mobile Communications (GSM) (commonly referred to as 2G), GSM Enhanced Data Rates for GSM Evolution (EDGE) RAN (GSM EDGERAN, GERAN), General Packet Radio Service (GPRS), Universal Mobile Telecommunications System (UMTS) (commonly referred to as 3G based on basic wideband-code division multiple access (W-CDMA)), High-Speed ​​Packet Access (HSPA), LTE, LTE-A, evolved LTE (eLTE) (i.e., LTE connected to 5GC), NR (commonly referred to as 5G), and / or LTE-A Pro. However, the scope of the present disclosure is not limited to these protocols.

[0045] The BS may include, but is not limited to, a base station (NodeB, NB) in UMTS, an evolved NodeB (eNB) in LTE or LTE-A, a radio network controller (RNC) in UMTS, a BS controller (BSC) in GSM / GERAN, a next generation (ng)-eNB in ​​an Evolved Universal Terrestrial Radio Access (E-UTRA) BS connected to a 5GC, a next generation NodeB (gNB) in a 5G-RAN, or any other device capable of controlling wireless communications and managing radio resources within a cell. The BS may provide services to one or more UEs through a radio interface.

[0046] A base station (BS) can provide wireless coverage to a specific geographic area by forming multiple cells that form a RAN. The BS supports the operation of cells. Each cell is used to serve at least one UE within its wireless coverage area.

[0047] Each cell (usually referred to as a serving cell) can provide services to serve one or more UEs within its wireless coverage, so that each cell schedules downlink (DL) and optional uplink (UL) resources to at least one UE within its wireless coverage for DL ​​packet and optional UL packet transmission. The BS can communicate with one or more UEs in the wireless communication system through multiple cells. The cell can allocate sidelink (SL) resources to support proximity service (ProSe) or vehicle to everything (V2X) services. Each cell can have overlapping coverage areas with other cells.

[0048] As described above, an emergency PDU session may cause the UE to be paged after the initial communication is terminated in order to enable subsequent communications, still as part of the activated emergency PDU session. As described above, for example, an activated emergency PDU session may include subsequent communications between the UE and emergency services or a call center. However, because the PDU session and the emergency PDU session are established and terminated by the CN component of the network, any network device such as a node or base station (e.g., a gNB or eNB) that is involved in serving the UE of the emergency PDU session is unaware that the session is active. Thus, for example, a node is unaware that it should avoid paging a UE that uses one of the following: Paging Early Indication (PEI), extended discontinuous reception (eDRX), a Wake Up Signal (WUS), or a Group Wake up Signal (GWUS), where the PEI includes a subgroup-based user equipment (UE) identifier (UE ID).

[0049] According to one example, systems, methods, and apparatus are provided for disabling, enabling, or re-enabling at least one network operation, wherein the network operation may include at least one of: a paging early indication (PEI), extended discontinuous reception (eDRX), a wake-up signal (WUS), or a group wake-up signal (GWUS), wherein the paging early indication (PEI) includes a subgroup-based user equipment (UE) identifier (UE ID). In one example, use of the network operation, such as a network operation for implementing paging of a UE, may be enabled, disabled, or re-enabled by a network controller (CN) (e.g., a CN function in a mobile telecommunications network). However, when an emergency PDU session is activated in a synchronous manner, a similar indication (e.g., an "eDRX usage indicator" in a paging message or a downlink (DL) non-access stratum (NAS) transmission message) may also be applied to eDRX to avoid interoperability issues and reduce latency. Thus, a network device such as a node or base station (e.g., a gNB or eNB) may be made aware that a paging function such as PEI should be disabled (e.g., due to an activated emergency PDU session) or enabled or re-enabled (e.g., due to termination of an emergency PDU session).

[0050] Figure 1 The present invention is a communication process between a UE, at least one core network function of a telecommunication network and at least one network node of the telecommunication network according to an example. Figure 1 In the example of FIG, 1 , UE 101 initiates (1) an emergency call, and a CN function 105 of the network for the emergency call establishes an emergency PDU (or Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Radio Access Bearer (E-RAB), etc.) session for the emergency call. For example, the CN function 105 may include an access mobility function (AMF) or a mobility management entity (MME) of the network.

[0051] When the initial emergency call is completed, the emergency PDU session remains in the active state (2). That is, the CN function 105 does not terminate the emergency PDU session. After the emergency call is completed, the network device 103 (e.g., gNB) causes the UE 101 to enter the RRC idle (IDLE) operating state (3). The UE 101 stops using network operations. That is, in one example, the UE 101 stops using paging early indication (PEI), and the non-access stratum indicates this to the access stratum of the network.

[0052] The CN function 105 of the network performs (5) paging for the subsequent emergency call back as part of the activated emergency PDU session. As part of the paging message, data including an indication for disabling, enabling or re-enabling the use of at least one network operation of the network device 103 for the UE 101 may be provided. Figure 1In the example of , the paging message may include data including an indication for disabling the use of PEI, so that the network device 103 may disable the use of PEI and generate a paging message for the UE 101 without an indication to use PEI. That is, the network device 103 may send (7) a paging message to the UE 101 as part of a PDU (or Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Radio Access Bearer (E-RAB) session for the emergency call, wherein the paging message is sent without a paging early indication (PEI) and / or a user equipment (UE) identifier (UE ID) associated with a subgroup of user equipment (UE). The UE may be associated with a UE. 101 establishes one or more emergency call backs (8), and after completion / termination of the establishment, the emergency PDU session (9) may be released. UE 101 may therefore resume using the PEI based on the indication (10) of the NAS relating to the release of the emergency PDU session. That is, UE 101 and network function 105 are aware of the release. However, at this point, network device 103 is not aware of the release. Therefore, network function 105 may send (11) a paging message to network device 103, the paging message including data indicating an indication that the use of the PEI should be enabled (or re-enabled or as the case may be). Therefore, network device 103 re-enables (12) the use of the PEI and sends (13) a paging message from network device 103 to UE 101 using data indicating the PEI and UE ID subgroup information.

[0053] Figure 2 According to an example communication flow, when a UE is in RRC Inactive mode, a CN function (e.g., AMF) uses an indication in a DL NAS transmission message when sending a DL NAS message to a network device (e.g., gNB). This operation mode can reduce the amount of time it takes for the UE to transition from the RRC Idle state to the RRC Connected state.

[0054] exist Figure 2In the example of FIG, 1 , UE 101 initiates (1) an emergency call, and a CN function 105 of the network for the emergency call establishes an emergency PDU (or Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Radio Access Bearer (E-RAB), etc.) session for the emergency call. For example, the CN function 105 may include an access and mobility function (AMF) or a mobility management entity (MME) of the network.

[0055] When the initial emergency call is completed, the emergency PDU session remains in active state (2). That is, the CN function 105 does not terminate the emergency PDU session.

[0056] After the emergency call is completed, UE 101 is switched to the RRC Inactive state by the network (e.g., a network device such as a gNB) (3). UE 101 stops using network operations. That is, in one example, UE 101 stops using paging early indication (PEI), and the non-access stratum indicates this to the network's access stratum (4).

[0057] Figure 2 The example involves multiple network devices, namely, a last serving gNB 203 and a set of receiving gNBs 201. The last serving gNB 203 comprises the network device that communicates with UE 101 while the UE is in the RRC Connected state (e.g., as part of an initial emergency call) and before switching to the RRC Inactive state. The receiving gNB 201 is the network device that UE 101 communicates with when UE 101 responds to a paging call. For example, after terminating the initial emergency call, UE 101 may have moved out of coverage of the last serving gNB 203.

[0058] The CN function 105 sends (5a) a DL NAS transport message to the last serving gNB 203. The DL NAS transport message includes information indicating an indication to disable the use of the PEI. The last serving gNB 203 performs (5b) paging for a subsequent emergency call back as part of the activated emergency PDU session. As part of the paging message, data may be provided including an indication to disable, enable, or re-enable the use of at least one network operation of the receiving gNB 201 for the UE 101. Figure 2In the example of , the paging message (5b) may include data including an indication to disable the use of PEI, so that the receiving gNB 201 (and the last serving gNB 203) may disable the use of PEI (6). Figure 2 In the example of FIG. 1 , a paging message for UE 101 may be generated without using a PEI and sent to UE 101 by the last serving gNB (7a) and the receiving gNB 201 (7b) as needed. That is, the receiving gNB 201 or the last serving gNB 203 may send a paging message to UE 101 during an active PDU session for an emergency call, wherein the paging message is sent without a paging early indication (PEI) and / or a user equipment (UE) identifier (UE ID) associated with a subgroup of user equipment (UE).

[0059] The RRC connection may be restored (8). That is, the UE 101 may switch from the RRC inactive operating state to the RRC connected operating state, and an emergency call back (8) may be established with the UE 101, and after completion / termination of the establishment, the emergency PDU session (9) may be released. Therefore, the UE 101 may resume using the PEI based on the NAS indication (10) associated with the release of the emergency PDU session. That is, the UE 101 and the CN function 105 are aware of the release. However, at this time, the last serving gNB 203 and the receiving gNB 201 are not aware of the release. Therefore, the CN function 105 may send (11a) information as part of a DL NAS transport message to the last network device 203, the information including data indicating that the use of the PEI should be enabled (or re-enabled, as the case may be). The last serving gNB 203 may send a paging message (11b) to the receiving gNB 201, the paging message including data indicating that the use of the PEI should be enabled (or re-enabled, as the case may be). Therefore, the receiving gNB 201 (and the last serving gNB 203) re-enables (12) the use of PEI and sends a paging message to the UE 101 from the last serving gNB 203 (13a) and the receiving gNB 201 (13b) using the PEI and UE ID subgroup information.

[0060] Figure 3 The invention provides a communication process according to an example, wherein a CN function (e.g., AMF or MME) uses an indication in a DL NAS transport message when establishing or releasing an emergency PDU session for a UE in an RRC idle state.

[0061] exist Figure 3 In the example of FIG, 1 , UE 101 initiates (1) an emergency call, and a CN function 105 of the network for the emergency call establishes an emergency PDU (or Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Radio Access Bearer (E-RAB), etc.) session for the emergency call. For example, the CN function 105 may include an access and mobility function (AMF) or a mobility management entity (MME) of the network.

[0062] CN function 105 sends (1a) a DL NAS transfer message (e.g., including a PDU Session Setup Accept message) to network device (gNB) 201. This DL NAS transfer message includes information indicating that the use of the PEI is disabled. gNB 201 transmits (1b) the received DL NAS message to UE 101 within a DL Information Transfer message. UE 101 stops using the network operation. That is, in one example, UE 101 stops using the PEI, and the non-access stratum indicates this to the access stratum of the network (2).

[0063] When the initial emergency call is completed, the emergency PDU session remains active (3). That is, the CN function 105 does not terminate the emergency PDU session. After the emergency call is completed, the gNB 201 allows the UE 101 to enter the RRC idle state (4).

[0064] The CN function 105 of the network performs (5) paging for the subsequent emergency call back as part of the activated emergency PDU session. As part of the paging message, data including an indication for disabling, enabling or re-enabling the use of at least one network operation of the network device 103 for the UE 101 may be provided. Figure 3In the example of , the paging message may include data including an indication to disable the use of PEI, so that the gNB 201 may disable the use of PEI and generate a paging message for the UE 101 without using PEI. That is, the gNB 201 may send (7) the paging message to the UE 101 as part of a PDU (or Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Radio Access Bearer (E-RAB) session) for the emergency call, wherein the paging message is sent without a paging early indication (PEI) and / or a user equipment (UE) identifier (UE ID) associated with a subgroup of user equipment (UE).

[0065] One or more emergency call backs (8) may be established with UE 101, and after completion / termination of the establishment, the emergency PDU session may be released (9). As part of the release procedure, CN function 105 may send (9a) a DL NAS transfer message (e.g., including a PDU Session Release Command) to gNB 201. The DL NAS transfer message may include information indicating an indication to enable / re-enable the use of the PEI. gNB 201 transmits (9b) the received DL NAS message to UE 101. Consequently, UE 101, based on the content of the DL NAS message including the PDU Session Release Command, starts / resumes using the PEI based on the indication from the NAS to the AS layer (10).

[0066] For example, the CN function 105 may send a paging message (11) related to a call that is not part of an emergency PDU session to the gNB 201. Accordingly, the gNB 201 may enable / re-enable the use of PEI (12) for this paging message and any subsequent paging messages. The gNB 201 may send (13) a paging message to the UE 101, the paging message including a paging early indication (PEI) and / or a user equipment (UE) identifier (UE ID) associated with a subgroup of user equipment (UE).

[0067] Figure 4A communication process according to an example, wherein a CN function (e.g., AMF) uses an indication in a DL NAS transport message when establishing or releasing an emergency PDU session for a UE in an RRC inactive running state.

[0068] exist Figure 4 In the example of FIG, 1 , UE 101 initiates (1) an emergency call, and a CN function 105 of the network for the emergency call establishes an emergency PDU (or Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Radio Access Bearer (E-RAB), etc.) session for the emergency call. For example, the CN function 105 may include an access and mobility function (AMF) or a mobility management entity (MME) of the network.

[0069] The CN function 105 sends (1a) a DL NAS transfer message (including a PDU Session Setup Accept message) to the last serving gNB 203. The DL NAS transfer message includes information indicating that the use of the PEI is disabled. The last serving gNB 203 stores this information indicating that the use of the PEI is disabled in the UE context, which represents the configuration of the UE and is maintained on the last serving gNB. The last serving gNB 203 transmits (1b) the received DL NAS message to the UE 101. The UE 101 stops using network operations. That is, in one example, the UE 101 stops using the PEI, and the UE's non-access stratum indicates this to the UE's access stratum (2).

[0070] When the initial emergency call is completed, the emergency PDU session remains in the active state (3). That is, the CN function 105 does not terminate the emergency PDU session. After the emergency call is completed, the UE 101 switches to the RRC inactive state (4). Figure 4 In the example shown in FIG5 , the last serving gNB 203 may receive DL signaling or DL ​​data (5). DL signaling may be received from the AMF, and DL data may be received from the user plane function (UPF).

[0071] The last serving gNB 203 performs (5b) paging for the subsequent emergency call back as part of the activated emergency PDU session. In one example, a paging message (5b) is sent from the last serving gNB 203 to the receiving gNB 201. As part of the paging message, data including an indication for disabling, enabling, or re-enabling use of at least one network operation of the network device 103 for the UE 101 may be provided. Figure 4 In the example of , the paging message may include data including an indication for disabling the use of the PEI. The last serving node 203 and the receiving node 201 disable the PEI (6) so that any paging message generated will not use the PEI.

[0072] The last serving gNB 203 can generate a paging message for UE 101 without using PEI (7a) and subgroup-based UE ID. The receiving gNB 201 can generate a paging message for UE 101 without using PEI (7b) and subgroup-based UE ID.

[0073] That is, the receiving gNB 201 or the last serving gNB 203 may send a paging message to the UE 101 as part of a PDU (or Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Radio Access Bearer (E-RAB) session) for the emergency call, wherein the paging message is sent without a paging early indication (PEI) and / or a user equipment (UE) identifier (UE ID) associated with a subgroup of user equipment (UE).

[0074] The RRC connection may be restored (8) in the last serving gNB or the receiving gNB. If the connection is restored in the receiving gNB, the UE context is transferred from the last serving gNB to the receiving gNB using the UE context retrieval procedure via the Xn / X2 interface so that the receiving gNB assumes the role of the last serving gNB. That is, the UE 101 may switch from the RRC Inactive Operational State to the RRC Connected Operational State. The emergency PDU session may be released (9). As part of the release procedure, the CN function 105 may send (9a) a DL NAS Transfer message (including a PDU Session Release Command) to the last serving gNB 203. The DL NAS Transfer message may include information indicating an indication to enable / re-enable the use of the PEI. The last serving gNB 203 transmits (9b) the received DL NAS message to the UE 101. The NAS layer in the UE may, based on the content of the message, instruct the AS layer in the UE to start using the PEI and the subgroup-based UE ID. As a result, the UE 101 starts / re-starts using the PEI (10). When receiving DL signaling from the AMF or DL, the last serving gNB 203(11) may receive data from the user plane function (UPF). The last serving gNB may enable / re-enable the use of PEI and subgroup-based UE ID.

[0075] A paging message (11b) may be sent from the last serving gNB 203 to the receiving gNB 201. The paging message may include information indicating an indication that use of the PEI should be enabled / reenabled. Thus, the receiving gNB 201 (and the last serving gNB 203) may enable / reenable use of the PEI (12). The last serving gNB 203 may send (13a) a paging message to the UE 101, the paging message including a paging early indication (PEI) and a user equipment (UE) identifier (UE ID) associated with a subgroup of user equipment (UE). The receiving gNB 201 may send (13b) a paging message to the UE 101, the paging message including a paging early indication (PEI) and a user equipment (UE) identifier (UE ID) associated with a subgroup of user equipment (UE).

[0076] Figure 5A communication flow is provided according to an example, wherein a UE-initiated dynamic capability update is used during an emergency PDU session before the UE switches to an RRC idle running state.

[0077] exist Figure 5 In the example of FIG, 1 , UE 101 initiates (1) an emergency call, and a CN function 105 of the network for the emergency call establishes an emergency PDU (or Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Radio Access Bearer (E-RAB), etc.) session for the emergency call. For example, the CN function 105 may include an access and mobility function (AMF) or a mobility management entity (MME) of the network.

[0078] The CN function 105 sends (1a) a DL NAS transfer message (including a PDU session establishment accept message) to the gNB 501. The DL NAS transfer message includes information indicating that the use of the PEI is disabled. The gNB 501 transmits (1b) a DL NAS message to the UE 101. The NAS layer in the UE can recognize that an emergency PDU session has been established and should indicate this to the AS layer. Based on this indication from the NAS layer to the AS layer, the UE 101 stops using network operations. That is, in one example, the UE 101 stops using the PEI and initiates a capability update procedure to disable NR paging subgroup support for the gNB at the AS layer and disable NR paging subgroup support for the core network function at the NAS layer. In one example, the UE autonomously initiates a UE capability update procedure to update the UE's PEI and subgroup-related capabilities to the gNB at the AS layer and to the CN / AMF at the NAS layer.

[0079] When the initial emergency call is completed, the emergency PDU session remains in the active state (3). That is, the CN function 105 does not terminate the emergency PDU session. After the emergency call is completed, the UE 101 switches to the RRC idle running state (4).

[0080] The CN function 105 sends (5) a page for a subsequent emergency callback to the gNB 501 as part of the activated emergency PDU session. Since the capability update procedure of the UE 101 has provided information to the AS layer and the NAS layer to disable NR paging subgroup support, a paging message without PEI is generated (6) by the gNB 501 and sent (7) to the UE 101. That is, the paging message is sent without a paging early indication (PEI) and / or a user equipment (UE) identifier (UEID) associated with the subgroup of user equipment (UE). The emergency callback can be established (8) as part of the emergency PDU session.

[0081] The emergency PDU session may be released (9). As part of the release procedure, the CN function 105 may send (9a) a DL NAS Transport message (including a PDU Session Release Command) to the gNB 501. The gNB 501 may forward information from the received DL NAS Transport message to the UE 101 (9b). Accordingly, the UE 101 resumes using the PEI based on the indication from the UE NAS layer to the UE AS layer (from 9b) and initiates a capability update procedure to re-enable the NR paging subgroup (10). The NR paging subgroup is enabled at the AS layer and the NAS layer (10a).

[0082] A paging message (11) may be sent from the CN function 105 to the gNB 501. When PEI is enabled / reenabled (12), the gNB 501 sends (13) a paging message to the UE 101, the paging message including a paging early indication (PEI) and / or a user equipment (UE) identifier (UE ID) associated with a subgroup of user equipment (UE).

[0083] Figure 6 A communication flow is provided according to an example, wherein a UE-initiated dynamic capability update is used during an emergency PDU session before the UE switches to an RRC inactive running state.

[0084] exist Figure 6In the example of FIG, 1 , UE 101 initiates (1) an emergency call, and a CN function 105 of the network for the emergency call establishes an emergency PDU (or Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Radio Access Bearer (E-RAB), etc.) session for the emergency call. For example, the CN function 105 may include an access and mobility function (AMF) or a mobility management entity (MME) of the network.

[0085] The CN function 105 sends (1a) a DL NAS transfer message (including a PDU Session Setup Accept message) to the last serving gNB 203. The DL NAS transfer message includes information indicating an indication of disabling the use of the PEI. The last serving gNB 203 stores this information disabling the use of the PEI in the UE context, which represents the configuration of the UE and is maintained on the last serving gNB. The last serving gNB 203 transmits (1b) the received DL NAS message to the UE 101. The UE 101 stops using network operations. That is, in one example, the UE 101 stops using the PEI, and the non-access stratum (NAS) indicates this to the access stratum (AS) of the UE. The UE initiates a capability update procedure to disable NR paging subgroup support at the AS layer and the NAS layer (2).

[0086] When the initial emergency call is completed, the emergency PDU session remains in the active state (4). That is, the CN function 105 does not terminate the emergency PDU session. After the emergency call is completed, the UE 101 switches to the RRC inactive state (5). Figure 6 In the example shown in FIG5 , the last serving gNB 203 may receive (5a) DL signaling or DL ​​data. DL signaling may be received from the AMF, and DL data may be received from the UPF.

[0087] The last serving gNB 203 performs (5b) paging for the subsequent emergency callback as part of the activated emergency PDU session. In one example, a paging message (5b) is sent from the last serving gNB 203 to the receiving gNB 201. The last serving gNB 203 and the receiving gNB 201 disable PEI (6) so that any paging messages generated do not use PEI.

[0088] The last serving gNB 203 can generate a paging message for UE 101 without using PEI (7a) and subgroup-based UE ID. The receiving gNB 201 can generate a paging message for UE 101 using PEI (7b) and subgroup-based UE ID.

[0089] That is, the receiving gNB 201 or the last serving gNB 203 may send a paging message to the UE 101 as part of a PDU (or Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Radio Access Bearer (E-RAB) session) for the emergency call, wherein the paging message is sent without a paging early indication (PEI) and / or a user equipment (UE) identifier (UE ID) associated with a subgroup of user equipment (UE).

[0090] The RRC connection can be restored (8) in the last serving gNB or the receiving gNB. If the connection is restored in the receiving gNB, the UE context is transferred from the last serving gNB to the receiving gNB using the UE context retrieval procedure via the Xn / X2 interface so that the receiving gNB assumes the role of the last serving gNB. That is, the UE 101 can switch from the RRC Inactive Operational State to the RRC Connected Operational State. The emergency PDU session can be released (9). As part of the release procedure, the CN function 105 can send (9a) a DL NAS Transfer message (including a PDU Session Release Command) to the last serving gNB 203. The last serving gNB 203 transmits (9b) the received information to the UE 101. As a result, the UE 101 resumes using the PEI based on the NAS indication (from 9b) and initiates the capability update procedure to re-enable the NR paging subgroup (10). The NR paging subgroup is enabled at the AS layer and the NAS layer (10a). The last serving gNB 203(11) may receive data from the UPF when receiving DL signaling from the AMF or DL. The last serving gNB may enable / re-enable the use of PEI and subgroup-based UE ID.

[0091] A paging message (11b) may be sent from the last serving gNB 203 to the receiving gNB 201. The paging message may include information indicating an indication that use of the PEI should be enabled / reenabled. Thus, the receiving gNB 201 (and the last serving gNB 203) may enable / reenable use of the PEI (12). The last serving gNB 203 may send (13a) a paging message to the UE 101, the paging message including a paging early indication (PEI) and a user equipment (UE) identifier (UE ID) associated with a subgroup of user equipment (UE). The receiving gNB 201 may send (13b) a paging message to the UE 101, the paging message including a paging early indication (PEI) and a user equipment (UE) identifier (UE ID) associated with a subgroup of user equipment (UE).

[0092] Examples in the present disclosure may be provided as processes, methods, systems, or machine-readable instructions, such as any combination of software, hardware, firmware, etc. Such machine-readable instructions may be embodied in a computer-readable storage medium (including but not limited to disk storage, CD-ROM, optical storage, etc.) having computer-readable program code therein or thereon.

[0093] The present disclosure is described in conjunction with the flowcharts and / or block diagrams of the methods, devices, and systems provided by the examples of the present disclosure. Although the above flowcharts show a specific execution order, the execution order may be different from that described. The blocks described in conjunction with one flowchart can be combined with the blocks described in conjunction with another flowchart. In some examples, some blocks of the flowcharts may not be required and / or additional blocks may be added. It should be understood that each process and / or block in the flowcharts and / or block diagrams and the combination of processes and / or diagrams in the flowcharts and / or block diagrams can be implemented by the machine-readable instructions.

[0094] For example, machine-readable instructions can be executed by a machine such as a general-purpose computer, a platform including user devices such as smart devices (such as smart phones), a dedicated computer, an embedded processor, or a processor of other programmable data processing devices to implement the functions described in the specification and the drawings. Specifically, the processor or processing device can execute the machine-readable instructions. Therefore, the module of the device can be implemented by a processor that executes machine-readable instructions stored in a memory, or a processor that operates according to instructions embedded in a logic circuit. The term "processor" should be broadly interpreted to include a CPU, a processing unit, an ASIC, a logic unit, or a programmable gate group, etc. Both the method and the module can be executed by a single processor or divided between multiple processors.

[0095] Such machine-readable instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific mode. For example, the instructions may be provided in a non-transitory computer-readable storage medium encoded with instructions that are executable by a processor.

[0096] Figure 7 is a schematic diagram of a machine according to an example. For example, machine 600 can be a system or device, user equipment, or a portion thereof (e.g., a network device, a core network device, or a UE). Machine 700 includes a processor 703 and a memory 705 for storing instructions 707 executable by processor 703. The machine also includes a storage module 709 that can be used to store data.

[0097] Instructions 707 executable by processor 703 may cause machine 700 (e.g., which may be a network device) to: receive data including an indication, wherein the indication is for disabling, enabling, or re-enabling use of at least one network operation of the network device for user equipment (UE), the user equipment (UE) being in a radio resource control (RRC) idle or inactive operating state, and the user equipment (UE) being involved in an activated packet data unit (PDU) session or an evolved universal terrestrial radio access network (E-UTRAN) radio access bearer (E-RAB) session for an emergency call, and use the received data to disable, enable, or re-enable at least one network operation.

[0098] Thus, the machine 700 may implement a method for disabling, enabling, or re-enabling use of at least one network operation (eg, a paging operation) of a network device for a user equipment (UE) during an emergency PDU session.

[0099] Such machine-readable instructions may also be loaded onto a computer or other programmable data processing device so that the computer or other programmable data processing device performs a series of operations to generate computer-implemented processing instructions, whereby the instructions executed on the computer or other programmable device will provide operations for implementing the functions specified by the processes in the flowcharts and / or the blocks in the block diagrams.

[0100] Furthermore, the teachings herein may be implemented in the form of a computer or software product, such as a non-transitory machine-readable storage medium, in which the computer software or product is stored and includes a plurality of instructions (e.g., machine-readable instructions) that enable a computer device to implement the methods described in the examples of the present disclosure.

[0101] In some examples, certain methods may be performed in a cloud computing or web-based environment. A cloud computing environment may provide various services and applications over the Internet. These cloud-based services (e.g., software as a service, platform as a service, infrastructure as a service, etc.) may be accessed via a web browser or other remote interface on a user's device. Various functions described herein may be provided via a remote desktop environment or any other cloud-based computing environment.

[0102] Although various embodiments are described and / or illustrated herein in the context of a fully functional computer system, one or more of these exemplary embodiments may be published as a program product in various forms, without regard to the specific type of computer-readable storage medium used to actually perform the publication. The embodiments disclosed herein may also be implemented using software modules that perform some specific tasks. These software modules may include scripts, batches, or other executable files that may be stored on a computer-readable storage medium or in a computing system. In some embodiments, these software modules may configure a computing system to perform one or more exemplary embodiments disclosed herein. In addition, one or more modules described herein may convert data, physical devices, and / or representations of physical devices from one form to another.

[0103] The foregoing description is provided to enable those skilled in the art to best utilize the various aspects of the exemplary embodiments disclosed herein. This exemplary description is not intended to be exhaustive or to limit the disclosure to the precise form disclosed. Various modifications and variations may be made without departing from the spirit and scope of the disclosure. The embodiments disclosed herein are to be considered in all respects as illustrative and not restrictive. Reference should be made to the appended claims and their equivalents in determining the scope of the disclosure.

Claims

1. A network device in a telecommunications network, characterized in that: The telecommunications network includes at least one core network and at least one network node, and the network device is configured to: receiving data comprising an indication for disabling, enabling, or re-enabling use of at least one network operation of the network device for a user equipment (UE), the user equipment (UE) being in a radio resource control (RRC) idle or inactive operating state and the user equipment (UE) being involved in an active packet data unit (PDU) session or an evolved universal terrestrial radio access network (E-UTRAN) radio access bearer (E-RAB) session for an emergency call; The received data is used to disable, enable, or re-enable the at least one network operation.

2. The network device according to claim 1, wherein: The network operation includes at least one of the following: paging early indication (PEI), extended discontinuous reception (eDRX), wake-up signal (WUS), or group wake-up signal (GWUS), wherein the paging early indication (PEI) includes a subgroup-based user equipment (UE) identifier (UE identifier, UE ID).

3. The network device according to claim 1 or 2, characterized in that: The network device is configured to receive the data from the at least one core network or the at least one network node of the telecommunication network.

4. The network device according to claim 3, wherein: The network device is further configured to receive the data as part of a paging message from the at least one core network of the telecommunications network.

5. The network device according to claim 4, wherein: The network device is also used to: receive the data as part of a paging message for an emergency call back from the at least one core network of the telecommunications network, wherein the emergency call back is received by the UE as part of the activated Packet Data Unit (PDU) session or Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Radio Access Bearer (E-RAB) session for the emergency call.

6. The network device according to any one of the preceding claims, characterized in that The network device is further configured to: Sending a paging message to the user equipment (UE) as part of the packet data unit (PDU) session or evolved universal terrestrial radio access network (E-UTRAN) radio access bearer (E-RAB) session for the emergency call, wherein the paging message is sent without a paging early indication (PEI) and / or a user equipment (UE) identifier (UE ID) associated with a subgroup of the user equipment (UE).

7. The network device according to any one of the preceding claims, characterized in that The data comprises a portion of a downlink (DL) non-access stratum (NAS) message from at least one core network of the telecommunications network.

8. The network device according to claim 7, wherein: The network device is also used to: when establishing the emergency call for the user equipment (UE), receive the data including an indication as part of a packet data unit (PDU) session or an evolved universal terrestrial radio access network (E-UTRAN) radio access bearer (E-RAB) session acceptance message sent by at least one core network of the telecommunications network, wherein the indication is used to disable the use of paging early indication (PEI), extended discontinuous reception (eDRX), wake-up signal (WUS) or group wake-up signal (GWUS) for the user equipment (UE).

9. The network device according to claim 7 or 8, characterized in that: The network device is used to: when releasing the emergency call for the user equipment (UE), receive the data including an indication as part of a packet data unit (PDU) session or an evolved universal terrestrial radio access network (E-UTRAN) radio access bearer (E-RAB) session release message sent by at least one core network of the telecommunications network, wherein the indication is used to re-enable the use of paging early indication (PEI), extended discontinuous reception (eDRX), wake-up signal (WUS) or group wake-up signal (GWUS) for the user equipment (UE).

10. The network device according to any one of the preceding claims, characterized in that The network device includes a functionally separated network device, wherein the functionally separated network device includes a centralized unit (CU) and a distributed unit (DU), and the network device is configured to: receive the data from the at least one core network of the telecommunications network using an F1 interface configured between the CU and the DU.

11. A core network device of a telecommunications network, characterized in that: The telecommunications network includes at least one core network and at least one network node, wherein the core network device is configured to: Data including an indication is sent to a network device of the telecommunications network, wherein the indication is used to disable, enable, or re-enable use of at least one network operation for user equipment (UE), the UE being in a radio resource control (RRC) idle or inactive operating state and the UE being involved in an active session for an emergency call.

12. The core network device according to claim 11, characterized in that: The activated session for the emergency call includes an activated packet data unit (PDU) session or an evolved universal terrestrial radio access network (E-UTRAN) radio access bearer (E-RAB) session for the emergency call; the network operation includes at least one of the following: paging early indication (PEI), extended discontinuous reception (eDRX), wake up signal (WUS), or group wake up signal (GWUS), wherein the paging early indication (PEI) includes a subgroup-based user equipment (UE) identifier (UE identifier, UE ID).

13. The core network device according to claim 12, characterized in that: The core network device is used to: send the data as part of a paging message for an emergency call back, wherein the emergency call back is received by the user equipment (UE) as part of the packet data unit (PDU) session or evolved universal terrestrial radio access network (E-UTRAN) radio access bearer (E-RAB) session for the emergency call.

14. The core network device according to any one of claims 11 to 13, characterized in that: The core network device is configured to send the data including an indication as part of a downlink (DL) non-access stratum (NAS) message, wherein the indication is configured to disable, enable, or re-enable the at least one network operation.

15. A user equipment, characterized in that: The user equipment (UE) is participating in an active Packet Data Unit (PDU) session or an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Radio Access Bearer (E-RAB) session for an emergency call, and the user equipment (UE) is configured to: receiving data from a network device in a telecommunications network, wherein the telecommunications network includes at least one core network and at least one network node, the data representing an indication of establishment or release of the emergency call; Data is sent to the at least one core network and the at least one network node of the telecommunications network to disable or enable use of paging early indication and paging subgroups for the user equipment (UE), wherein the data is provided as part of a user equipment (UE) capability information message.

Images