Methods for configuring paging assistance information, methods for establishing connections, electronic devices and computer program products
By configuring the PEI CN subgroup ID and anomaly indication information, the paging compatibility issue between different 5G protocol versions was resolved, improving network paging efficiency and the stability of emergency communication, while reducing resource consumption.
Patent Information
- Application Number
- CN202510591267.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-05-08
- Publication Date
- 2026-11-10
AI Technical Summary
Between the 5G R17/R18 and R19 protocol versions, compatibility issues caused by differences in the PEI paging packet mechanism affect network paging efficiency and resource consumption.
By configuring paging assistance information, including PEI CN subgroup ID or anomaly indication, the paging strategy between the UE and the network can be optimized, ensuring protocol version compatibility, reducing the paging broadcast range, and lowering network resource consumption.
It improved network paging efficiency, reduced paging broadcast range, lowered network resource consumption, and ensured the stability and efficiency of emergency communications.
Smart Images

Figure CN123075666A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of communication technology, and more specifically, to a method for configuring paging assistance information, a connection establishment method, an electronic device, and a computer program product. Background Technology
[0002] In 5G Release 17 / R18, when a User Equipment (UE) has an emergency PDU (Protocol Data Unit) session, packet paging based on Paging Early Indication (PEI) is not used. However, in Release 19, there is no restriction preventing the UE and network from using PEI packet paging when an emergency PDU session exists. Because Release 17 / R18 and Release 19 handle the support for PEI paging packets differently when an emergency PDU session exists, compatibility issues may arise when the UE, gNB, and AMF (Access and Mobility Management Function) are deployed using different protocol versions. Summary of the Invention
[0003] This application provides a method for configuring paging assistance information, a connection establishment method, an electronic device, and a computer program product to at least solve the compatibility problem caused by differences in PEI paging packet mechanisms between different protocol versions of UEs and networks in the related art.
[0004] According to one embodiment of this application, a method for configuring paging assistance information is provided, applied to the Access and Mobility Management Function (AMF), comprising:
[0005] The terminal UE sends a first indication information, wherein the first indication information is used to indicate support for the Early Paging Indication (PEI) paging grouping mechanism;
[0006] Configure paging assistance information for the UE according to the first indication information, wherein the paging assistance information includes the Paging Early Indication Core Network Subgroup ID (PEI CN subgroup ID) or the paging assistance information is used to indicate PEI paging packet anomalies.
[0007] According to another embodiment of this application, a method for configuring paging assistance information is also provided, applied to a UE, including:
[0008] A first indication message is sent to the Access and Mobility Management Function (AMF), wherein the first indication message is used to indicate support for the Early Paging Indication (PEI) paging packet mechanism.
[0009] Receive paging assistance information sent by AMF, wherein the paging assistance information includes the Paging Early Indication Core Network Subgroup ID (PEI CN subgroup ID) or the paging assistance information is used to indicate PEI paging packet anomalies.
[0010] According to another embodiment of this application, a connection establishment method is also provided, applied to a relay UE, comprising:
[0011] Receive connection request messages sent by remote UEs through the Signaling Radio Bearers (SRB0) channel;
[0012] In non-Radio Resource Control (RRC) connected mode, the connection request message is forwarded to the target network node of the remote UE using the pre-assigned remote UE LocalID.
[0013] According to yet another embodiment of this application, a computer-readable storage medium is also provided, wherein a computer program is stored therein, and the computer program is configured to perform the steps in any of the above method embodiments when it is run.
[0014] According to yet another embodiment of this application, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.
[0015] According to yet another embodiment of this application, a computer program product is also provided, including a computer program that, when executed by a processor, implements the steps in any of the above method embodiments.
[0016] Through the above embodiments of this application, a first indication information sent by a terminal UE is received, wherein the first indication information is used to indicate support for the Early Paging Indication (PEI) paging grouping mechanism; paging assistance information is configured for the UE according to the first indication information, wherein the paging assistance information includes the Early Paging Indication Core Network Subgroup ID (PEI CN subgroup ID) or the paging assistance information is used to indicate PEI paging grouping anomalies. This can at least solve the compatibility problem between UEs with different protocol versions and networks caused by differences in the PEI paging grouping mechanism in related technologies, thereby improving network paging efficiency. Through the reasonable allocation of PEI CN subgroup IDs, the scope of paging broadcasts can be significantly reduced, and network resource consumption can be reduced. Attached Figure Description
[0017] Figure 1 This is a schematic diagram of the hardware structure of the mobile terminal used in the embodiments of the method of this application;
[0018] Figure 2 This is a flowchart of a paging assistance information configuration method according to an embodiment of this application. Figure 1 ;
[0019] Figure 3 This is a flowchart of a paging assistance information configuration method according to an embodiment of this application. Figure 2 ;
[0020] Figure 4 This is a flowchart of a connection establishment method according to an embodiment of this application;
[0021] Figure 5 This is a schematic diagram illustrating the indirect connection of multiple relay UEs to a network according to embodiments of this application. Detailed Implementation
[0022] The embodiments of this application will be described in detail below with reference to the accompanying drawings and examples.
[0023] It should be noted that the terms "first," "second," etc., in the specification, claims, and drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.
[0024] The methods and embodiments provided in this application can be executed on a mobile terminal, computer terminal, or similar computing device. Taking running on a mobile terminal as an example, Figure 1 This is a schematic diagram of the hardware structure of the mobile terminal used in the embodiments of the method of this application. For example... Figure 1 As shown, a mobile terminal may include one or more ( Figure 1 Only one is shown in the diagram. A processor 102 (which may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.) and a memory 104 for storing data are also shown. The mobile terminal may further include a transmission device 106 for communication functions and an input / output device 108. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the mobile terminal described above. For example, the mobile terminal may also include components that are more... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.
[0025] The memory 104 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the paging assistance information configuration method in this embodiment. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, thus implementing the above-described method. The memory 104 may include high-speed random access memory and non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to the mobile terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.
[0026] The transmission device 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the mobile terminal's communication provider. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be a Radio Frequency (RF) module used for wireless communication with the Internet.
[0027] This embodiment provides a method for configuring paging assistance information running on the aforementioned mobile terminal or network architecture. Figure 2 This is a flowchart of a paging assistance information configuration method according to an embodiment of this application. Figure 1 ,like Figure 2 As shown, the process applied to the Access and Mobility Management Function (AMF) includes the following steps:
[0028] Step S202: Receive first indication information sent by the terminal UE, wherein the first indication information is used to indicate support for the Early Paging Indication (PEI) paging packet mechanism;
[0029] Step S204: Configure paging assistance information for the UE according to the first indication information, wherein the paging assistance information includes the paging early indication core network subgroup ID (PEI CN subgroup ID) or paging assistance information used to indicate PEI paging packet anomalies.
[0030] Through the above steps S202 to S204, the compatibility problem caused by the difference in PEI paging grouping mechanism between UEs and networks with different protocol versions can be resolved at least. By reasonably allocating PEI CN subgroup IDs, the scope of paging broadcasts can be significantly reduced, and network resource consumption can be reduced.
[0031] Paging Early Indication (PEI) is a paging grouping mechanism that optimizes network paging efficiency for UEs. By dividing UEs into different PEI groups, the network can more accurately page target UEs and reduce unnecessary paging broadcasts. The PEI CN subgroup ID is an identifier assigned to the UE to identify its PEI group on the network side, enabling rapid UE location during paging. The AMF receives first indication information from the UE supporting the PEI paging grouping mechanism and configures paging assistance information, including but not limited to the PEI CN subgroup ID, based on this information. This improves network paging efficiency, especially in network environments with a large number of UEs. Proper allocation of the PEI CN subgroup ID can significantly reduce the scope of paging broadcasts and lower network resource consumption.
[0032] In one embodiment, step S204 may include: if the UE has already established an Emergency Protocol Data Unit (PDU) session, and the AMF does not support configuring paging assistance information when the UE has already established an PDU session, sending PEI anomaly indication information to the UE, wherein the PEI anomaly indication information is used to indicate an anomaly in the PEI paging group. An Emergency Protocol Data Unit (PDU) session is a special network connection established by the UE in emergency situations (such as emergency calls). In this case, the network needs to ensure the stability of the UE's connection and the priority of data transmission. When the UE has already established an emergency PDU session, the AMF may not support configuring the PEI CN subgroup ID due to network policies or the special nature of the emergency session. In this case, the AMF sends PEI anomaly indication information to the UE, informing the UE that the current PEI paging group mechanism is unavailable. This mechanism ensures that in emergency session scenarios, the network can take appropriate measures to guarantee the UE's communication needs, while avoiding paging conflicts caused by improper PEI configuration, thus ensuring the priority and stability of emergency communication.
[0033] In another embodiment, step S204 may further include: if the UE has not yet established an Emergency Protocol Data Unit (EPD) session, configuring a PEI CN subgroup ID for the UE. In regular communication scenarios where the UE has not established an EPDD session, the AMF can configure a PEI CN subgroup ID for the UE to support the PEI paging grouping mechanism. By rationally allocating PEI CN subgroup IDs, the network can achieve accurate paging of UEs, reduce the scope of paging broadcasts, and improve the utilization efficiency of network resources. This mechanism is particularly important in network environments with a large number of UEs, as it not only improves paging efficiency but also reduces interference to other UEs and optimizes overall network performance.
[0034] In one embodiment, the method further includes: if a PEI CN subgroup ID has been configured for the UE, after the UE establishes an emergency protocol data unit session, sending a first update message to the UE to update the PEI CN subgroup ID configuration. When the UE enters the emergency PDU session state from the normal communication state, the network may need to adjust the PEI CN subgroup ID configuration to adapt to the special needs of emergency communication. The AMF updates the UE's PEI CN subgroup ID configuration by sending the first update message, ensuring that the network can adopt the most appropriate paging strategy in emergency communication scenarios, guaranteeing that the UE's emergency communication needs are responded to in a timely manner. This reflects the network's flexibility and adaptability, enabling dynamic adjustment of paging strategies in different communication scenarios and improving user experience.
[0035] Furthermore, the first update message does not contain the UE's PEI CN subgroup ID; or the first update message carries an instruction to instruct the UE to release the PEI CN subgroup ID. In some cases, the network may decide not to use the PEI CN subgroup ID for paging packets after the UE establishes an emergency PDU session. In this case, the first update message sent by the AMF may not contain the PEI CN subgroup ID, but instead contain an instruction to instruct the UE to release the identifier. This ensures flexible adjustment of network policies, avoids the use of inapplicable paging policies in emergency communication scenarios, and thus guarantees the efficiency and reliability of emergency communication.
[0036] In another embodiment, the method further includes receiving protocol version indication information sent by the UE, wherein the protocol version indication information includes the UE's protocol version information or an indication of whether it is an R19 UE. The protocol version indication information is the UE reporting its supported protocol versions to the network, which is crucial for the network to determine whether it supports specific functions (such as the PEI paging grouping mechanism). For example, an R19 UE may support more advanced paging assistance information configurations, while earlier versions of UEs may not. By receiving the UE's protocol version indication information, the AMF can determine whether the UE supports the configuration of the PEI CN subgroup ID, and thus take appropriate paging strategies. This ensures protocol compatibility between the network and the UE, avoiding paging failures or inefficiencies caused by protocol version mismatches.
[0037] In one embodiment of this application, if the UE's protocol version does not support the use of paging assistance information when an emergency protocol data unit session has been established, the PEI CN subgroup ID will not be included in the paging message associated with the UE, even if an emergency protocol data unit session has been established. When the UE's protocol version does not support the use of the PEI CN subgroup ID in an emergency PDU session, the network will not include this identifier in the paging message when paging the UE. This mechanism avoids paging configuration errors caused by UE protocol version limitations, ensuring the correctness and effectiveness of the network paging strategy. Especially in network environments with diverse UE protocol versions, it can effectively avoid paging anomalies and guarantee the UE's communication quality.
[0038] In another embodiment, the method further includes sending the UE's PEI CN subgroup ID to the base station. The AMF sending the UE's PEI CN subgroup ID to the base station enables the base station to perform paging operations based on this identifier, which is a key step in implementing the PEI paging grouping mechanism. By using the PEI CN subgroup ID by the base station, the network can accurately page UEs, reduce the scope of paging broadcasts, and improve the utilization efficiency of network resources. This mechanism is particularly important in network environments with a high density of UEs, as it not only improves paging efficiency but also reduces interference to other UEs, optimizing overall network performance.
[0039] In another embodiment, if the UE's PEI CN subgroup ID has already been sent to the base station, after the UE establishes an Emergency Protocol Data Unit (EPD) session, a second update message updating the UE's PEI CN subgroup ID configuration is sent to the base station. When the UE enters the emergency PDU session state from the normal communication state, the network may need to adjust the PEI CN subgroup ID configuration on the base station side to adapt to the special needs of emergency communication. The AMF updates the base station's PEI CN subgroup ID configuration by sending the second update message, ensuring that in emergency communication scenarios, the base station can adopt the most appropriate paging strategy to guarantee timely response to the UE's emergency communication needs. This demonstrates the network's flexibility and adaptability, enabling dynamic adjustment of paging strategies in different communication scenarios and improving user experience.
[0040] Furthermore, the second update message may not contain the UE's PEI CN subgroup ID; or the second update message may carry an indication to release the UE's PEI CN subgroup ID; or the second update message may indicate that the UE is not an R19 UE; or the second update message may indicate the UE's protocol version information. In some cases, the network may decide not to use the PEI CN subgroup ID for paging packets after the UE establishes an emergency PDU session. In this case, the second update message sent by the AMF may not contain the PEI CN subgroup ID, but instead contain an instruction to the base station to release the identifier, or an instruction to the base station to provide the UE's protocol version information, so that the base station can take appropriate paging strategies. This mechanism ensures flexible adjustment of network strategies, avoids the use of inapplicable paging strategies in emergency communication scenarios, and thus guarantees the efficiency and reliability of emergency communication.
[0041] The second update message can specifically be Core Network RRC Inactive Assistance Information. Core Network RRC Inactive Assistance Information is a mechanism used by the network to provide paging assistance information when the UE is inactive (e.g., in idle mode). When the UE establishes an emergency PDU session, the AMF updates the base station's PEICN subgroup ID configuration by sending Core Network RRC Inactive Assistance Information. This not only ensures timely adjustments to the network paging strategy but also effectively reduces network resource consumption and improves network energy efficiency when the UE is inactive.
[0042] One aspect of this application provides a method for configuring paging assistance information. Figure 3 This is a flowchart of a paging assistance information configuration method according to an embodiment of this application. Figure 2 ,like Figure 3 As shown, when applied to a UE, the process includes the following steps:
[0043] Step S302: Send a first indication message to the Access and Mobility Management Function (AMF), wherein the first indication message is used to indicate support for the Early Paging Indication (PEI) paging packet mechanism;
[0044] Step S304: Receive paging assistance information sent by AMF, wherein the paging assistance information includes the Paging Early Indication Core Network Subgroup ID (PEI CN subgroup ID) or paging assistance information used to indicate PEI paging packet anomalies.
[0045] Through the above steps S302 to S304, the compatibility problem caused by the difference in PEI paging grouping mechanism between UEs and networks with different protocol versions can be solved at least. By reasonably allocating PEI CN subgroup IDs, the scope of paging broadcasts can be significantly reduced, and network resource consumption can be reduced.
[0046] The UE indicates its support for the PEI paging group mechanism by sending a first indication message to the AMF. This allows the network side to configure paging assistance information, including but not limited to the PEI CN subgroup ID (CoreNetworksubgroupIdentification), based on the UE's support. When the UE receives paging assistance information from the AMF, it can adjust its paging reception strategy according to the PEI CN subgroup ID or PEI paging group anomaly indication. This allows the UE to respond to network paging requests more quickly and accurately in emergency communication scenarios, improving communication timeliness and reliability. This solves the technical problem of efficiently and accurately paging UEs in environments with a large number of UEs and limited network resources. Through information interaction between the UE and the AMF, paging strategies are optimized, enhancing the user experience.
[0047] In this embodiment, step S204 may include: if an Emergency Protocol Data Unit (EPD) session has been established, and the AMF does not support configuring paging assistance information when the UE has established an EPD session, receiving PEI anomaly indication information sent by the AMF, wherein the PEI anomaly indication information is used to indicate PEI paging packet anomalies. When the UE has established an emergency PDU session, and the AMF does not support configuring PEI CN subgroup ID due to network policy or the special nature of the emergency session, the UE will receive PEI anomaly indication information from the AMF. This mechanism informs the UE that the current PEI paging packet mechanism is unavailable, and the UE needs to adopt other strategies to respond to the network's paging request. Through this mechanism, the UE can adjust its paging reception strategy in a timely manner, avoiding paging failures caused by improper PEI configuration, ensuring the priority and stability of emergency communication, and solving the technical problem of how to ensure UE paging response efficiency in emergency communication scenarios.
[0048] In one embodiment, if the PEI CN subgroup ID has been received, after establishing an emergency protocol data unit session, the UE receives a first update message from the AMF updating the PEI CN subgroup ID configuration. When the UE transitions from a normal communication state to an emergency PDU session state, the network may need to adjust the UE's PEI CN subgroup ID configuration to adapt to the specific needs of emergency communication. By receiving the first update message from the AMF, the UE can update its PEI CN subgroup ID configuration, ensuring that in emergency communication scenarios, the UE can adopt the most appropriate paging reception strategy and respond to the network's paging requests in a timely manner. This mechanism reflects the close collaboration between the UE and the network, enabling dynamic adjustment of paging strategies in different communication scenarios and improving user experience.
[0049] In another embodiment, the method further includes receiving an SIB message sent by the base station, wherein the SIB message contains second indication information, which indicates that the PEI CN subgroup ID will not be used when an emergency protocol data unit session has been established. The System Information Block (SIB) message is system information broadcast by the base station to the UE, which may contain network policies or configuration information. When the UE has established an emergency PDU session, the base station informs the UE through the second indication information in the SIB message that the PEI CN subgroup ID will not be used for paging in the current emergency communication scenario. This mechanism ensures that the UE can adjust its paging reception strategy according to network instructions, avoiding the use of inapplicable paging strategies in emergency communication scenarios, thereby ensuring the efficiency and reliability of emergency communication.
[0050] The following examples illustrate the implementation of this application using two different UE / gNB / AMF deployment scenarios with different protocol versions.
[0051] The deployment scenario for this embodiment is: R19 UE, R17 / 18gNB, R17 / 18AMF.
[0052] In 5G R17, an energy-saving scheme for UE listening to paging groups was introduced based on the traditional paging mechanism. To reduce UE power consumption caused by false paging, UE groups listening to the same paging occasion (PO) can be further divided into multiple subgroups. Through subgroup division, when the associated Paging Early Indication (PEI) indicates that a subgroup is being paging, UEs within that subgroup only need to listen to PDCCH (Physical Downlink Control Channel) paging within their PO. In other words, before receiving paging, the UE first attempts to receive the PEI (an additional indication preceding paging), which indicates whether the UE needs to receive paging in subsequent paging occasions. The PEI-based group paging method can reduce the false wake-up rate and reduce the negative impact of false paging, i.e., the unnecessary energy consumption caused by a UE waking up due to paging for another UE.
[0053] In Release 17 / R18, it was determined that when a UE has an emergency PDU session, latency requirements are high, necessitating rapid paging of idle / inactive UEs to allow them to quickly enter connected state and receive and send emergency services. If PEI-based packet paging is used while a UE has an emergency PDU session, latency will occur, impacting emergency service processing. Therefore, PEI-based packet paging should be avoided as much as possible when a UE has an emergency PDU session. Consequently, the protocol stipulates that when a UE has an emergency PDU session, it should not send indication information supporting PEI paging packets to the network / AMF, and the AMF will not configure a PEI packet ID for the UE when an emergency PDU session exists. Furthermore, if a UE has already obtained a PEI packet ID from the AMF and then established an emergency PDU session, neither the UE nor the AMF should use the PEI packet ID until the emergency PDU session is released. The R19 discussion argued that PSAP (Public Safety Answering Point) callbacks are transmitted as normal calls within an IMS PDU session. Therefore, when an emergency PDU session exists, there is no need to restrict the UE and network from using PEI packet paging.
[0054] The following example uses R18 gNB / AMF; R17 gNB / AMF is the same as R18 gNB / AMF. In other words, R19 UEs that support PEI no longer have the restriction of emergency PDU sessions, meaning they can still use PEI paging packets when an emergency PDU session exists. However, R18 gNB / AMF cannot use the core network-based PEI paging packet method.
[0055] An R19 UE that supports PEI can send an indication message to the R18 AMF indicating that it supports PEI paging packets (even if the UE has an emergency PDU session). After receiving the indication, the R18 AMF will find that the UE has an emergency PDU session and has two possible handling methods: 1) The R18 AMF will treat this as an abnormal situation (receiving the indication message that supports PEI paging packets from the UE when the UE has an emergency PDU session) and send a PEI abnormal indication message to the UE in the response message; 2) The R18 AMF will find that the UE has an emergency PDU session and will not configure a PEI CN subgroup ID (PEI packet ID based on core network packets) for the UE.
[0056] In another scenario, when the R19 UE sends an indication message supporting PEI paging packets to the R18 AMF, it lacks an emergency PDU session. Therefore, it obtains the PEI CN subgroup ID from the R18 AMF, and the R18 AMF sends the UE's PEI CN subgroup ID to the R18 gNB for configuration purposes related to determining whether the UE should enter the RRC inactive state. Subsequently, the UE establishes an emergency PDU session.
[0057] If the UE retains the context of the emergency PDU session when entering RRC idle state, when the R18 AMF initiates a paging of the UE and discovers that the UE has an emergency PDU session, it will not include the PEI CN subgroup ID in the paging message associated with the UE. Correspondingly, the R18 gNB will not use the PEI paging packet method to page the UE. However, the R19 UE, having previously obtained the PEI CN subgroup ID, will listen for its own subgroup ID in the PEI. In other words, the R19 UE will listen for the PEI, but the R18 gNB will not send the PEI subgroup ID to which the UE belongs. Therefore, the R19 UE will not be able to listen for its own PEI subgroup ID and will not wake up to listen for paging messages, thus missing its own paging message. To resolve this mismatch between network and UE behavior, the following method can be considered: After the UE establishes an emergency PDU session, the AMF sends a message to the UE to update the PEI CN subgroup ID configuration (e.g., a CONFIGURATIONUPDATE COMMAND message). Specifically, the AMF either no longer includes the UE's PEI CN subgroup ID in the message, or the AMF includes an instruction to release the PEI CN subgroup ID in the message. In this case, the UE will release the PEI CN subgroup ID configuration and will not use that group ID to listen for PEI packet paging.
[0058] If a UE retains the context of its emergency PDU session when entering the RRC inactive state, when the R18 gNB initiates RAN paging for the UE, the gNB can recognize that the UE has an emergency PDU session. Therefore, it will not use the PEI CN subgroup ID for RAN paging. However, the R19 UE, having previously obtained the PEI CN subgroup ID, will listen for its own packet ID in the PEI. This leads to the same problem as described above: the UE will miss its own paging messages. To resolve this mismatch between gNB and UE behavior, the following method can be considered: After the UE establishes an emergency PDU session, the AMF sends a message to the gNB to update the UE's PEI CN subgroup ID configuration (e.g., a Core Network RRC Inactive Assistance Information message). Specifically, the AMF should no longer include the UE's PEI CN subgroup ID in this message, or the AMF should include an instruction to release the PEI CN subgroup ID. Both the UE and gNB will release the PEI CN subgroup ID configuration and will not use this packet ID for PEI packet paging.
[0059] Alternatively, the gNB includes an indication in the SIB message that the PEI CN subgroup ID should not be used during an emergency PDU session. Upon receiving this indication in the SIB message, the R19 UE, even if it has already obtained the PEI CN subgroup ID, will still not use that group ID during an emergency PDU session, thus ensuring consistency between the UE and the gNB.
[0060] The deployment scenario for this embodiment is: R17 / 18UE, R19 gNB, R19 AMF.
[0061] The following explanation uses R18 UE as an example; R17 UE is the same as R18 UE. That is to say, R18 UE cannot use PEI paging packet mode based on core network packets when there is an emergency PDU session; while R19 gNB / AMF does not have the restriction of emergency PDU session, that is, it can still use PEI paging packets when there is an emergency PDU session.
[0062] When the R18 UE sends an indication message supporting PEI paging packets to the R19 AMF, it lacks an emergency PDU session. Therefore, it obtains the PEI CN subgroup ID from the R19 AMF, and the R19 AMF sends the UE's PEI CN subgroup ID to the R19 gNB for configuration purposes related to determining whether the UE should enter the RRC inactive state. Subsequently, the UE establishes an emergency PDU session. In other words, after configuring the UE's PEI CN subgroup ID, an emergency PDU session is established.
[0063] If the R18 UE retains the context of its emergency PDU session when entering RRC idle state, when the R19 AMF initiates a paging of the UE, since the UE's PEI CN subgroup ID has already been configured and there is no emergency PDU session restriction, the R19 AMF will include the PEI CN subgroup ID in the paging message associated with the UE. Correspondingly, the R19 gNB will use the UE's PEI CN subgroup ID to page the UE. However, if the R18 UE has an emergency PDU session, it will not use the PEI CN subgroup ID and will listen for its own paging messages in the traditional way. In this case, although the UE will not miss its own paging messages, a mismatch between UE behavior and network behavior still occurs, causing the base station to send extra signals / consume more power. To resolve this mismatch, the UE can indicate to the AMF whether it is an R19 UE or send its protocol version information to the AMF. If the UE is not an R19 UE, then when the R19 AMF initiates CN paging for the UE, it checks whether the UE has an emergency PDU session. If it does, the PEI CN subgroup ID will not be included in the paging message associated with the UE.
[0064] Similarly, a similar issue exists with RAN paging for RRC-inactive UEs. To address the mismatch between UE and gNB behavior, if the R19 AMF receives an indication from the UE that the UE is not an R19 UE, then after the UE establishes an emergency PDU session, the R19 AMF sends a message to the R19 gNB to update the UE's PEI CN subgroup ID configuration (e.g., a Core Network RRC Inactive Assistance Information message). Specifically, the AMF no longer includes the UE's PEI CN subgroup ID in this message, or the AMF includes an indication to release the PEI CN subgroup ID, or the AMF indicates in the message that the UE is not an R19 UE or its protocol version information. After receiving the indication, the base station does not use the PEI CN subgroup ID to page the UE when the UE has an emergency PDU session.
[0065] This application also provides a connection establishment method. Figure 4 This is a flowchart of a connection establishment method according to an embodiment of this application, such as... Figure 4 As shown, it is applied to a relay UE and includes:
[0066] Step S402: Receive a connection request message sent by the remote UE through the signaling radio bearer SRB0 channel;
[0067] Step S404: In the non-Radio Resource Control (RRC) connected state, the connection request message is forwarded to the target network node of the remote UE using the pre-assigned remoteUE Local ID.
[0068] Through steps S402 to S404, the relay UE, in a non-RRC connection state, can receive connection request messages sent by the remote UE via the SRB0 channel and forward the messages to the target network node of the remote UE using the pre-assigned remote UE Local ID. This mechanism enables the relay UE to support the connection requests of the remote UE even in a non-connection state, improving network coverage and connection establishment success rate. Especially when the UE is at the edge of network coverage or has poor signal, the relay UE can act as a signal enhancement node, helping the remote UE successfully establish a connection with the target network node by forwarding connection request messages. This solves the problem of improving connection establishment success rate when the UE is at the edge of network coverage, and through information forwarding between the relay UE and the remote UE, it expands network coverage and improves user experience.
[0069] In one embodiment of this application, the method further includes: after entering the RRC connection state, reporting sidelink UE information to the base station, wherein the sidelink UE information is used to indicate the association between the remote UE Local ID and the destination L2 ID. When the relay UE enters the RRC connection state, it reports the sidelink UE information to the base station, including the association between the remote UE Local ID and the destination L2 ID. This mechanism enables the network to understand the connection relationship between the relay UE and the remote UE, thereby enabling more accurate location of the remote UE during paging or data transmission, improving the efficiency of network paging and data transmission. Through information interaction between the relay UE and the base station, the technical problem of how to improve the efficiency of network paging and data transmission in multi-hop relay scenarios is solved. By reporting the association information, the network achieves precise management of the connection relationship between the relay UE and the remote UE, optimizing overall network performance.
[0070] Furthermore, the destination L2 ID in the sidelink UE information carries a pre-assigned remote UELocal ID; or the sidelink UE information carries indication information, where the indication information is used to indicate that the destination L2 ID is associated with the pre-assigned remote UE local ID. The destination L2 ID is the Layer 2 (L2) identifier of the target network node for establishing a connection between the relay UE and the remote UE, carrying a pre-assigned remote UE Local ID, or the sidelink UE information carries indication information indicating the association between the two. This mechanism ensures that the network can accurately page or transmit data to the remote UE through the relay UE, improving the efficiency of network paging and data transmission.
[0071] In another embodiment, the method further includes: reporting multi-hop relay-related capability information to the base station, wherein the capability information includes at least one of the following: the capability to support the relay UE, and the capability to forward remote UE SRB0 messages in a non-RRC connected state. The relay UE reports its multi-hop relay capability information to the base station, including but not limited to the capability to support the relay UE and the capability to forward remote UE SRB0 messages in a non-RRC connected state. This mechanism enables the network to understand the capabilities of the relay UE, thereby fully utilizing the relay UE's functions when needed, improving network coverage and connection establishment success rate. Especially when the UE is at the edge of network coverage or has poor signal, the relay UE can act as a signal enhancement node, helping the remote UE successfully establish a connection with the target network node by forwarding connection request messages.
[0072] Figure 5This is a schematic diagram illustrating the indirect connection of multiple relay UEs to a network according to embodiments of this application, such as... Figure 5 The diagram illustrates a multi-hop relay scenario, where a remote UE can indirectly connect to the network through multiple relay UEs. In multi-hop SL relay, a method to expedite connection establishment for remote UEs is proposed: allowing intermediate relay UEs to forward remote UE SRB0 messages while in non-RRC connected state. One approach is to pre-assign a remote UE Local ID to a UE that can act as an intermediate relay UE when it enters an inactive state. When this UE receives an SRB0 message from a remote UE via SL-RLC0, it uses the remote UE Local ID for forwarding the message. This eliminates the need to wait for the intermediate relay UE to enter connected state before retrieving its Local ID from the base station and forwarding the SRB0 message, thus accelerating RRC connection establishment for remote UEs to some extent. In this method, when an Intermediate relay UE reports sidelink UE Information to the base station after entering the RRC connected state, it needs to indicate the association between the pre-assigned remote UE Local ID and the destination L2 ID. For example, it can carry the pre-assigned remote UE Local ID under the corresponding destination L2 ID or carry an indication (indicating that the destination L2 ID is associated with the pre-assigned remote UE Local ID). A UE that can act as an Intermediate relay UE can report multi-hop relay related capability information to the base station, such as at least one of the following: supporting the capabilities of an Intermediate relay UE, and the ability to forward remote UE SRB0 messages in the RRC inactive state. Therefore, a remote UE Local ID is pre-assigned when the base station releases the UE and it enters the RRC inactive state.
[0073] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.
[0074] This embodiment also provides a paging assistance information configuration device, which is used to implement the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated. Applied to Access and Mobility Management Function (AMF), the device includes:
[0075] The first receiving module is configured to receive first indication information sent by the terminal UE, wherein the first indication information is used to indicate support for the Early Paging Indication (PEI) paging grouping mechanism;
[0076] The configuration module is configured to configure paging assistance information for the UE according to the first indication information, wherein the paging assistance information includes the Paging Early Indication Core Network Subgroup ID (PEI CN subgroup ID) or the paging assistance information is used to indicate PEI paging packet anomalies.
[0077] According to another embodiment of this application, a paging assistance information configuration device is also provided, applied to a UE, comprising:
[0078] The sending module is configured to send first indication information to the Access and Mobility Management Function (AMF), wherein the first indication information is used to indicate support for the Early Paging Indication (PEI) paging packet mechanism.
[0079] The second receiving module is used to receive paging assistance information sent by the AMF, wherein the paging assistance information includes the Early Paging Indicator Core Network Subgroup ID (PEI CN subgroup ID) or the paging assistance information is used to indicate PEI paging packet anomalies.
[0080] According to another embodiment of this application, a connection establishment apparatus is also provided, applied to a relay UE, the apparatus comprising:
[0081] The third receiving module is used to receive connection request messages sent by the remote UE through the signaling radio bearer SRB0 channel;
[0082] The forwarding module is used to forward the connection request message to the target network node of the remote UE using a pre-assigned remote UE Local ID in a non-Radio Resource Control (RRC) connected state.
[0083] It should be noted that the above modules can be implemented by software or hardware. For the latter, they can be implemented in the following ways, but are not limited to: all the above modules are located in the same processor; or, the above modules are located in different processors in any combination.
[0084] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the steps in any of the above method embodiments when run.
[0085] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.
[0086] Embodiments of this application also provide an electronic device including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.
[0087] In one exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.
[0088] Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.
[0089] Obviously, those skilled in the art should understand that the modules or steps of this application described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. They can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those presented here, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, this application is not limited to any particular combination of hardware and software.
[0090] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the principles of this application should be included within the protection scope of this application.
Claims
1. A method for configuring paging auxiliary information, characterized in that, The Access and Mobility Management Functions (AMF) applied to include: The terminal UE sends a first indication information, wherein the first indication information is used to indicate support for the Early Paging Indication (PEI) paging grouping mechanism; Configure paging assistance information for the UE according to the first indication information, wherein the paging assistance information includes the Paging Early Indication Core Network Subgroup ID (PEI CN subgroup ID) or the paging assistance information is used to indicate PEI paging packet anomalies.
2. The method according to claim 1, characterized in that, Configuring paging assistance information for the UE according to the first indication information includes: If the UE has already established an Emergency Protocol Data Unit (EPD) session, and the AMF does not support configuring the paging assistance information when the UE has already established the EPD session, the AMF will send PEI anomaly indication information to the UE, wherein the PEI anomaly indication information is used to indicate that the PEI paging packet is abnormal.
3. The method according to claim 1, characterized in that, Configuring paging assistance information for the UE according to the first indication information includes: If the UE has not yet established an Emergency Protocol Data Unit session, configure the PEI CN subgroupID for the UE.
4. The method according to claim 3, characterized in that, The method further includes: If a PEI CN subgroup ID has been configured for the UE, after the UE establishes the Emergency Protocol Data Unit session, a first update message updating the PEI CN subgroup ID configuration is sent to the UE.
5. The method according to claim 4, characterized in that, The first update message does not contain the UE's PEI CN subgroup ID; or The first update message carries an instruction to instruct the UE to release the PEI CN subgroup ID.
6. The method according to claim 1, characterized in that, The method further includes: The protocol version indication information sent by the UE is received, wherein the protocol version indication information includes the protocol version information of the UE or an indication of whether it is an R19 UE.
7. The method according to claim 6, characterized in that, If the UE's protocol version does not support the use of the paging assistance information when an emergency protocol data unit session has been established, the PEI CN subgroup ID will not be included in the paging message associated with the UE if the emergency protocol data unit session has been established.
8. The method according to claim 1, characterized in that, The method further includes: Send the UE's PEI CN subgroup ID to the base station.
9. The method according to claim 8, characterized in that, The method further includes: If the PEI CN subgroup ID of the UE has been sent to the base station, after the UE establishes an emergency protocol data unit session, a second update message updating the PEI CN subgroup ID configuration of the UE is sent to the base station.
10. The method according to claim 9, characterized in that, The second update message does not contain the UE's PEI CN subgroup ID; or The second update message carries an indication to release the PEI CN subgroup ID of the UE; or The second update message indicates that the UE is not an R19 UE; or The second update message indicates the protocol version information of the UE.
11. The method according to claim 9, characterized in that, The second update message is Core Network RRC Inactive Assistance Information.
12. A method for configuring paging auxiliary information, characterized in that, Applied to UE, including: A first indication message is sent to the Access and Mobility Management Function (AMF), wherein the first indication message is used to indicate support for the Early Paging Indication (PEI) paging packet mechanism. Receive paging assistance information sent by AMF, wherein the paging assistance information includes the Paging Early Indication Core Network Subgroup ID (PEI CN subgroup ID) or the paging assistance information is used to indicate PEI paging packet anomalies.
13. The method according to claim 12, characterized in that, The method further includes: If an Emergency Protocol Data Unit (EPD) session has already been established, and the AMF does not support configuring the paging assistance information when the UE has already established the EPD session, the UE receives the PEI anomaly indication information sent by the AMF, wherein the PEI anomaly indication information is used to indicate that the PEI paging packet is abnormal.
14. The method according to claim 12, characterized in that, If the PEI CN subgroup ID has been received, after establishing an Emergency Protocol Data Unit session, the first update message sent by the AMF to update the PEI CN subgroup ID configuration will be received.
15. The method according to claim 12, characterized in that, The method further includes: The system information block (SIB) message sent by the base station is received, wherein the SIB message contains second indication information, wherein the second indication information is used to indicate that the PEI CNsubgroup ID is not used when an emergency protocol data unit session has been established.
16. A connection establishment method, characterized in that, Applied to relay UEs, including: Receive connection request messages sent by remote UEs via the SRB0 channel of the signaling radio bearer; In non-Radio Resource Control (RRC) connected state, the connection request message is forwarded to the target network node of the remote UE using the pre-assigned remote UE Local ID.
17. The method according to claim 16, characterized in that, The method further includes: After entering the RRC connected state, the side link UE information is reported to the base station, wherein the side link UE information is used to indicate the association between the remote UE Local ID and the destination L2 ID.
18. The method according to claim 17, characterized in that, The destination L2 ID in the sidelink UE information carries the pre-assigned remote UE LocalID; or The sidelink UE information carries indication information, wherein the indication information is used to indicate that the destination L2ID is associated with a pre-assigned remote UE local ID.
19. The method according to claim 16, characterized in that, The method further includes: The system reports multi-hop relay-related capability information to the base station, wherein the capability information includes at least one of the following: the ability to support relay UEs, and the ability to forward remote UE SRB0 messages in non-RRC connected state.
20. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method described in any one of claims 1 to 11, 12 to 15, and 16 to 19.
21. A computer program product, characterized in that, Includes a computer program, which, when executed by a processor, implements the steps of the method described in any one of claims 1 to 11, 12 to 15, and 16 to 19.
