CN116506891A - URSP information transmission method, device and storage medium - Google Patents

Abstract

The disclosure relates to a method, a device and a storage medium for transmitting URSP information. The URSP information transmission method is applied to core network equipment and comprises the following steps: responding to the URSP information with the size larger than a target threshold value, and performing slicing processing on the URSP information to obtain URSP slicing information; and sending the URSP slicing information. The core network equipment can send URSP information with any information size through the method and the device.

Description

URSP information transmission method, device and storage medium

Technical Field

The disclosure relates to the field of communication technologies, and in particular, to a method and device for transmitting urs information, and a storage medium.

Background

With the development of scientific technology, communication technology is well known as a common information interaction technology, and also has wide application prospects in various scenes of daily life.

In the related art, a core network device, such as a policy control function (Policy Control Function, PCF) device, may send User terminal routing policy (User Routing Select Policy, urs p) information to a User Equipment (UE). However, in the related art, the core network device has a problem that the prsp information with a large information size cannot be transmitted.

Disclosure of Invention

In order to overcome the problems in the related art, the present disclosure provides a method, an apparatus, and a storage medium for transmitting urs information.

According to a first aspect of an embodiment of the present disclosure, there is provided a method for transmitting user terminal routing policy urs p information, applied to a core network device, including:

responding to the URSP information with the size larger than a target threshold value, and performing slicing processing on the URSP information to obtain URSP slicing information; and sending the URSP slicing information.

In one embodiment, the target threshold is a maximum value of a downlink non-access stratum NAS transport message size carrying the urs information.

In one embodiment, the slicing processing for the urs p information includes: and dividing the URSP information into a plurality of URSP fragments by taking the target threshold as a maximum limit, wherein the size of each URSP fragment is smaller than or equal to the target threshold.

In one embodiment, the sending the urs p shard information includes: and sending a first identification for identifying the currently transmitted URSP slicing information.

In one embodiment, the method further comprises: and transmitting a second identifier in response to the completion of the transmission of the last URSP fragment information, wherein the second identifier is used for identifying that all the URSP fragment information of the URSP information is completely transmitted.

In one embodiment, the sending the urs p shard information includes: and transmitting the URSP fragmentation information through a reserved field carrying terminal strategy information in a terminal strategy part management list.

In one embodiment, the method further comprises: and receiving a terminal management policy rejection instruction sent by the terminal, and stopping sending the URSP fragmentation information.

According to a second aspect of the embodiments of the present disclosure, there is provided a transmission method of a user terminal routing policy urs p information, applied to a terminal, including:

receiving URSP slicing information sent by core network equipment, wherein the URSP slicing information is obtained by slicing processing of the core network equipment when the size of the URSP information is larger than a target threshold; and recombining the received URSP fragment information to obtain the URSP information.

In one embodiment, the target threshold is a maximum value of a downlink non-access stratum NAS transport message size carrying the urs information.

In one embodiment, the size of the urs p slice information is less than or equal to the target threshold.

In one embodiment, the receiving the urs p fragmentation information sent by the core network device includes: a first identification identifying currently transmitted urs p shard information is received.

In one embodiment, the method further comprises: and starting a timer in response to the first identification received for the first time, and continuing to receive the first identification of the follow-up URSP slicing information within the duration of the timer.

In one embodiment, the method further comprises: and stopping the timer in response to receiving a second identification, wherein the second identification is used for identifying that all URSP fragment information of the URSP information is completely transmitted.

In one embodiment, the method further comprises: and responding to the timeout of the timer, and sending a terminal management policy reject instruction to the core network equipment.

In one embodiment, the receiving the urs p fragmentation information sent by the core network device includes: and receiving the URSP slicing information through a reserved field carrying terminal strategy information in a terminal strategy part management list.

According to a third aspect of the embodiments of the present disclosure, there is provided a transmission apparatus of a user terminal routing policy urs p information, applied to a core network device, including:

the processing unit is used for responding to the URSP information that the size is larger than the target threshold value and performing slicing processing on the URSP information to obtain URSP slicing information; and the sending unit is used for sending the URSP slicing information.

In one embodiment, the target threshold is a maximum value of a downlink non-access stratum NAS transport message size carrying the urs information.

In one embodiment, the processing unit performs slicing processing on the urs p information in the following manner: and dividing the URSP information into a plurality of URSP fragments by taking the target threshold as a maximum limit, wherein the size of each URSP fragment is smaller than or equal to the target threshold.

In one embodiment, the transmitting unit transmits the urs p slice information in the following manner: and sending a first identification for identifying the currently transmitted URSP slicing information.

In one embodiment, the transmitting unit is further configured to: and transmitting a second identifier in response to the completion of the transmission of the last URSP fragment information, wherein the second identifier is used for identifying that all the URSP fragment information of the URSP information is completely transmitted.

In one embodiment, the transmitting unit transmits the urs p slice information in the following manner: and transmitting the URSP fragmentation information through a reserved field carrying terminal strategy information in a terminal strategy part management list.

In one embodiment, the apparatus further comprises: and the receiving unit is used for receiving a terminal management policy rejection instruction sent by the terminal and stopping sending the URSP fragmentation information.

According to a fourth aspect of the embodiments of the present disclosure, there is provided a transmission apparatus of a user terminal routing policy urs p information, applied to a terminal, including:

the receiving unit is used for receiving the URSP slicing information sent by the core network equipment, wherein the URSP slicing information is obtained by slicing processing of the core network equipment when the size of the URSP information is larger than a target threshold value; and the processing unit is used for recombining the received URSP fragment information to obtain the URSP information.

In one embodiment, the target threshold is a maximum value of a downlink non-access stratum NAS transport message size carrying the urs information.

In one embodiment, the size of the urs p slice information is less than or equal to the target threshold.

In one embodiment, the receiving unit receives the urs p slice information sent by the core network device in the following manner: a first identification identifying currently transmitted urs p shard information is received.

In one embodiment, the processing unit is further configured to, in response to receiving the first identifier for the first time, start a timer, and continue to receive the first identifier of the subsequent urs p fragment information for the duration of the timer.

In one embodiment, the processing unit is further configured to: and stopping the timer in response to receiving a second identification, wherein the second identification is used for identifying that all URSP fragment information of the URSP information is completely transmitted.

In one embodiment, the processing unit is further configured to: and responding to the timeout of the timer, and sending a terminal management policy reject instruction to the core network equipment.

In one embodiment, the receiving unit receives the urs p slice information sent by the core network device in the following manner: and receiving the URSP slicing information through a reserved field carrying terminal strategy information in a terminal strategy part management list.

According to a fifth aspect of the embodiments of the present disclosure, there is provided a transmission apparatus for user terminal routing policy urs p information, including:

a processor; a memory for storing processor-executable instructions;

wherein the processor is configured to: the transmission method of the user terminal routing policy urs p information described in the first aspect or any implementation manner of the first aspect is performed, or the transmission method of the user terminal routing policy urs p information described in the second aspect or any implementation manner of the second aspect is performed.

According to a sixth aspect of the disclosed embodiments, there is provided a storage medium having instructions stored therein, which when executed by a processor, enable the processor to perform the method for transmitting the user terminal routing policy urs p information described in the first aspect or any one of the embodiments of the first aspect, or perform the method for transmitting the user terminal routing policy urs p information described in the second aspect or any one of the embodiments of the second aspect.

The technical scheme provided by the embodiment of the disclosure can comprise the following beneficial effects: and aiming at the situation that the core network equipment cannot send the URSP information (namely, the size of the URSP information is larger than a target threshold value), carrying out slicing processing on the URSP information to obtain the URSP slicing information. Because the information size of each URSP fragment information is smaller than the URSP information before the fragment processing, the mode of processing the URSP information with the information size larger than the target threshold value into the URSP fragment information can meet the information sending requirement of core network equipment, so that the core network equipment can realize the transmission of the URSP information with the information size larger than the target threshold value.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure.

Fig. 1 is a flowchart illustrating a method of transmitting urs information according to an exemplary embodiment.

Fig. 2 is a flowchart illustrating another method of transmitting urs information according to an exemplary embodiment.

Fig. 3 is a flowchart illustrating yet another method of transmitting urs information according to an exemplary embodiment.

Fig. 4 is a flowchart illustrating another method of transmitting urs information according to an exemplary embodiment.

Fig. 5 is a flowchart illustrating yet another method of transmitting urs information according to an exemplary embodiment.

Fig. 6 is a flowchart illustrating another method of transmitting urs information according to an exemplary embodiment.

Fig. 7 is a flowchart illustrating yet another method of transmitting urs information according to an exemplary embodiment.

Fig. 8 is a flowchart illustrating another method of transmitting urs information according to an exemplary embodiment.

Fig. 9 is a flowchart illustrating yet another method of transmitting urs information according to an exemplary embodiment.

Fig. 10 is a flowchart illustrating another method of transmitting urs information according to an exemplary embodiment.

Fig. 11 is a block diagram of a transmission apparatus of urs information according to an exemplary embodiment.

FIG. 12 is a block diagram of another URSP information transmitting device according to an exemplary embodiment

Fig. 13 is a block diagram of a further transmission apparatus of urs information, according to an exemplary embodiment.

Fig. 14 is a block diagram illustrating an apparatus for transmission of urs information according to an exemplary embodiment.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure.

In the drawings, the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The described embodiments are some, but not all, embodiments of the present disclosure. The embodiments described below by referring to the drawings are exemplary and intended for the purpose of explaining the present disclosure and are not to be construed as limiting the present disclosure. Based on the embodiments in this disclosure, all other embodiments that a person of ordinary skill in the art would obtain without making any inventive effort are within the scope of protection of this disclosure. Embodiments of the present disclosure are described in detail below with reference to the attached drawings.

The URSP information transmission method provided by the embodiment of the disclosure can be applied to information interaction scenes between core network equipment and terminals. For example, the method can be applied to an information transmission scene that the core network transmits the URSP information to the terminal.

The PCF and urs are briefly summarized below for ease of understanding:

PCF: for helping operators easily create and seamlessly deploy policies in 5G networks. The PCF is associated with the 3gpp 5g architecture, typically as a unified policy framework supporting management of network behavior, and provides policy rules for management of network behavior through control interface functions. And, to make it more convenient, the PCF will typically collect relevant subscription information through the unified data management function device.

Urs p: the urs information describes the correspondence between applications (apps) and network slices for the rules defined by the 3gpp 5g protocol. The terminal operating system needs to select a network slice for the App according to the urs p information. There are two important sets of parameters in the urs p information, one set is a path Descriptor (Traffic Descriptor) parameter describing App attributes, including parameters such as AppId, data network name (DataNetworkName, DNN), IP triplet (IP Descriptor), domain name Descriptor (Domain Descriptor), and association capability (Connection Capabilities). Another group is a routing descriptor (Route Selection Descriptor) describing data bearer attributes, including parameters such as network cut-off (S-nsai), session and service continuity Mode (SSC Mode), DNN, etc. The URSP information characterizes the corresponding relation between a plurality of groups of access descriptors and routing descriptors, and after the terminal knows the access descriptor parameters related to the App, the routing descriptors related to the data bearing, including the network slice information, can be searched according to the URSP information. Based on this, the terminal can learn the network slice that needs to be accessed and execute the subsequent procedure.

In the related art, a core network device such as PCF may use information such as a downlink non-access stratum transport (Down Link Non Access Stratum transport, DL NAS transport) message as an information carrier to transmit urs information to a terminal. In the related art, since the size of information that can be carried by carrier information as a carrier is limited, the core network device cannot transmit USRP information whose information size exceeds the maximum carrying capacity of the carrier information, and this method has a problem that it cannot cover all the urs p information transmission scenarios.

The embodiment of the disclosure provides a method for transmitting URSP information applied to core network equipment, which can perform slicing processing on URSP information to obtain URSP slicing information aiming at the condition that the information size of the URSP information exceeds the maximum bearing capacity of carrier information (namely, the size of the URSP information is larger than a target threshold). Because the size of the information contained in each urs slice information is smaller than that of the complete urs information, the core network can implement sending the urs information with larger information size by sending the urs information, and thus implement the complete coverage of the urs information transmission scene.

Fig. 1 is a flowchart illustrating a method of transmitting urs information according to an exemplary embodiment, which is used for a core network device, as shown in fig. 1, and includes the following steps.

In step S11, when the size of the urs p information is greater than the target threshold, the urs p information is subjected to slicing processing to obtain urs p slicing information.

In the embodiment of the disclosure, the target threshold may be set according to the actual performance of the core network device. For example, according to the information sizes of a plurality of urs information that the core network device cannot send currently, a corresponding target threshold is set.

For example, the urs p information with information size less than or equal to the target threshold may be directly transmitted by the core network device.

In step S12, urs p slice information is transmitted.

The method for transmitting the URSP information can directly transmit the URSP information with the information size smaller than or equal to the target threshold value, and transmit the URSP information with the information size larger than the target threshold value after being segmented.

In the embodiment of the present disclosure, the corresponding target threshold may be set according to carrier information carrying the urs p information. For example, if the bearer information carrying the urs information is a downlink non-access stratum transmission message, the target threshold may be set to be the maximum value of the downlink non-access stratum transmission message size.

Fig. 2 is a flowchart of another method for transmitting urs information according to an exemplary embodiment, and as shown in fig. 2, step S22 of the embodiment of the present disclosure is similar to the implementation process of step S12 in fig. 1, and will not be described herein.

In step S21, when the size of the urs information is greater than the maximum value of the downlink non-access stratum transmission message, the urs information is fragmented, so as to obtain urs fragmentation information.

The purpose of setting the target threshold is to divide the urs information into a plurality of urs information whose information size is smaller than the target threshold. For example, the urs information may be fragmented with a target threshold as a maximum limit.

Fig. 3 is a flowchart of yet another method for transmitting urs information according to an exemplary embodiment, and as shown in fig. 3, step S32 of the embodiment of the present disclosure is similar to the implementation process of step S12 in fig. 1, and will not be described herein.

In step S31, when the urs information size is larger than the target threshold, the urs information is divided into a plurality of urs slices with the target threshold as the maximum limit.

Wherein the size of each urs slice is less than or equal to the target threshold.

According to the URSP information transmission method provided by the embodiment of the disclosure, the URSP information can be subjected to slicing processing in a mode that the target threshold is taken as the maximum limit. The method can control the number of the fragments of the URSP fragments to be as small as possible, so that the core network equipment can transmit the URSP information with fewer transmission times while the core network equipment can transmit the URSP information, and further the transmission efficiency of the core network equipment for transmitting the URSP information is guaranteed.

For example, since the terminal side needs to integrate the urs slice information into the urs information when receiving all the urs information, the core network device needs to send a corresponding hint identifier in addition to the urs information, so that the terminal side knows that the core network device has sent all the urs slice information.

In an embodiment, in a case that the core network device needs to send the urs slice information, an identifier for identifying that sending all the urs slice information is not completed currently may be sent through the core network device. Further, an identifier for identifying that all the urs slice information has been transmitted to completion may be transmitted in the case that the last urs slice information is completed. For convenience of description, an identification for identifying that all the urs slice information of the urs information has not been completely transmitted is referred to as a first identification, and an identification for identifying that all the urs slice information of the urs information has been completely transmitted is referred to as a second identification.

Fig. 4 is a flowchart of another method for transmitting urs information according to an exemplary embodiment, and as shown in fig. 4, step S41 of the embodiment of the present disclosure is similar to the implementation process of step S11 in fig. 1, and will not be described herein.

In step S42, a first identifier is sent that identifies the currently transmitted urs slice information, and a second identifier is sent if the transmission of the last urs slice information is completed.

In the embodiment of the disclosure, the terminal side may receive the first identifier sent by the core network device, and receive the second identifier sent by the core network device when all the first identifiers are received. And under the condition that the terminal receives the second identifier, the terminal can acquire that all URSP fragment information of the URSP information is completely transmitted, and further integrates all the received URSP fragment information to obtain the URSP information.

For example, for carrying terminal policy information (UE policy part) in the terminal policy part management list (UE policy section management list), the urs fragmentation information may be sent using its reserved (spark) field.

Fig. 5 is a flowchart of yet another method for transmitting urs information according to an exemplary embodiment, and as shown in fig. 5, step S51 of the embodiment of the present disclosure is similar to the implementation process of step S11 in fig. 1, and will not be described herein.

In step S52, the urs p fragment information is sent through the reserved field carrying the terminal policy information in the terminal policy part management list.

In an embodiment, for the manner of sending the urs fragmentation information with the first identifier and the second identifier, the first identifier and the second identifier may be directly set in the reserved field carrying the terminal policy information in the terminal policy part management list

Fig. 6 is a flowchart of another method for transmitting urs information according to an exemplary embodiment, and as shown in fig. 6, step S61 of the embodiment of the present disclosure is similar to the implementation process of step S11 in fig. 1, and will not be described herein.

In step S62, the first identifier for identifying the currently transmitted urs partition information is sent through the reserved field for carrying the terminal policy information in the terminal policy part management list, and the second identifier is sent through the reserved field for carrying the terminal policy information in the terminal policy part management list when the transmission of the last urs partition information is completed.

The method uses the characteristic that the core network equipment sends the terminal strategy information in the information transmission link, selects the reserved field which is not used by the terminal strategy information and bears the first identifier and the second identifier, and can not additionally increase the information transmission quantity of the core network equipment, thereby meeting the information transmission requirement.

For example, in a scenario in which the core network device sends the urs slice information to the terminal, there may be a case in which the terminal cannot receive all the urs slice information due to an error of the core network device or the terminal. In view of the foregoing, in an embodiment of the disclosure, a terminal management policy reject instruction may be sent by a terminal to a core network device (Manage UE Policy CommandReject). Further, the core network device may stop sending the urs p fragmentation information when receiving a terminal management policy reject instruction sent by the terminal.

Fig. 7 is a flowchart of yet another method for transmitting urs information according to an exemplary embodiment, and as shown in fig. 7, step S71 and step S72 of the embodiment of the present disclosure are similar to the implementation process of step S11 and step S12 in fig. 1, and are not described herein.

In step S73, a terminal management policy reject instruction sent by the terminal is received, and the sending of the urs p slice information is stopped.

According to the URSP information transmission method provided by the embodiment of the disclosure, the core network equipment can timely acquire the current state of the terminal by receiving the terminal management policy rejection instruction, and make corresponding adjustment.

Based on the same conception, the embodiment of the disclosure also provides a transmission method of the URSP information applied to the terminal, and for the case that the size of the URSP information is larger than the target threshold, the URSP fragmentation information obtained by carrying out fragmentation processing on the URSP information by the core network equipment can be received by the terminal. Furthermore, the received URSP fragment information can be recombined to obtain URSP information with the information size larger than the target threshold value, and the method can enable the terminal to realize the URSP information with the information size larger than the target threshold value, so that the complete coverage of the URSP information transmission scene is realized.

Fig. 8 is a flowchart illustrating another method for transmitting urs information according to an exemplary embodiment, which is applied to a terminal as shown in fig. 8, including the following steps.

In step S81, the urs slice information sent by the core network device is received.

In the embodiment of the disclosure, the urs slicing information received by the terminal is obtained by performing slicing processing on the core network device when the urs information is greater than a target threshold.

In step S82, the urs information is obtained by reorganizing the received urs slice information.

Of course, the terminal side may receive not only the urs p slice information, but also the urs p information whose information size is smaller than or equal to the target threshold. The process of receiving the urs information with the information size smaller than or equal to the target threshold by the terminal is similar to the implementation process in the prior art, and will not be described herein.

In the embodiment of the disclosure, the target threshold may be set according to carrier information carrying the urs p information. For example, if the bearer information carrying the urs information is a downlink non-access stratum transmission message, the target threshold may be set to be the maximum value of the downlink non-access stratum transmission message size.

In addition, for example, since the core network device may set a maximum limit with the target threshold, the burst processing is performed on the urs p information, so as to obtain urs p burst information with an information size smaller than or equal to the target threshold. Therefore, the size of the urs p slice information received by the terminal is less than or equal to the target threshold.

In an embodiment, the terminal may receive the urs p slice information sent by the core network device by receiving the first identifier.

Fig. 9 is a flowchart of yet another method for transmitting urs information according to an exemplary embodiment, and as shown in fig. 9, step S92 of the embodiment of the present disclosure is similar to the implementation process of step S82 in fig. 8, and will not be described herein.

In step S91, a first identification identifying the currently transmitted urs p fragment information is received.

In the embodiment of the disclosure, since the first identifier is used for identifying that all the urs slice information of the urs slice information is not completely transmitted, the second identifier is used for identifying that all the urs slice information of the urs slice information is completely transmitted. Thus, for example, a timer may be started when the first identifier is received for the first time, so that the terminal may monitor whether the received urs information is timed out by the timer and respond according to the actual situation.

In an embodiment, all the urs p fragment information of the urs p information may be determined to be received in case that the second identification is received. In this case, the timer may be stopped, and the information reorganization process may be performed with the received urs p slice information to obtain urs p information.

In another embodiment, when the terminal has not received the second identifier and the timer expires, the terminal may stop receiving the urs p slice information, and send a terminal management policy reject instruction to the core network device, so that the core network device stops transmitting the urs p slice information.

Fig. 10 is a flowchart of another method for transmitting urs information according to an exemplary embodiment, and as shown in fig. 10, step S103 of the embodiment of the present disclosure is similar to the implementation process of step S82 in fig. 8, and will not be described herein.

In step S101, in the case that the first identifier is received for the first time, a timer is started, and the first identifier of the subsequent urs p fragment information is continuously received for the duration of the timer.

In step S102a, in the case where the second flag is received, the timer is stopped.

In step S102b, if the timer expires, a terminal management policy reject instruction is sent to the core network device.

In an example, a timer for determining whether the length required for the terminal to receive the second identification is too long may be directly set. For example, the timer of the duration a may be directly set, and the timer may be started when the terminal receives the first identifier for the first time. Further, it may be determined that the length of time required for the terminal to receive the second identifier is too long in case of timeout of the timer, the urs p fragmentation information receiving process is terminated, and a terminal management policy reject instruction is sent to the core network device.

In another example, a timer for determining whether the time interval for which the terminal receives the first identification is too long may be set. For example, a timer of duration B may be set and started if the first identification is received for the first time. Further, the timer may be updated under the condition that the terminal receives the next first identifier, and the duration of the timer is recovered to be the duration of B. If the timer is overtime on the basis, the time interval for the terminal to receive the first identifier is determined to be too long, then the receiving process of the URSP fragmentation information is terminated, and a terminal management strategy reject instruction is sent to the core network equipment.

In the embodiment of the disclosure, corresponding to a core network device side, for the case that the core network device sends the urs p slicing information through a reserved field carrying terminal policy information in a terminal policy part management list, the terminal may receive the urs p slicing information through the reserved field carrying terminal policy information in the terminal policy part management list.

Illustratively, the reserved field of the terminal policy information includes a blank bit (illustratively represented as 0000) of a four-bit binary code. In an embodiment, a corresponding first identifier or second identifier may be set for the reserved field. For example, 0001 is set as the first identifier corresponding to the first piece of urs slice information, 0010 is set as the first identifier corresponding to the second piece of urs slice information, and so on, until 1110 is set as the first identifier corresponding to the fifteenth piece of slice information. For another example, 1111 is set to the second flag.

In the embodiment of the disclosure, the number of fragments is set according to a size relationship between the information size of the urs information and the target threshold. For example, for the case where the information size of the urs information is greater than the target threshold and less than the double target threshold, the urs information may be divided into two urs slice information. Wherein the first piece of urs p slice information corresponds to a first identification of 0001, and the information size is equal to a target threshold. The second piece of urs p slice information corresponds to the first identification of 0010, and the information size is less than the target threshold.

For example, the terminal may read the payload container type (Payload container type) in the downlink non-access stratum transmission message sent by the core network device side, so as to determine whether the terminal policy (UE policy) is included therein. Further, under the condition that the terminal policy is read, the terminal policy delivery service message type (UE policy delivery service message type) can be searched in the terminal policy, whether the terminal policy delivery service message type comprises a terminal management policy instruction or not is judged (Manage UE Policy Command), and further, whether the terminal policy information type is URSP information or not is further judged under the condition that the terminal policy instruction is determined to be included.

For the above case, if it is determined that the terminal policy information type is the urs p information, the reserved field of the terminal policy information may be further read.

For example, if the reserved field is an initial blank bit (denoted 0000 in the example), the urs p information received by the terminal may be determined to be complete information with an information size less than or equal to the target threshold. If the reserved field is the first identifier (e.g., any one of 0001-1110), it may be determined that the urs p information received by the terminal is urs p slice information, i.e., the terminal has not currently acquired complete urs p information. In this case, before the timer expires, the terminal may further wait for the core network device to send the remaining urs p fragmentation information, and further end receiving and integrating the received urs p fragmentation information to obtain the urs p information when obtaining that the reserved field is the second identifier (denoted by 1111 in the example). Or stopping receiving the URSP fragmentation information and sending a terminal management strategy reject instruction to the core network equipment under the condition that the timer is overtime.

Based on the same conception, the embodiment of the disclosure also provides a transmission device of the URSP information applied to the core network equipment.

It can be understood that, in order to implement the above-mentioned functions, the transmission device for the urs information provided in the embodiments of the present disclosure includes a hardware structure and/or a software module that perform each function. The disclosed embodiments may be implemented in hardware or a combination of hardware and computer software, in combination with the various example elements and algorithm steps disclosed in the embodiments of the disclosure. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Those skilled in the art may implement the described functionality using different approaches for each particular application, but such implementation is not to be considered as beyond the scope of the embodiments of the present disclosure.

Fig. 11 is a block diagram of a transmission apparatus of urs information according to an exemplary embodiment. Referring to fig. 11, the apparatus 100 is applied to a core network device, and includes a processing unit 101 and a transmitting unit 102.

The processing unit 101 performs slicing processing on the urs information in response to the urs information being greater than the target threshold, to obtain urs slicing information. A transmitting unit 102, configured to transmit the urs slice information.

In one embodiment, the target threshold is the maximum value of the downlink non-access stratum NAS transport message size carrying the urs information.

In one embodiment, the processing unit 101 performs slicing processing on the urs information in the following manner: and dividing the URSP information into a plurality of URSP fragments by taking the target threshold value as the maximum limit, wherein the size of each URSP fragment is smaller than or equal to the target threshold value.

In one embodiment, the transmitting unit 102 transmits the urs fragmentation information in the following manner: and sending a first identification for identifying the currently transmitted URSP slicing information.

In one embodiment, the sending unit 102 is further configured to: and transmitting a second identifier in response to the completion of the transmission of the last URSP slicing information, wherein the second identifier is used for identifying that all URSP slicing information of the URSP information is completely transmitted.

In one embodiment, the transmitting unit 102 transmits the urs fragmentation information in the following manner: and sending the URSP fragmentation information through a reserved field carrying the terminal strategy information in the terminal strategy part management list.

In one embodiment, the apparatus further comprises: a receiving unit 103.

Fig. 12 is a block diagram of another apparatus for transmitting urs information according to an exemplary embodiment, and referring to fig. 12, the apparatus includes a processing unit 101, a transmitting unit 102, and a receiving unit 103.

And the receiving unit 103 is configured to receive a terminal management policy reject instruction sent by the terminal, and stop sending the urs p slice information.

Based on the same conception, the embodiment of the disclosure also provides a transmission device of the URSP information applied to the terminal.

Fig. 13 is a block diagram of a further transmission apparatus of urs information, according to an exemplary embodiment. Referring to fig. 13, the apparatus 200 is applied to a terminal, and includes a receiving unit 201 and a processing unit 202.

And the receiving unit 201 is configured to receive the urs slice information sent by the core network device, where the urs slice information is obtained by performing a slice processing on the core network device when the urs slice information is greater than a target threshold. The processing unit 202 obtains the urs information by reorganizing the received urs slice information.

In one embodiment, the target threshold is the maximum value of the downlink non-access stratum NAS transport message size carrying the urs information.

In one embodiment, the size of the urs slice information is less than or equal to the target threshold.

In one embodiment, the receiving unit 201 receives the urs p slice information sent by the core network device in the following manner: a first identification identifying currently transmitted urs p shard information is received.

In one embodiment, the processing unit 202 is further configured to, in response to receiving the first identifier for the first time, start a timer and continue to receive the first identifier of the subsequent urs p fragment information for the duration of the timer.

In one embodiment, the processing unit 202 is further configured to: in response to receiving the second identification, the timer is stopped, the second identification identifying that all of the urs p fragment information of the urs p information has been transmitted in its entirety.

In one embodiment, the processing unit 202 is further configured to: and sending a terminal management policy reject instruction to the core network equipment in response to the timeout of the timer.

In one embodiment, the receiving unit 201 receives the urs p slice information sent by the core network device in the following manner: and receiving the URSP fragmentation information through a reserved field carrying the terminal strategy information in the terminal strategy part management list.

The specific manner in which the various modules perform the operations in the apparatus of the above embodiments have been described in detail in connection with the embodiments of the method, and will not be described in detail herein.

Fig. 14 is a block diagram illustrating an apparatus 300 for transmission of urs information, according to an exemplary embodiment. The apparatus 300 may be applied to a core network device or terminal, which may be, for example, a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, an exercise device, a personal digital assistant, etc.

Referring to fig. 14, the apparatus 300 may include one or more of the following components: a processing component 302, a memory 304, a power component 306, a multimedia component 308, an audio component 310, an input/output (I/O) interface 312, a sensor component 314, and a communication component 316.

The processing component 302 generally controls overall operation of the apparatus 300, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 302 may include one or more processors 320 to execute instructions to perform all or part of the steps of the methods described above. Further, the processing component 302 can include one or more modules that facilitate interactions between the processing component 302 and other components. For example, the processing component 302 may include a multimedia module to facilitate interaction between the multimedia component 308 and the processing component 302.

Memory 304 is configured to store various types of data to support operations at apparatus 300. Examples of such data include instructions for any application or method operating on the device 300, contact data, phonebook data, messages, pictures, videos, and the like. The memory 304 may be implemented by any type or combination of volatile or nonvolatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.

The power component 306 provides power to the various components of the device 300. The power components 306 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for the device 300.

The multimedia component 308 includes a screen between the device 300 and the user that provides an output interface. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may sense not only the boundary of a touch or sliding action, but also the duration and pressure associated with the touch or sliding operation. In some embodiments, the multimedia component 308 includes a front-facing camera and/or a rear-facing camera. The front-facing camera and/or the rear-facing camera may receive external multimedia data when the apparatus 300 is in an operational mode, such as a photographing mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

The audio component 310 is configured to output and/or input audio signals. For example, the audio component 310 includes a Microphone (MIC) configured to receive external audio signals when the device 300 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may be further stored in the memory 304 or transmitted via the communication component 316. In some embodiments, audio component 310 further comprises a speaker for outputting audio signals.

The I/O interface 312 provides an interface between the processing component 302 and peripheral interface modules, which may be a keyboard, click wheel, buttons, etc. These buttons may include, but are not limited to: homepage button, volume button, start button, and lock button.

The sensor assembly 314 includes one or more sensors for providing status assessment of various aspects of the apparatus 300. For example, the sensor assembly 314 may detect the on/off state of the device 300, the relative positioning of the components, such as the display and keypad of the device 300, the sensor assembly 314 may also detect a change in position of the device 300 or a component of the device 300, the presence or absence of user contact with the device 300, the orientation or acceleration/deceleration of the device 300, and a change in temperature of the device 300. The sensor assembly 314 may include a proximity sensor configured to detect the presence of nearby objects in the absence of any physical contact. The sensor assembly 314 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 314 may also include an acceleration sensor, a gyroscopic sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

The communication component 316 is configured to facilitate communication between the apparatus 300 and other devices, either wired or wireless. The device 300 may access a wireless network based on a communication standard, such as WiFi,4G or 5G, or a combination thereof. In one exemplary embodiment, the communication component 316 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 316 further includes a Near Field Communication (NFC) module to facilitate short range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, ultra Wideband (UWB) technology, bluetooth (BT) technology, and other technologies.

In an exemplary embodiment, the apparatus 300 may be implemented by one or more Application Specific Integrated Circuits (ASICs), digital Signal Processors (DSPs), digital Signal Processing Devices (DSPDs), programmable Logic Devices (PLDs), field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic elements for executing the methods described above.

In an exemplary embodiment, a non-transitory computer readable storage medium is also provided, such as memory 304, including instructions executable by processor 320 of apparatus 300 to perform the above-described method. For example, the non-transitory computer readable storage medium may be ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.

It is understood that the term "plurality" in this disclosure means two or more, and other adjectives are similar thereto. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship. The singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

It is further understood that the terms "first," "second," and the like are used to describe various information, but such information should not be limited to these terms. These terms are only used to distinguish one type of information from another and do not denote a particular order or importance. Indeed, the expressions "first", "second", etc. may be used entirely interchangeably. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present disclosure.

It will be further understood that "connected" includes both direct connection where no other member is present and indirect connection where other element is present, unless specifically stated otherwise.

It will be further understood that although operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any adaptations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the scope of the appended claims.

Claims (17)

1. A method for transmitting a user terminal routing policy urs p information, which is characterized in that the method is applied to a core network device, the method comprising:

responding to the URSP information with the size larger than a target threshold value, and performing slicing processing on the URSP information to obtain URSP slicing information;

and sending the URSP slicing information.

2. The method of claim 1, wherein the target threshold is a maximum value of a downlink non-access stratum, NAS, transport message size carrying the urs information.

3. The method according to claim 1 or 2, wherein the slicing the urs information comprises:

and dividing the URSP information into a plurality of URSP fragments by taking the target threshold as a maximum limit, wherein the size of each URSP fragment is smaller than or equal to the target threshold.

4. The method of claim 1, wherein the sending the urs p shard information comprises:

and sending a first identification for identifying the currently transmitted URSP slicing information.

5. The method according to claim 4, wherein the method further comprises:

and transmitting a second identifier in response to the completion of the transmission of the last URSP fragment information, wherein the second identifier is used for identifying that all the URSP fragment information of the URSP information is completely transmitted.

6. The method of claim 1, 4 or 5, wherein said transmitting said urs p slicing information comprises:

and transmitting the URSP fragmentation information through a reserved field carrying terminal strategy information in a terminal strategy part management list.

7. The method according to claim 1, wherein the method further comprises:

and receiving a terminal management policy rejection instruction sent by the terminal, and stopping sending the URSP fragmentation information.

8. A method for transmitting a user terminal routing policy urs p information, applied to a terminal, the method comprising:

receiving URSP slicing information sent by core network equipment, wherein the URSP slicing information is obtained by slicing processing of the core network equipment when the size of the URSP information is larger than a target threshold;

and recombining the received URSP fragment information to obtain the URSP information.

9. The method of claim 8, wherein the target threshold is a maximum value of a downlink non-access stratum, NAS, transport message size carrying the urs information.

10. The method according to claim 8 or 9, wherein the size of the urs slice information is less than or equal to the target threshold.

11. The method of claim 8, wherein the receiving the urs p fragmentation information sent by the core network device comprises:

a first identification identifying currently transmitted urs p shard information is received.

12. The method of claim 11, wherein the method further comprises:

and starting a timer in response to the first identification received for the first time, and continuing to receive the first identification of the follow-up URSP slicing information within the duration of the timer.

13. The method according to claim 12, wherein the method further comprises:

and stopping the timer in response to receiving a second identification, wherein the second identification is used for identifying that all URSP fragment information of the URSP information is completely transmitted.

14. The method according to claim 12, wherein the method further comprises:

and responding to the timeout of the timer, and sending a terminal management policy reject instruction to the core network equipment.

15. The method according to claim 8 or 11, wherein the receiving the urs p fragmentation information sent by the core network device comprises:

and receiving the URSP slicing information through a reserved field carrying terminal strategy information in a terminal strategy part management list.

16. A transmission apparatus for a user terminal routing policy urs p information, comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to: transmission method of performing the user terminal routing policy urs p information as claimed in any one of claims 1 to 7 or of performing the user terminal routing policy urs p information as claimed in any one of claims 8 to 15.

17. A storage medium having instructions stored therein, which when executed by a processor, enable the processor to perform the method of transmitting user terminal routing policy, urs, information according to any one of claims 1 to 7 or to perform the method of transmitting user terminal routing policy, urs, information according to any one of claims 8 to 15.