A ResumeIdentity parsing method for heterogeneous vendor networking scenarios

Abstract

The present invention provides a method for resolving ResumeIdentity in a cross-vendor networking scenario, belonging to the field of 5G communication technology. The method comprises: configuring multiple ResumeIdentity resolution rule tables within a cross-vendor 5G base station (gNB), setting resolution rules for different types of ResumeIdentity identifiers in each ResumeIdentity resolution rule table; when the cross-vendor gNB receives a Resume request from a user terminal (UE), the gNB finds a ResumeIdentity resolution rule table that matches the gNB and uses the resolution rules in the ResumeIdentity resolution rule table to resolve the Resume request from the UE. This method can implement ResumeIdentity resolution for cross-vendor gNBs.

Description

Technical Field

[0001] The present invention belongs to the field of mobile communication technology, and in particular relates to a ResumeIdentity parsing method for a heterogeneous vendor networking scenario. Background Art

[0002] 5G NR (New Radio) introduces the RRC_INACTIVE state. When notifying a UE (user terminal) that it has entered the RRC_INACTIVE state, the last serving gNB (base station) issues a fullI-RNTI and shortI-RNTI identifier for UE context restoration. A UE in the RRC_INACTIVE state can move within the RAN Notification Area (RNA). When the UE moves to another RAN, it initiates a Resume Request with the ResumeIdentity identifier (fullI-RNTI or shortI-RNTI) to request context restoration by the target gNB. Upon receiving the Resume Request, the target gNB parses the fullI-RNTI or shortI-RNTI identifier to obtain the identifier of the last serving gNB. It then retrieves the UE context from the gNB via the Xn interface and restores the UE's RRC connection.

[0003] When a UE initiates a Resume request, if the currently selected cell carries the useFullResumeID flag in its SIB1, it uses the fullI-RNTI to initiate the Resume request; otherwise, it uses the shortI-RNTI. The fullI-RNTI is 40 bits long, while the shortI-RNTI is 24 bits long. The fullI-RNTI and shortI-RNTI identifiers consist of the UE ID, the gNB ID, and some bits of the PLMN ID. The length of each component is customized by the base station vendor. Therefore, in a multi-vendor network, the base station receiving the Resume request cannot determine the fullI-RNTI and shortI-RNTI composition rules. Parsing them according to their own composition rules will result in gNBID parsing errors, preventing the UE context from being retrieved from the last serving gNB. This can cause the Resume request to fail and the UE to drop the call. Summary of the Invention

[0004] In order to overcome the deficiencies of the above-mentioned prior art, the present invention provides a ResumeIdentity parsing method for a heterogeneous vendor networking scenario.

[0005] In order to achieve the above object, the present invention provides the following technical solutions:

[0006] A ResumeIdentity parsing method for a heterogeneous vendor networking scenario includes:

[0007] Configure multiple ResumeIdentity resolution rule tables in the 5G base station gNB of a different manufacturer, and set resolution rules for different types of ResumeIdentity identifiers in each ResumeIdentity resolution rule table;

[0008] When a gNB of a different vendor receives a Resume request from a user terminal (UE), it finds the ResumeIdentity resolution rule table that matches the adjacent gNB and uses the resolution rules in the ResumeIdentity resolution rule table to parse the Resume request from the UE.

[0009] Furthermore, the parsing rules of the ResumeIdentity parsing rule table include:

[0010] Rule ID, used as the number of the ResumeIdentity resolution rule table in the base station;

[0011] ResumeId type, used to identify the ResumeIdentity type corresponding to the resolution rule, is divided into two types: fullI-RNTI or shortI-RNTI;

[0012] The starting position of the gNBID is used to indicate the bit position of the gNBID from left to right in the ResumeIdentity identifier;

[0013] gNBID length: indicates the bit length of the gNBID in the ResumeIdentity identifier;

[0014] PLMN starting position: indicates the BIT position of PLMN from left to right in ResumeIdentity;

[0015] PLMN length: indicates the BIT length of the PLMN in the ResumeIdentity identifier.

[0016] Furthermore, when the gNB of a different manufacturer receives a Resume request from a user terminal UE, the ResumeIdentity resolution rule table that matches the adjacent gNB is found to include:

[0017] When a gNB of a different vendor receives a ResumeRequest or ResumeRequest1 message initiated by a UE, if the ResumeIdentity type carried in the message is shortI-RNTI, it obtains the resolution rule table for all ResumeId types with shortI-RNTI in the resolution rule table. Otherwise, it obtains the resolution rule table for ResumeIdentity types with fullI-RNTI in the resolution table.

[0018] Use all the rules in the obtained ResumeIdentity resolution rule table to match them with adjacent gNBs one by one until a match is successful.

[0019] Furthermore, the rules in all the obtained ResumeIdentity resolution rule tables are matched one by one with the neighboring gNBs, including:

[0020] Obtain the gNBID Index information based on the gNBID starting position and gNBID length N configured in the ResumeIdentity resolution rule table.

[0021] Determine whether the lower N bits of the adjacent gNBID are exactly equal to the gNBID Index. If they are exactly equal,

[0022] Indicates that the current rule can successfully match the adjacent gNB. Otherwise, the system continues to determine whether the next rule in the ResumeIdentity resolution rule table can successfully match the adjacent gNB.

[0023] Furthermore, when the gNB of a different vendor finds a ResumeIdentity resolution rule table that matches the adjacent gNB, it obtains the PLMN information based on the PLMN start position and PLMN length configured in the ResumeIdentity rule table.

[0024] The present invention provides a method for parsing ResumeIdentity in a heterogeneous networking scenario, which has the following beneficial effects:

[0025] The present invention configures ResumeIdentity parsing rules for gNBs from different vendors in the ResumeIdentity parsing rule table, specifying the ResumeIdentity type, gNBID starting position, gNBID length, PLMN starting position, and PLMN length. gNBs from different vendors can use the ResumeIdentity parsing rules to parse the ResumeIdentity sent by the UE. This solves the problem in the prior art where the fullI-RNTI and shortI-RNTI identifiers consist of a UE identifier, a gNBID, and a partial bit of the PLMN identifier, with the length of each component customized by the base station vendor. Therefore, in a multi-vendor networking scenario, a base station receiving a Resume request cannot learn the fullI-RNTI and shortI-RNTI composition rules. Parsing according to the local composition rules results in gNBID parsing errors, resulting in an inability to obtain the UE context from the last serving gNB, leading to Resume failure and UE call drops. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] To more clearly illustrate the embodiments of the present invention and its design, the following briefly introduces the drawings required for this embodiment. The drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be derived from these drawings without inventive effort.

[0027] Figure 1 This is a flow chart of a ResumeIdentity parsing method for a cross-vendor networking scenario according to the present invention;

[0028] Figure 2 This is a schematic diagram of the configuration parsing rules of the present invention. DETAILED DESCRIPTION

[0029] In order to enable those skilled in the art to better understand the technical solution of the present invention and to be able to implement it, the present invention is described in detail below with reference to the accompanying drawings and specific embodiments. The following embodiments are only used to more clearly illustrate the technical solution of the present invention and are not intended to limit the scope of protection of the present invention.

[0030] Example:

[0031] The present invention provides a method for parsing ResumeIdentity in a heterogeneous networking scenario, specifically Figure 1As shown, it includes: configuring multiple ResumeIdentity resolution rule tables in the 5G base station gNB of a different manufacturer, setting resolution rules for different types of ResumeIdentity identifiers in each ResumeIdentity resolution rule table; when the gNB of a different manufacturer receives a Resume request sent by a user terminal UE, it finds the ResumeIdentity resolution rule table that can match the adjacent gNB, and uses the resolution rules in the ResumeIdentity resolution rule table to resolve the Resume request sent by the UE.

[0032] The following are specific embodiments of the present invention:

[0033] Step 1: Configure the ResumeIdentity resolution rule table

[0034] In a cross-vendor networking scenario, gNBs can configure the ResumeIdentity resolution rule table through the O&M. The resolution rule consists of the following items:

[0035] 1) Rule ID: The unique index value of the parsing rule, unique throughout the entire site;

[0036] 2) ResumeId type: The ResumeIdentity type corresponding to the identity resolution rule, which is divided into two types: fullI-RNTI and shortI-RNTI;

[0037] 3) gNBID starting position: indicates the bit position of the gNBID from left to right in ResumeIdentity;

[0038] 4) gNBID length: indicates the length of the bit occupied by the gNBID in ResumeIdentity;

[0039] 5) PLMN starting position: indicates the BIT position of PLMN from left to right in ResumeIdentity;

[0040] 6) PLMN length: indicates the BIT length of PLMN in ResumeIdentity;

[0041] Multiple parsing rules can be configured in the parsing rule table. An example of a parsing rule table is shown in Table 1. When multiple parsing rules are configured, the gNB attempts to perform parsing on each rule.

[0042] Table 1 ResumeIdentity parsing rules

[0043]

[0044] Step 2: Get the corresponding parsing rules based on the ResumeIdentity type

[0045] Upon receiving the ResumeRequest or ResumeRequest1 message initiated by the UE, the gNB determines that if the ResumeIdentity type carried in the received message is shortI-RNTI, it retrieves all resolution rules with a resolution type of full from the resolution rule table; otherwise, it retrieves all resolution rules with a resolution type of short from the resolution rule table.

[0046] Step 3: Parse gNBID and PLMN according to the parsing rules

[0047] After the gNB obtains the ResumeIdentity resolution rule, it performs the following resolution:

[0048] 1) Obtain gNBID Index information based on the gNBID starting position and gNBID length configured in the rule;

[0049] 2) Obtain PLMN information based on the PLMN starting position and PLMN length configured in the rule;

[0050] 3) Match all neighboring gNBIDs based on the obtained gNBID Index. Match according to the gNBID length configured in the rule. For example, if the length is 20, the lower 20 bits of the matching neighboring gNBID must be exactly equal to the gNBID Index.

[0051] 4) If the current rule successfully matches the adjacent gNB, the parsing is complete; otherwise, the next rule is processed.

[0052] After the gNBID and PLMN are resolved, the Retrieve UE Context message is forwarded to the matching adjacent gNB based on the service logic to obtain the UE context.

[0053] The above-described embodiments are only preferred specific implementation methods of the present invention, and the protection scope of the present invention is not limited thereto. Any simple changes or equivalent replacements of the technical solutions that can be obviously obtained by any technician familiar with the field within the technical scope disclosed in the present invention fall within the protection scope of the present invention.

Claims

1. A method for parsing ResumeIdentity in a heterogeneous vendor networking scenario, characterized in that: include: Configure multiple ResumeIdentity resolution rule tables in the 5G base station gNB of a different manufacturer, and set resolution rules for different types of ResumeIdentity identifiers in each ResumeIdentity resolution rule table; When a gNB of a different vendor receives a Resume request from a UE, it finds a ResumeIdentity resolution rule table that matches the adjacent gNB and uses the resolution rules in the ResumeIdentity resolution rule table to resolve the Resume request from the UE. The parsing rules of the ResumeIdentity parsing rule table include: Rule ID, used as the number of the ResumeIdentity resolution rule table in the base station; ResumeId type, used to identify the ResumeIdentity type corresponding to the resolution rule, is divided into two types: fullI-RNTI or shortI-RNTI; The starting position of the gNBID is used to indicate the bit position of the gNBID from left to right in the ResumeIdentity identifier; gNBID length: indicates the bit length of the gNBID in the ResumeIdentity identifier; PLMN starting position: indicates the BIT position of PLMN from left to right in ResumeIdentity; PLMN length: indicates the BIT length of the PLMN in the ResumeIdentity identifier.

2. The method for parsing ResumeIdentity in a heterogeneous vendor networking scenario according to claim 1, characterized in that: When a gNB of a different vendor receives a Resume request from a user terminal UE, it finds a ResumeIdentity resolution rule table that matches the adjacent gNB, including: When a gNB of a different vendor receives a ResumeRequest or ResumeRequest1 message initiated by a UE, if the ResumeIdentity type carried in the message is shortI-RNTI, it obtains the resolution rule table for all ResumeId types with shortI-RNTI in the resolution rule table. Otherwise, it obtains the resolution rule table for ResumeIdentity types with fullI-RNTI in the resolution table. Use all the rules in the obtained ResumeIdentity resolution rule table to match them with adjacent gNBs one by one until a match is successful.

3. The method for parsing ResumeIdentity in a heterogeneous vendor networking scenario according to claim 2, characterized in that: The rules in the obtained ResumeIdentity resolution rule table are matched one by one with the neighboring gNBs, including: Obtain gNBIDIndex information based on the gNBID starting position and gNBID length N configured in the ResumeIdentity resolution rule table; Determine whether the lower N bits of the adjacent gNBID are exactly equal to the gNBID Index. If they are exactly equal, Indicates that the current rule can successfully match the adjacent gNB. Otherwise, the system continues to determine whether the next rule in the ResumeIdentity resolution rule table can successfully match the adjacent gNB.

4. The method for parsing ResumeIdentity in a heterogeneous vendor networking scenario according to claim 1, characterized in that: When the gNB of a different vendor finds a ResumeIdentity resolution rule table that matches the adjacent gNB, it obtains the PLMN information based on the PLMN start position and PLMN length configured in the ResumeIdentity rule table.

Images