Information indication method and apparatus, and device and storage medium

Abstract

An information indication method and apparatus, and a device and a storage medium, which relate to the technical field of communications. The method is executed by means of a first device. The method comprises: receiving first information sent by a first core network element, wherein the first information is used for indicating at least one tracking area code (TAC) and / or at least one cell identity that a first device is allowed or authorized to broadcast (410). In the method, at least one TAC and / or at least one cell identity that a first device is allowed or authorized to broadcast is indicated to the first device by means of a core network element, and it is not necessary for an operator to manually configure the TAC and / or the cell identity that the first device is allowed or authorized to broadcast, such that the configuration mode of a TAC and a cell identity is more flexible and convenient.

Description

Information indication method, device, equipment and storage medium Technical Field

[0001] The embodiments of the present application relate to the field of communication technology, and in particular to an information indication method, apparatus, device, and storage medium. Background Art

[0002] In communications networks, terminal devices access the core network through access network devices. Different access network devices have different network coverage. In related technologies, OAM (Operation Administration and Maintenance) configuration is commonly used to configure the network coverage of access network devices. However, this method requires operators to perform backend maintenance and configuration of the access network device's network coverage, which prevents flexible configuration of the access network device's network coverage.

[0003] Summary of the Invention

[0004] The embodiments of the present application provide an information indication method, apparatus, device, and storage medium. The technical solution is as follows:

[0005] According to one aspect of an embodiment of the present application, a method for indicating information is provided. The method is performed by a first device, and the method includes:

[0006] Receive first information sent by a first core network network element, where the first information is used to indicate at least one TAC (Tracking Area Code) and / or at least one cell identifier that the first device is allowed or authorized to broadcast.

[0007] According to one aspect of an embodiment of the present application, an information indication method is provided, the method being performed by a first core network element, the method including:

[0008] First information is sent to a first device, where the first information is used to indicate at least one TAC and / or at least one cell identifier that the first device is allowed or authorized to broadcast.

[0009] According to one aspect of an embodiment of the present application, there is provided an information indication device, the device comprising:

[0010] The receiving module is used to receive first information sent by the first core network network element, where the first information is used to indicate at least one TAC and / or at least one cell identifier that the first device is allowed or authorized to broadcast.

[0011] According to one aspect of an embodiment of the present application, there is provided an information indication device, the device comprising:

[0012] The sending module is configured to send first information to a first device, where the first information is used to indicate at least one TAC and / or at least one cell identifier that the first device is allowed or authorized to broadcast.

[0013] The technical solutions provided by the embodiments of the present application may have the following beneficial effects:

[0014] The core network network element indicates to the first device at least one TAC and / or at least one cell identifier that the first device is allowed or authorized to broadcast, without the need for the operator to manually configure the TAC and / or cell identifier that the first device is allowed or authorized to broadcast, making the configuration method of TAC and cell identifier more flexible and convenient. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] FIG1 is a schematic diagram of a network architecture provided by an embodiment of the present application;

[0016] FIG2 is a schematic diagram of a 5G system architecture provided by an embodiment of the present application;

[0017] FIG3 is a schematic diagram of a VMR (Vehicle-Mounted Relay) scenario provided by one embodiment of the present application;

[0018] FIG4 is a flowchart of an information indication method provided by an embodiment of the present application;

[0019] FIG5 is a flowchart of an information indication method provided by another embodiment of the present application;

[0020] FIG6 is a flowchart of an information indication method provided by another embodiment of the present application;

[0021] FIG7 is a flowchart of an information indication method provided by another embodiment of the present application;

[0022] FIG8 is a block diagram of an information indication device provided by one embodiment of the present application;

[0023] FIG9 is a block diagram of an information indication device provided by another embodiment of the present application;

[0024] FIG10 is a schematic structural diagram of a first device provided by an embodiment of the present application;

[0025] FIG11 is a schematic structural diagram of a first core network element provided in an embodiment of the present application. DETAILED DESCRIPTION

[0026] In order to make the objectives, technical solutions and advantages of this application clearer, the implementation methods of this application will be further described in detail below with reference to the accompanying drawings.

[0027] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. A person skilled in the art will appreciate that, with the evolution of the network architecture and the emergence of new business scenarios, the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

[0028] Please refer to FIG1 , which shows a schematic diagram of a network architecture 100 provided by an embodiment of the present application. The network architecture 100 may include: a terminal device 10 , an access network device 20 , and a core network element 30 .

[0029] The terminal device 10 may refer to a UE (User Equipment), a STA (Station), an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a wireless communication device, a user agent, or a user apparatus. In some embodiments, the terminal device 10 may also be a cellular phone, a cordless phone, a SIP (Session Initiation Protocol) phone, a WLL (Wireless Local Loop) station, a PDA (Personal Digital Assistant), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a 5GS (5th Generation System) or a terminal device in a future evolved PLMN (Public Land Mobile Network), etc., and the embodiments of the present application are not limited thereto. For ease of description, the above-mentioned devices are collectively referred to as terminal devices. The number of terminal devices 10 is generally multiple, and one or more terminal devices 10 may be distributed in each cell managed by an access network device 20. The terminal device may also be referred to as a terminal or UE for short, and those skilled in the art will understand its meaning.

[0030] The access network device 20 is a device deployed in the access network to provide wireless communication functions for the terminal device 10. The access network device 20 may include various forms of macro base stations, micro base stations, relay stations, APs (Access Points), etc. In systems using different wireless access technologies, the names of devices with access network device functions may be different. For example, in the 5G NR (New Radio) system, it is called gNodeB or gNB (Next Generation Node B). With the evolution of communication technology, the name "access network device" may change. For the convenience of description, in the embodiments of the present application, the above-mentioned devices that provide wireless communication functions for the terminal device 10 are collectively referred to as access network devices. In some embodiments, a communication relationship can be established between the terminal device 10 and the core network network element 30 through the access network device 20. For example, in an LTE (Long Term Evolution) system, the access network device 20 may be an Evolved Universal Terrestrial Radio Access Network (EUTRAN) or one or more eNodeBs in the EUTRAN. In a 5G NR system, the access network device 20 may be a Radio Access Network (RAN) or one or more gNBs in the RAN. In the embodiments of the present application, unless otherwise specified, the "network device" referred to refers to the access network device 20, such as a base station.

[0031] The core network element 30 is a network element deployed in the core network. The functions of the core network element 30 are mainly to provide user connection, user management, and service bearer, and to provide an interface to the external network as a bearer network. For example, the core network elements in the 5G NR system may include network elements such as the AMF (Access and Mobility Management Function) entity, the UPF (User Plane Function) entity, and the SMF (Session Management Function) entity.

[0032] In some embodiments, the access network device 20 and the core network element 30 communicate with each other via an air interface technology, such as the NG interface in the 5G NR system. The access network device 20 and the terminal device 10 communicate with each other via an air interface technology, such as the Uu interface.

[0033] The "5G NR system" in the embodiments of the present application may also be referred to as a 5G system or an NR system, but those skilled in the art will understand its meaning. The technical solutions described in the embodiments of the present application may be applicable to LTE systems, 5G NR systems, and subsequent evolution systems of 5G NR systems (e.g., B5G (Beyond 5G) systems, 6G systems (6th Generation System, sixth generation mobile communication systems)), and other communication systems such as NB-IoT (Narrow Band Internet of Things) systems, which are not limited in this application.

[0034] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources (for example, frequency domain resources, or spectrum resources) on the carrier used by the cell. The cell can be a cell corresponding to the network device (for example, a base station). The cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cell, micro cell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0035] Before introducing the technical solutions of this application, we first introduce and explain some of the relevant technical knowledge involved in this application. The following related technologies can be combined with the technical solutions of the embodiments of this application as optional solutions, and they all fall within the scope of protection of the embodiments of this application. The embodiments of this application include at least part of the following contents.

[0036] Figure 2 shows the 5G network system architecture. The UE establishes an access layer connection with the AN (Access Network) through the Uu interface, exchanging access layer messages and wireless data transmission. The UE establishes a non-access layer (NAS) connection with the AMF through the N1 interface, exchanging NAS messages. The AMF is the mobility management function in the core network, and the SMF is the session management function in the core network. In addition to managing UE mobility, the AMF is also responsible for forwarding session management-related messages between the UE and the SMF. The PCF (Policy Control Function) is a policy management function in the core network, responsible for formulating policies related to UE mobility management, session management, and billing. The UPF is a user plane function in the core network, communicating with external data networks through the N6 interface and with the AN through the N3 interface. After the UE accesses the 5G network through the Uu interface, it establishes a PDU (Protocol Data Unit) session under the control of the SMF for data transmission.

[0037] In order to improve the coverage of access network equipment, relay nodes can be used in the network, as shown in Figure 3.

[0038] In Figure 3, a terminal device (UE1 on the left) connects to the CN of MNO (Mobile Network Operator) 1 via the gNB function on the vehicle-mounted relay. The vehicle-mounted relay not only has gNB functionality but also complete UE functionality. The UE function in the vehicle-mounted relay connects to the CN of MNO2 via access network equipment. This means that the CN connected to UE1 on the left may not be the same as the CN connected to the UE function in the vehicle-mounted relay. The vehicle-mounted relay can function both as a UE connecting to MNO2's CN and as a gNB connecting UE1 to MNO1's CN, thereby enhancing network coverage.

[0039] As shown in Figure 3, UE1 on the left utilizes the gNB functionality of the on-board relay. Traditional access network equipment's TAC and cell identifier (e.g., cell ID) are configured through OAM. Once configured, the gNB can begin broadcasting. Operation, maintenance, and management (OAM) refers to network management tasks based on the actual needs of the operator's network operations. Network management tasks are typically divided into three categories: operation, administration, and maintenance (abbreviated as OAM). Operation primarily involves daily network and service analysis, forecasting, planning, and configuration; maintenance primarily involves daily operational activities such as testing and troubleshooting the network and its services. These tasks are performed by operators in the backend and require manual configuration, making it impossible to achieve real-time and flexible configuration of the access network equipment's network coverage. Because on-board relays inherently offer excellent mobility, static configuration is clearly unsuitable for configuring the TAC and cell identifier of the gNB on the on-board relay. The technical solutions provided in the embodiments of this application enable dynamic management of tracking areas and cell identifiers in VMRs, enabling more flexible and convenient TAC and cell identifier configuration for the gNB on the on-board relay.

[0040] Please refer to FIG4 , which shows a flow chart of an information indication method provided by an embodiment of the present application. The method is executed by a first device and includes the following step 410 .

[0041] Step 410: The first device receives first information sent by a first core network element, where the first information is used to indicate at least one TAC and / or at least one cell identifier that the first device is allowed or authorized to broadcast.

[0042] Correspondingly, the first core network element sends the first information to the first device.

[0043] TA (Tracking Area) is a new concept established by the cellular communication system for UE location management. When the UE is in idle state, the core network can know the tracking area where the UE is located. At the same time, when the idle UE needs to be paged, it must be paged in all cells in the tracking area where the UE is registered. Multiple TAs form a TA list and are assigned to a UE at the same time. When the UE moves within the TA list (TA List), it does not need to perform mobility registration updates to reduce frequent interactions with the network; when the UE enters a new TA area that is not in its registered TA list, it needs to perform a mobility new registration update, and the AMF reallocates a group of TAs to the UE. The newly allocated TA may also include some TAs in the original TA list. Each cell belongs to only one TA. TA is a cell-level configuration. Multiple cells can be configured with the same TA, and a cell can only belong to one TA. In some embodiments, the TA can be identified by a TAC.

[0044] A cell is the basic unit of coverage in a cellular communication system. Because there are so many cells, each requires an identifier to distinguish it. This is called a cell identifier. Cell identifiers give meaning to neighboring cells. Cell identifiers are generally divided into two types: physical and logical. Physical identifiers are generally simpler and used only in wireless networks; logical identifiers are network-wide and therefore longer. For example, in the LTE system, the physical identifier of a cell is called the Physical Cell Identifier (PCI), which ranges from 0 to 503 and is used only in wireless networks. It is a key parameter for cell reference signals, synchronization signals, and terminal measurements. The logical identifier of a cell is called the Cell Identification (CID), a 28-bit binary number.

[0045] In some embodiments, the first device is mobile. For example, the first device is a mobile device such as a vehicle-mounted device or a mobile phone. As shown in FIG3 , the first device may be the vehicle-mounted relay in FIG3 .

[0046] In some embodiments, the first device functions as both a terminal device and an access network device. In other words, the first device can establish a communication connection with other access network devices as a terminal device, and can also establish a communication connection with other terminal devices as an access network device. Here, "other access network devices" refers to access network devices other than the first device, and "other terminal devices" refers to terminal devices other than the first device. In some embodiments, the first device can be a relay device, and remote terminals can establish a communication connection with the core network through the first device.

[0047] In some embodiments, the first device may also be referred to as a relay device, or the first device may have the function of a relay device, which is not limited in this application.

[0048] In some embodiments, the first information includes at least one of the following information: at least one TAC that the first device is allowed or authorized to broadcast, at least one cell identifier that the first device is allowed or authorized to broadcast, a first S-NSSAI (Single Network Slice Selection Assistance Information), a first DNN (Data Network Name), and geographic location information.

[0049] In some embodiments, the first information includes at least one TAC that the first device is allowed or authorized to broadcast.

[0050] In some embodiments, the first information includes at least one cell identity that the first device is allowed or authorized to broadcast.

[0051] In some embodiments, the first information includes at least one TAC that the first device is allowed or authorized to broadcast, and at least one cell identity that the first device is allowed or authorized to broadcast.

[0052] In some embodiments, the first information includes at least one TAC that the first device is allowed or authorized to broadcast, at least one cell identifier that the first device is allowed or authorized to broadcast, and geographic location information.

[0053] In some embodiments, the first information includes a first S-NSSAI and / or a first DNN.

[0054] In some embodiments, the first information includes a first S-NSSAI, a first DNN, and geographic location information.

[0055] In some embodiments, the first S-NSSAI is an S-NSSAI corresponding to at least one TAC and / or at least one cell identifier that the first device is allowed or authorized to broadcast.

[0056] For cellular communication systems, network slicing is mainly reflected in admission control, network selection and resource separation. The standard is mainly identified through the S-NSSAI parameter. SST (Slice / Service Type) indicates the slice and service type of S-NSSAI, while sst-SD (Slice Differentiator) is the composition of the S-NSSAI parameter slice, service type and slice component. The SST field has standard values ​​and non-standard values, but the UE shall not use S-NSSAI with non-standard values ​​in the access layer process. Values ​​0 to 127 belong to the standard SST range. Values ​​128 to 255 belong to the operator-specific range. The SD field has a reserved value "no SD value associated with The SST" defined as hexadecimal FFFFFF. In some protocols, the SD field is not included to indicate that no SD value is associated with the SST. Among them, the slice / service type (SST) refers to the expected network slice behavior in terms of functions and services; the slice component (SD) is optional information that supplements the slice / service type to distinguish between multiple network slices l of the same slice / service type.

[0057] In some embodiments, the TAC and / or cell ID are associated with the S-NSSAI. When the TAC and / or cell ID are known, the corresponding S-NSSAI can be obtained; when the S-NSSAI is known, the corresponding TAC and / or cell ID can be obtained.

[0058] In some embodiments, the first DNN is a DNN corresponding to at least one TAC and / or at least one cell identifier that the first device is allowed or authorized to broadcast.

[0059] The DNN in 5GS and the APN (Access Point Name) in 4G are mappable; therefore, the specification's description, definition, and usage of the APN mirror the description, definition, and usage of the DNN. A DNN or APN consists of two parts: 1) a network ID (identification), which identifies an external network and is mandatory; 2) an optional operator ID, which identifies the operator.

[0060] Network ID: The network ID contains at least one label and is up to 63 bytes long. It cannot start with a network element name such as "rac", "lac", "sgsn", or "rnc", cannot end with ".gprs", and cannot contain "*".

[0061] Operator ID: The operator ID consists of three tags. The last tag must be ".gprs". The first and second tags must uniquely identify a PLMN (Public Land Mobile Network). Each operator has a default DNN / APN operator ID, which is derived from the IMSI: "mnc <mnc>.mcc <mcc>.gprs". For LBO (Local Breakout) roaming scenarios (that is, when the PGW / UPF of the VPLMN (Visited PLMN) provides services to access external networks), the operator ID of the DNN / APN should be the network ID of the VPLMN.

[0062] In some embodiments, the TAC and / or cell identifier are associated with the DNN. If the TAC and / or cell identifier are known, the corresponding DNN can be obtained; if the DNN is known, the corresponding TAC and / or cell identifier can be obtained.

[0063] In some embodiments, the geographic location information includes at least one of the following: a TAC of an access network device to which the first device is connected, a cell identifier of the access network device to which the first device is connected, and latitude and longitude coordinates of the location of the first device.

[0064] In some embodiments, the geographic location information is geographic location information of the first device.

[0065] In some embodiments, the access network device connected to the first device is a second device. The second device may have only the functions of an access network device or may have the functions of both a terminal device and an access network device. This application does not limit this. Since the second device is an access network device with respect to the first device, the second device is referred to as the access network device connected to the first device.

[0066] In some embodiments, the first core network element is an AMF.

[0067] In some embodiments, after step 410 , the method further includes the following step 420 .

[0068] Step 420: The first device broadcasts at least one TAC and / or at least one cell identifier.

[0069] In some embodiments, after receiving the first information, the first device may broadcast at least one TAC and / or at least one cell identifier indicated in the first information. Other terminal devices (terminal devices other than the first device) may use the first device as an access network device and access the core network through the at least one TAC and / or at least one cell identifier broadcast by the first device.

[0070] In some embodiments, if the first information includes a first S-NSSAI and / or a first DNN, the first device can determine the TAC and / or cell identifier that the first device is allowed or authorized to broadcast based on the first S-NSSAI and / or the first DNN, and then the first device broadcasts the TAC and / or cell identifier that is allowed or authorized to broadcast.

[0071] In some embodiments, if the first information includes the first S-NSSAI and / or the first DNN, step 420 can be replaced by the following step 421.

[0072] Step 421: The first device broadcasts a first S-NSSAI and / or a first DNN.

[0073] In some embodiments, other terminal devices (terminal devices other than the first device) may determine the TAC and / or cell identifier that the first device is allowed or authorized to broadcast based on the first S-NSSAI and / or the first DNN.

[0074] The technical solution provided in the embodiment of the present application indicates to the first device through the core network network element at least one TAC and / or at least one cell identifier that the first device is allowed or authorized to broadcast, without the need for an operator to manually configure the TAC and / or cell identifier that the first device is allowed or authorized to broadcast, making the configuration method of TAC and cell identifier more flexible and convenient.

[0075] In some embodiments, the first information may be carried in any message sent by the first core network element to the first device. For example, the first information may be carried in a registration accept message sent by the first core network element to the first device, a downlink NAS transmission message sent by the first core network element to the first device, or a PDU session establishment accept message sent by the first core network element to the first device.

[0076] In this regard, the embodiments of the present application provide corresponding implementation plans based on the above three exemplary schemes.

[0077] Solution 1: The first information is carried in the registration acceptance message

[0078] In some embodiments, the first information is carried in a registration acceptance message corresponding to a registration request message, wherein the registration request message is a message sent by the first device for requesting to initiate a registration process.

[0079] In some embodiments, the registration accept message may also be referred to as a registration response message.

[0080] It should be noted that the acceptance messages mentioned in the embodiments of the present application can all be referred to as response messages. For example, a registration acceptance message can be referred to as a registration response message, and a PDU session establishment acceptance message can be referred to as a PDU session establishment response message.

[0081] FIG5 is a flowchart of the information indication method provided by the embodiment of Solution 1. The method may include at least one of the following steps 1 to 2.

[0082] Step 1: The first device sends a registration request message to the first core network element. The registration request message is used to initiate a registration process.

[0083] Correspondingly, the first core network network element receives the registration request message sent by the first device.

[0084] In some embodiments, the registration message may be used to initiate an initial registration process or a mobility registration process, which is not limited in this application.

[0085] In some embodiments, the registration request message carries a user identifier and a registration type. In some embodiments, the registration type includes at least one of the following: initial registration, mobility registration, and periodic registration.

[0086] In some embodiments, the user identifier is used to uniquely identify the first device. In some embodiments, the user identifier can be a temporary identifier of the first device or a SUCI (Subscription Concealed Identifier), which is not limited in this application. If the user identifier is a SUCI, after obtaining the user identifier, the first core network element needs to parse the SUCI to obtain a SUPI (Subscription Permanent Identifier).

[0087] SUCI consists of the following components:

[0088] (1) SUPI Type: ranges from 0 to 7. It identifies the type of SUPI hidden in the SUCI. The following values ​​are defined:

[0089] -0: IMSI (International Mobile Subscriber Identification Number)

[0090] -1: Network Specific Identifier (NSI)

[0091] -2: Global Line Identifier (GLI)

[0092] -3: Global Cable Identifier (GCI)

[0093] -4 to 7: Reserve values ​​for future use

[0094] (2) Home Network Identifier (HNI): used to identify the user's home network.

[0095] When the SUPI type is IMSI, the home network identifier consists of two parts:

[0096] Merchant Category Code (MCC): Consists of three decimal digits. The MCC uniquely identifies the country where the mobile user is registered.

[0097] Mobile Network Code (MNC): Consists of two or three decimal digits. The MNC identifies the mobile user's home PLMN or SNPN.

[0098] When the SUPI type is NSI, GLI or GCI, the Home Network Identifier consists of a variable-length character string.

[0099] SUPI is a 5G concept, equivalent to IMSI in LTE. Its format and size are the same as IMSI. However, unlike IMSI, SUPI is the user's permanent identity information that never appears on the air interface. What appears on the air interface is SUCI.

[0100] Step 2: The first core network element sends a registration acceptance message to the first device. The registration acceptance message is used to indicate acceptance of the registration request of the first device.

[0101] Correspondingly, the first device receives the registration acceptance message sent by the first core network network element.

[0102] In some embodiments, the registration acceptance message carries the first information.

[0103] In some embodiments, the first information can be sent to the first device after being determined by the first core network element, or it can be indicated to the first core network element by other core network elements and then sent to the first device by the first core network element. This application does not limit this.

[0104] In some embodiments, the registration acceptance message also includes a 5G-GUTI (Globally Unique Temporary UE Identity) and a registration area.

[0105] 5G-GUTI is a 5G globally unique temporary UE identifier, which can reduce the explicit use of UE's permanent identifier in communications and improve security.

[0106] In some embodiments, the registration area refers to a registration area of ​​the first device. In some embodiments, the registration area includes at least one tracking area and / or at least one cell.

[0107] In some embodiments, the first information is indicated to the first core network element by other core network elements and then sent by the first core network element to the first device. Before step 2, the method also includes the following steps 3 to 4.

[0108] Step 3: The first core network element sends a second message to the second core network element, where the second message is used to request policy information related to accessibility and mobility management.

[0109] Correspondingly, the second core network element receives the second message sent by the first core network element.

[0110] In some embodiments, the second message is an access and mobility policy control create request message. In some embodiments, the second message is an Npcf_AMPolicyControl Create Request.

[0111] In some embodiments, the second core network element is a PCF.

[0112] In some embodiments, the second message may be referred to as an Npcf_AMPolicyControl Create Request message.

[0113] In some embodiments, the second message includes at least one of the following: SUPI, access type, location information, and PLMN ID of the first device.

[0114] In some embodiments, the access type includes at least one of the following: 3GPP access, non-3GPP access.

[0115] The 5G core network supports access through non-3GPP (3rd Generation Partnership Project) access networks (such as WLAN (Wireless Local Area Network)). Non-3GPP access networks should be connected to the 5G core network through the non-3GPP InterWorking Function (N3IWF). The N3IWF connects to the 5G core network CP and UP functions through the N2 and N3 interfaces respectively. If the selected N3IWF is located in the same PLMN as the 3GPP access, UEs connected to the same 5G core network of the PLMN through both 3GPP access and non-3GPP access will be served by the same AMF.

[0116] In some embodiments, the location information refers to the location information of the first device. In some embodiments, the location information of the first device may be reported by the first device to the first core network network element, or may be obtained by the first core network network element based on communication measurements with the first device, and this application does not limit this. In some embodiments, the location information of the first device is added by the access network device to the registration request message sent by the first device. In some embodiments, the communication between the first device and the first core network network element is forwarded by the access network device, and the access network device may process the relevant information or message (for example, add new information) when forwarding the relevant information or message.

[0117] When the UE is turned on, its first task is to search for a network and register, which is called network selection. The UE's network selection operation can be divided into two processes: PLMN selection and cell search. During the PLMN selection process, the UE maintains some PLMN lists, which sort the PLMNs by priority and then search from high priority to low priority. The priority order is: RPLMN (Registered PLMN), HPLMN (Home PLMN), UPLMN (User Controlled PLMN), OPLMN (Operator Controlled PLMN), VPLMN. Except for VPLMN, each type of PLMN list stores the corresponding RAT (Radio Access Technology), which identifies GSM / GPRS technology, UMTS technology, or E-UTRA technology, to determine which access technology takes priority under the same PLMN. Different PLMNs are distinguished by PLMN ID.

[0118] Step 4: The first core network element receives a first message sent by the second core network element, where the first message is used to indicate policy information related to access and mobility management.

[0119] Correspondingly, the second core network element sends the first message to the first core network element.

[0120] In some embodiments, the first message is an Access and Mobility Policy Control Create Response message. In some embodiments, the first message is an Npcf_AMPolicyControl Create Response.

[0121] In some embodiments, the access and mobility management-related policy information includes at least one of the following: a TAC that the first device is allowed or authorized to broadcast, a cell identifier that the first device is allowed or authorized to broadcast, a first S-NSSAI, and a first DNN.

[0122] In some embodiments, after step 2, the following step 5 is also included.

[0123] Step 5: The first device sends a registration completion message to the first core network element. The registration completion message is used to confirm that the 5G-GUTI configured in the registration acceptance message has taken effect.

[0124] In some embodiments, after completing registration, the first device establishes a PDU session with the first core network element based on at least one TAC and / or at least one cell identifier indicated in the first information. Exemplarily, the first device sends a PDU session establishment request message to the first core network element, where the PDU session establishment request message is used to request establishment of a PDU session with the first core network element.

[0125] In some embodiments, if the first information includes a first S-NSSAI and a first DNN, a PDU session is established based on the first S-NSSAI and the first DNN indicated in the first information.

[0126] In some embodiments, after completing registration, the first device broadcasts based on at least one TAC and / or at least one cell identifier indicated in the first information. In other words, after completing registration, the first device broadcasts at least one TAC and / or at least one cell identifier indicated in the first information.

[0127] In some embodiments, if the first information includes the first S-NSSAI and the first DNN, the first device broadcasts the first S-NSSAI and the first DNN based on the first S-NSSAI and the first DNN indicated in the first information. In other words, after completing registration, the first device broadcasts the first S-NSSAI and the first DNN.

[0128] In some embodiments, the first device completes registration after the first device receives a registration acceptance message sent by the first core network element.

[0129] It should be noted that steps 1 and 3-5 mentioned in the above embodiment are optional steps. Any one or more of steps 1 and 3-5 mentioned in the above embodiment can be combined with step 2 to form a new embodiment, which is within the scope of protection of this application. For example, step 2 is combined with step 1 to form a new embodiment. For example, steps 1-4 are combined to form a new embodiment.

[0130] Through the above method, the first device can obtain at least one TAC and / or at least one cell identifier that the first device is allowed or authorized to broadcast in the registration acceptance message, and the configuration method of the TAC and the cell identifier is more flexible and convenient.

[0131] Solution 2: The first information is carried in the downlink NAS transmission message

[0132] In some embodiments, the first information is carried in a downlink NAS transmission message, and the downlink NAS transmission message is used to indicate policy data of the first device.

[0133] FIG6 is a flowchart of the information indication method provided by the embodiment of Solution 2. The method may include the following step 1.

[0134] Step 1: A first core network element sends a downlink NAS transmission message to a first device, where the downlink NAS transmission message is used to indicate policy data of the first device.

[0135] Correspondingly, the first device receives the downlink NAS transmission message sent by the first core network network element.

[0136] In some embodiments, the downlink NAS transmission message includes at least one of the following: a TAC that the first device is allowed or authorized to broadcast, a cell identifier that the first device is allowed or authorized to broadcast, a first S-NSSAI, a first DNN, and policy data of the first device; wherein, the first S-NSSAI is the S-NSSAI corresponding to at least one TAC and / or at least one cell identifier that the first device is allowed or authorized to broadcast, and the first DNN is the DNN corresponding to at least one TAC and / or at least one cell identifier that the first device is allowed or authorized to broadcast.

[0137] In some embodiments, after receiving a downlink NAS transmission message sent by a first core network element, the first device establishes a PDU session with the first core network element based on at least one TAC and / or at least one cell identifier indicated in the first information. Exemplarily, the first device sends a PDU session establishment request message to the first core network element, where the PDU session establishment request message is used to request establishment of a PDU session with the first core network element.

[0138] In some embodiments, if the first information includes a first S-NSSAI and a first DNN, a PDU session is established based on the first S-NSSAI and the first DNN indicated in the first information.

[0139] In some embodiments, after receiving a downlink NAS transmission message sent by a first core network element, the first device broadcasts the at least one TAC and / or at least one cell identifier indicated in the first information. In other words, after receiving a downlink NAS transmission message sent by the first core network element, the first device broadcasts the at least one TAC and / or at least one cell identifier indicated in the first information.

[0140] In some embodiments, if the first information includes a first S-NSSAI and a first DNN, the broadcast is performed based on the first S-NSSAI and the first DNN indicated in the first information. In other words, after the first device receives the downlink NAS transmission message sent by the first core network element, it broadcasts the first S-NSSAI and the first DNN.

[0141] In some embodiments, before step 1, the method further includes at least one of the following steps 2 to 8.

[0142] Step 2: The first device sends a registration request message to the first core network element. The registration request message is used to initiate a registration process.

[0143] Step 3: The first core network element sends a second message to the second core network element, where the second message is used to request policy information related to accessibility and mobility management.

[0144] In some embodiments, the second message is an access and mobility policy control create request message. In some embodiments, the second message is an Npcf_AMPolicyControl Create Request.

[0145] Step 4: The second core network element sends a first message to the first core network element, where the first message is used to indicate policy information related to access and mobility management.

[0146] In some embodiments, the first message is an Access and Mobility Policy Control Create Response message. In some embodiments, the first message is an Npcf_AMPolicyControl Create Response.

[0147] Step 5: The first core network element sends a registration acceptance message to the first device. The registration acceptance message is used to indicate acceptance of the registration request of the first device.

[0148] Step 6: The first device sends a registration completion message to the first core network element. The registration completion message is used to confirm that the 5G-GUTI configured in the registration acceptance message has taken effect.

[0149] For a detailed description of steps 2 to 6, please refer to the description of steps 1 to 5 in the first embodiment, and this application will not repeat them one by one here. Unlike steps 1 to 5 in the first embodiment, the policy control creation response message in step 2 and the registration acceptance message in step 5 do not carry the first information.

[0150] Step 7: The first core network element sends a policy control update notification request message to the second core network element.

[0151] In some embodiments, the policy control update notification request message includes policy data of the first device. The policy data of the first device includes URSP (UE Route Selection Policy) rules, and the URSP rules may carry indication parameters.

[0152] In some embodiments, the policy control update notification request message may be called Npcf_UEPolicyControl Create Request.

[0153] Step 8: The second core network element sends a policy control update notification response message to the first core network element.

[0154] The policy control update notification response information corresponds to the policy control update notification request message in step 7, and is used to instruct the second core network element to accept the policy update notification request of the first core network element.

[0155] In some embodiments, the policy control update notification response information may be called Npcf_UEPolicyControl Create Response.

[0156] In some embodiments, after step 1, the method further includes at least one of the following steps 9 to 11.

[0157] Step 9: The first device sends an uplink NAS transmission message to the first core network element. The above NAS transmission information is used to confirm successful reception of the policy data of the first device.

[0158] Step 10: The first core network element sends a policy control update request message to the second core network element. The policy control update request message is used to confirm successful reception of the policy data of the first device.

[0159] In some embodiments, the policy control update request message may be referred to as Npcf_UEPolicyControlUpdateNotifyRequest.

[0160] Step 11: The second core network element sends a policy control update response message to the first core network element. The policy control update response message is used to confirm receipt of the policy control update request message.

[0161] In some embodiments, the policy control update response message may be referred to as Npcf_UEPolicyControlUpdateNotifyResponse.

[0162] It should be noted that steps 2 to 11 mentioned in the above embodiment are optional steps. Any one or more of steps 2 to 11 mentioned in the above embodiment can be combined with step 1 to form a new embodiment, which is within the scope of protection of this application. For example, step 2, step 5, and step 6 are combined with step 1 to form a new embodiment. For example, step 1 is combined with step 9 to form a new embodiment.

[0163] Through the above method, the first device can obtain at least one TAC and / or at least one cell identifier that the first device is allowed or authorized to broadcast in the downlink NAS transmission message, without the need for the operator to manually configure the TAC and / or cell identifier that the first device is allowed or authorized to broadcast, and the configuration method of the TAC and cell identifier is more flexible and convenient.

[0164] Solution 3: The first information is carried in the PUD session establishment acceptance message

[0165] In some embodiments, the first information is carried in a PDU session establishment accept message, and the PDU session establishment accept message is used to instruct the first core network element to accept the PDU session establishment request of the first device.

[0166] In some embodiments, the first information is carried in a PCO (Protocol Configuration Option); alternatively, the first information is carried in a downlink NAS transport message. In other words, the first information can be carried in a PCO and sent to the first device, or the first information can be carried in a downlink NAS transport message and sent to the first device. In some embodiments, a PDU Session Establishment Accept message is carried in a PCO and sent to the first device. In some embodiments, the PDU Session Establishment Accept message is carried in a downlink NAS transport message and sent to the first device.

[0167] Figure 7 is a flow chart of the information indication method provided by the embodiment described in Solution 3. The method may include at least one of the following steps 1 to 19.

[0168] Step 1: The first device initiates the registration process.

[0169] In some embodiments, the network assigns a 5G-GUTI to the first device during the registration process.

[0170] Regarding the registration process, please refer to the introduction in the above solution 1, and the embodiment of this application will not be repeated here. Compared with the steps in solution 1, in this embodiment, during the registration process, the first core network element does not indicate the first information to the first device.

[0171] Step 2: The first device sends an uplink NAS transmission message to the first core network element.

[0172] In some embodiments, when the first device needs to send data, the first device requests to establish a PDU session. In some embodiments, the uplink NAS transmission message includes at least one of the following: a PDU session identifier, a second S-NSSAI, a second DNN, a request type, and a PDU session establishment request message.

[0173] In some embodiments, the second S-NSSAI and the second DNN are different from the first S-NSSAI and the first DNN in the above embodiments. In some embodiments, if the first device pre-configures or pre-stores the relevant S-NSSAI and / or DNN, the second S-NSSAI may be the S-NSSAI pre-configured or pre-stored by the first device, and the second DNN may be the DNN pre-configured or pre-stored by the first device. In some embodiments, if the first device does not pre-configure or store the relevant S-NSSAI and / or DNN, the uplink NAS transmission message may not carry the second S-NSSAI and / or second DNN, and the first core network element may use the default S-NSSAI as the second S-NSSAI and the default DNN as the second DNN.

[0174] In some embodiments, the PDU session identifier is used to uniquely identify a PDU session.

[0175] In some embodiments, the PDU session request message includes at least one of the following: a PDU session identifier and a PDU session type.

[0176] In some embodiments, the PDU session identifier in the PDU session request message is the same as the PDU session identifier in the uplink NAS transmission message.

[0177] In some embodiments, the first core network element is an AMF.

[0178] Step 3: The first core network element selects a third core network element according to the second S-NSSAI and / or the second DNN, and sends a PDU session creation session management context request message to the third core network element.

[0179] In some embodiments, the third core network element is an SMF, and one SMF can manage one or more PDU sessions.

[0180] In some embodiments, the PDU session create session management context request message may be referred to as Nsmf_PDUsession_CreateSMcontext Request.

[0181] In some embodiments, the PDU session creation session management context request message includes at least one of the following: a PDU session identifier, an access and mobility management network element identifier, and a PDU session establishment request message.

[0182] Step 4: The third core network element sends a subscription data request message to the fourth core network element.

[0183] In some embodiments, the subscription data request message is used to obtain the subscription data. In some embodiments, the subscription data request message includes at least one of the following: a second S-NSSAI, a second DNN.

[0184] In some embodiments, the request does not include a message body, but includes query parameters.

[0185] The query parameters include the selected S-NSSAI, DNN, and PLMN ID information. These three query parameters are optional. If the S-NSSAI and DNN query parameters are not included, UDM will return all DNNs for all slices; if only DNN is included, UDM will return the DNN configuration of all slices available under the DNN. If only S-NSSAI is included without DNN, UDM will return all DNN configurations for the slice. If PLMN ID information is not carried, UDM will only return the configuration of the HPLMN associated with the S-NSSAI or DNN.

[0186] Note that S-NSSAI and DNN are important. If the S-NSSAI contains only the SST and not the SD portion, the UDM will assume that any SD value matches this slice query parameter. Furthermore, the DNN in the query parameter must be the DNN subscribed to by the UE; otherwise, the query request will fail, and the UDM will directly respond with a "404 Not Found" message. If the DNN selection mode in the PDU session establishment request received by the SMF from the AMF is a wildcard DNN, the SMF must also include the wildcard DNN in the query parameter. This way, when the SMF downloads the subscription data, it will also download the session subscription data for the wildcard DNN.

[0187] In some embodiments, the fourth core network element is a UDM (Unified Data Management).

[0188] Step 5: The fourth core network element sends the subscription data to the third core network element.

[0189] In some embodiments, the subscription data includes at least one of the following: allowed PDU session types, and default QoS (Quality of Service) parameters.

[0190] In some embodiments, the allowed PDU session type refers to a PDU session type allowed by the first device.

[0191] Step 6: The third core network element sends a session management policy association establishment request message to the second core network element.

[0192] Step 7: The second core network element sends a session management policy association establishment response message to the third core network element.

[0193] In some embodiments, the session management policy association establishment response message includes a default PCC (Policy and Charging Control Rule-PCC Rule) rule.

[0194] Step 8: The third core network element sends a PDU session establishment session management context response message to the first core network element.

[0195] In some embodiments, the PDU session establishment session management context response information can be called Nsmf_PDUsession_CreateSMcontext Response.

[0196] In some embodiments, the PDU session establishment session management context response information includes an SMF context identifier.

[0197] Step 9: The third core network element selects the fifth core network element and sends an N4 establishment request message to the fifth core network element.

[0198] In some embodiments, the N4 establishment request message includes at least one of the following: a PDU session identifier, a QoS flow identifier, and a QoS parameter. In 5GS, when a PDU session is established, a flow using the default QoS rule will be established together and maintained throughout the life cycle of the session (similar to the default bearer of 4G EPC (Evolved Packet Core)). This default flow should be a non-GBR (Guaranteed Bit Rate) QoS flow, that is, a flow that does not guarantee the rate, has low resource requirements, and only transmits a small amount of control information; if a QoS flow with guaranteed rate is required, a dedicated bearer or a dedicated connection should be initiated.

[0199] A QoS flow is not just a connection channel for a PDU session; it is closely related to quality of service. It is associated with a set of QoS service characteristics and parameters and is a connection channel with QoS characteristics. Other flows within the same PDU session may have different QoS characteristics.

[0200] Step 10: The fifth core network element sends an N4 establishment response message to the third core network element.

[0201] In some embodiments, the N4 establishment request response message includes at least one of the following: an IP (Internet Protocol, a protocol for interconnecting networks) address allocated by the fifth core network element, and a TEID (Tunnel Endpoint Identifier).

[0202] Step 11: The third core network element sends a communication N1N2 transmission message to the first core network element.

[0203] In some embodiments, the communication N1N2 transmission may be referred to as Namf_Communication_N1N2Message Transfer.

[0204] In some embodiments, the communication N1N2 transmission message includes at least one of the following: a PDU session identifier, a PDU session establishment accept message, and an N2-PDU session establishment request message.

[0205] In some embodiments, the PDU session establishment acceptance message includes at least one of the following: at least one TAC that the first device is allowed or authorized to broadcast, at least one cell identifier that the first device is allowed or authorized to broadcast, a first S-NSSAI, a first DNN, a PDU session identifier, a quality of service QoS flow identifier, QoS parameters, and QoS rules; wherein the first S-NSSAI is the S-NSSAI corresponding to the at least one TAC and / or at least one cell identifier that the first device is allowed or authorized to broadcast, and the first DNN is the DNN corresponding to the at least one TAC and / or at least one cell identifier that the first device is allowed or authorized to broadcast.

[0206] Step 12: The first core network element forwards the N2-PDU session establishment request message to the access network device; the first core network element forwards the PDU session establishment acceptance message to the first device via a downlink NAS transmission message.

[0207] In some embodiments, the access network device is NG-RAN.

[0208] In some embodiments, the first core network element may also forward the PDU session establishment acceptance message to the first device through the PCO.

[0209] Step 13: The access network device sends an RRC reconfiguration message to the first device. The RRC reconfiguration message carries a NAS container-PDU session establishment accept message.

[0210] Step 14: The first device sends an RRC reconfiguration completion message to the access network device.

[0211] Step 15: The access network device sends an N2-PDU session establishment accept message to the first core network network element.

[0212] In some embodiments, the N2-PDU session establishment acceptance message includes at least one of the following: a PDU session identifier, an IP address assigned by the access network device, and a TEID. In LET, a GTP tunnel used between two nodes communicating over the GTP (GPRS Tunneling Protocol) protocol uses an IP address, a UDP (User Datagram Protocol) port, and a TEID as identifiers for each node. After the GTP tunnel is established, when the sending node sends a GTP message to the receiving node, the GTP message header carries the TEID value assigned by the receiving node.

[0213] Step 16: The first core network element forwards the N2-PDU session establishment accept message to the third core network element via a PDU session update session management context request message.

[0214] In some embodiments, the PDU session update session management context request message may be referred to as Nsmf_PDUsession_UpdateSMcontext Request.

[0215] Step 17: The third core network element sends an N4 modification request message to the fifth core network element.

[0216] In some embodiments, the fifth core network element is a UPF.

[0217] In some embodiments, the N4 modification request message includes at least one of the following: an IP address and a TEID allocated by the access network device.

[0218] Step 18: The fifth core network element sends an N4 modification response message to the third core network element.

[0219] Step 19: The third core network element sends a PDU session update session management context response message to the first core network element.

[0220] In some embodiments, the PDU session update session management context response message may be referred to as Nsmf_PDUsession_UpdateSMcontext Response.

[0221] In some embodiments, after the first device receives the PDU session establishment accept message sent by the first core network element, the first device broadcasts based on at least one TAC and / or at least one cell identifier indicated in the first information. In other words, after the first device receives the PDU session establishment accept message sent by the first core network element, the first device broadcasts at least one TAC and / or at least one cell identifier indicated in the first information.

[0222] In some embodiments, if the first information includes a first S-NSSAI and a first DNN, the broadcast is performed based on the first S-NSSAI and the first DNN indicated in the first information. In other words, after the first device receives the PDU session establishment accept message sent by the first core network element, it broadcasts the first S-NSSAI and the first DNN.

[0223] It should be noted that steps 1 to 11 and steps 13 to 19 mentioned in the above embodiment are optional steps. Any one or more of steps 1 to 11 and steps 13 to 19 mentioned in the above embodiment can be combined with step 12 to form a new embodiment, which is within the scope of protection of this application. For example, step 11 is combined with step 12 to form a new embodiment. For example, steps 9 to 11 are combined with step 12 to form a new embodiment.

[0224] Through the above method, the first device can obtain at least one TAC and / or at least one cell identifier that the first device is allowed or authorized to broadcast in the PDU session establishment acceptance message, without the need for the operator to manually configure the TAC and / or cell identifier that the first device is allowed or authorized to broadcast. The configuration method of TAC and cell identifier is more flexible and convenient.

[0225] In the above method embodiments, the technical solution of this application is described only from the perspective of the interaction between the first device and the first core network element. The above steps performed by the first device can be independently implemented as a wireless communication method on the first device side, and the above steps performed by the first core network element can be independently implemented as a wireless communication method on the first core network element side. In addition, the embodiments provided herein can be arbitrarily combined to form new embodiments, all of which are within the scope of protection of this application.

[0226] The following are device embodiments of the present application, which can be used to implement the method embodiments of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments of the present application.

[0227] Please refer to Figure 8, which shows a block diagram of an information indication device provided by one embodiment of the present application. This device has the function of implementing the above-mentioned information indication method example. The function can be implemented by hardware or by hardware executing corresponding software. This device can be the first device described above, or it can be provided in the first device. As shown in Figure 8, the device 800 may include: a receiving module 810.

[0228] The receiving module 810 is used to receive first information sent by a first core network element, where the first information is used to indicate at least one TAC and / or at least one cell identifier that the first device is allowed or authorized to broadcast.

[0229] In some embodiments, the first information includes at least one of the following information: at least one TAC that the first device is allowed or authorized to broadcast, at least one cell identifier that the first device is allowed or authorized to broadcast, a first S-NSSAI, a first DNN, and geographic location information; wherein the geographic location information includes at least one of the following: the TAC of the access network device to which the first device is connected, the cell identifier of the access network device to which the first device is connected, and the latitude and longitude coordinates of the location of the first device.

[0230] In some embodiments, the first information is carried in a registration acceptance message corresponding to a registration request message, wherein the registration request message is a message sent by the first device to request initiation of a registration process.

[0231] In some embodiments, the first information is carried in a downlink NAS transmission message, and the downlink NAS transmission message is used to indicate policy data of the first device.

[0232] In some embodiments, the first information is carried in a PDU session establishment accept message, and the PDU session establishment accept message is used to instruct the first core network element to accept the PDU session establishment request of the first device.

[0233] In some embodiments, the first information is carried in a PCO; or, the first information is carried in a downlink NAS transmission message.

[0234] In some embodiments, the apparatus 800 further includes a sending module (not shown).

[0235] A sending module is configured to broadcast the at least one TAC and / or the at least one cell identifier.

[0236] The technical solution provided in the embodiment of the present application indicates to the first device through the core network network element at least one TAC and / or at least one cell identifier that the first device is allowed or authorized to broadcast, without the need for an operator to manually configure the TAC and / or cell identifier that the first device is allowed or authorized to broadcast, making the configuration method of TAC and cell identifier more flexible and convenient.

[0237] Please refer to Figure 9, which shows a block diagram of an information indication device provided by one embodiment of the present application. This device has the functionality to implement the aforementioned example information indication method. This functionality can be implemented in hardware or by hardware executing corresponding software. This device can be the first core network element described above, or it can be provided within the first core network element. As shown in Figure 9, the device 900 may include a sending module 910.

[0238] The sending module 910 is configured to send first information to a first device, where the first information is used to indicate at least one TAC and / or at least one cell identifier that the first device is allowed or authorized to broadcast.

[0239] In some embodiments, the first information includes at least one of the following information: at least one TAC that the first device is allowed or authorized to broadcast, at least one cell identifier that the first device is allowed or authorized to broadcast, a first S-NSSAI, a first DNN, and geographic location information; wherein the geographic location information includes at least one of the following: the TAC of the access network device to which the first device is connected, the cell identifier of the access network device to which the first device is connected, and the latitude and longitude coordinates of the location of the first device.

[0240] In some embodiments, the first information is carried in a registration acceptance message corresponding to a registration request message, wherein the registration request message is a message sent by the first device to request initiation of a registration process.

[0241] In some embodiments, the device further includes: a receiving module (not shown in the figure).

[0242] A receiving module is used to receive a first message sent by a second core network network element, where the first message is used to indicate policy information related to access and mobility management; the policy information related to access and mobility management includes at least one of the following: the TAC that the first device is allowed or authorized to broadcast, the cell identifier that the first device is allowed or authorized to broadcast, the first S-NSSAI, and the first DNN.

[0243] In some embodiments, the first information is carried in a downlink NAS transmission message, and the downlink NAS transmission message is used to indicate policy data of the first device.

[0244] In some embodiments, the first information is carried in a PDU session establishment accept message, and the PDU session establishment accept message is used to instruct the first core network element to accept the PDU session establishment request of the first device.

[0245] In some embodiments, the first information is carried in a PCO; or, the first information is carried in a downlink NAS transmission message.

[0246] In some embodiments, the receiving module is also used to receive the PDU session establishment acceptance message sent by the third core network network element; the PDU session establishment acceptance message includes at least one of the following: at least one TAC that the first device is allowed or authorized to broadcast, at least one cell identifier that the first device is allowed or authorized to broadcast, a first S-NSSAI, a first DNN, a PDU session identifier, a QoS flow identifier, QoS parameters, and a QoS rule.

[0247] The technical solution provided in the embodiment of the present application indicates to the first device through the core network network element at least one TAC and / or at least one cell identifier that the first device is allowed or authorized to broadcast, without the need for an operator to manually configure the TAC and / or cell identifier that the first device is allowed or authorized to broadcast, making the configuration method of TAC and cell identifier more flexible and convenient.

[0248] It should be noted that the device provided in the above embodiment only uses the division of the above-mentioned functional modules as an example to implement its functions. In actual applications, the above-mentioned functions can be assigned to different functional modules according to actual needs, that is, the content structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0249] Regarding the apparatus in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0250] Please refer to Figure 10, which shows a schematic diagram of the structure of a first device provided in one embodiment of the present application. The first device 1000 may include: a processor 1001, a transceiver 1002, and a memory 1003. The transceiver 1002 is used to implement a sending or receiving function, such as the function of the receiving module 810 described above, and the processor 1001 may be used to implement other processing functions or control sending and / or receiving.

[0251] The processor 1001 includes one or more processing cores. The processor 1001 executes various functional applications and information processing by running software programs and modules.

[0252] The transceiver 1002 may include at least one of a receiver and a transmitter. For example, the receiver and the transmitter may be implemented as the same wireless communication component, which may include a wireless communication chip and a radio frequency antenna.

[0253] The memory 1003 may be connected to the processor 1001 and the transceiver 1002 .

[0254] The memory 1003 may be used to store a computer program executed by the processor, and the processor 1001 is used to execute the computer program to implement each step in the above method embodiment.

[0255] In some embodiments, the transceiver 1002 is used to receive first information sent by a first core network element, where the first information is used to indicate at least one tracking area code TAC and / or at least one cell identifier that the first device is allowed or authorized to broadcast.

[0256] For details not described in detail in this embodiment, please refer to the above embodiments and will not be described in detail here.

[0257] In addition, the memory can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: magnetic or optical disks, electrically erasable programmable read-only memory, erasable programmable read-only memory, static access memory, read-only memory, magnetic memory, flash memory, and programmable read-only memory.

[0258] Please refer to Figure 11, which shows a schematic diagram of the structure of a first core network element provided by one embodiment of the present application. The first core network element 1100 may include: a processor 1101, a transceiver 1102, and a memory 1103. The transceiver 1102 is configured to implement receiving and / or transmitting functions, such as the functions of the transmitting module 910 and / or the receiving module described above; the processor 1101 is configured to implement other functions besides transmitting and / or receiving, or to control transmitting and / or receiving.

[0259] The processor 1101 includes one or more processing cores, and executes various functional applications and information processing by running software programs and modules. The processor 1101 is used to execute the other steps except the sending and receiving steps executed by the first core network element in the above method embodiment.

[0260] Transceiver 1102 may include a receiver and a transmitter. For example, the receiver and transmitter may be implemented as the same wireless communication component, which may include a wireless communication chip and a radio frequency antenna. Transceiver 1102 is configured to perform the sending and / or receiving steps performed by the first core network element in the above method embodiment.

[0261] The memory 1103 may be connected to the processor 1101 and the transceiver 1102 .

[0262] The memory 1103 may be used to store a computer program executed by the processor, and the processor 1101 may be used to execute the computer program to implement each step in the above-mentioned method embodiment on the first core network network element side.

[0263] In addition, the memory can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: magnetic or optical disks, electrically erasable programmable read-only memory, erasable programmable read-only memory, static access memory, read-only memory, magnetic memory, flash memory, and programmable read-only memory.

[0264] In some embodiments, the transceiver 1102 is configured to send first information to the first device, where the first information is configured to indicate at least one tracking area code (TAC) and / or at least one cell identifier (CID) that the first device is allowed or authorized to broadcast.

[0265] For details not described in detail in this embodiment, please refer to the above embodiments and will not be described in detail here.

[0266] An embodiment of the present application also provides a computer-readable storage medium, in which a computer program is stored, and the computer program is used to be executed by a processor to implement the above-mentioned information indication method on the first device side, or to implement the above-mentioned information indication method on the first core network network element side. In some embodiments, the computer-readable storage medium may include: ROM (Read-Only Memory), RAM (Random-Access Memory), SSD (Solid State Drives) or optical disks, etc. Among them, random access memory may include ReRAM (Resistance Random Access Memory) and DRAM (Dynamic Random Access Memory).

[0267] An embodiment of the present application also provides a chip, which includes a programmable logic circuit and / or program instructions. When the chip is running, it is used to implement the above-mentioned information indication method on the first device side, or to implement the above-mentioned information indication method on the first core network network element side.

[0268] An embodiment of the present application also provides a computer program product, which includes a computer program, and the computer program is stored in a computer-readable storage medium. The processor reads and executes the computer program from the computer-readable storage medium to implement the above-mentioned information indication method on the first device side, or to implement the above-mentioned information indication method on the first core network network element side.

[0269] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that A and B are associated.

[0270] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and indication, configuration and configuration, etc.

[0271] In some embodiments of the present application, "predefined" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., including the first device and the first core network element). This application does not limit the specific implementation method. For example, predefined may refer to those defined in a protocol.

[0272] In some embodiments of the present application, the "protocol" may refer to a standard protocol in the communication field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and this application does not limit this.

[0273] In this document, "plurality" refers to two or more. "And / or" describes the relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can mean: A exists alone, A and B exist simultaneously, or B exists alone. The character " / " generally indicates that the associated objects are in an "or" relationship.

[0274] As used herein, “greater than or equal to” may mean greater than, equal to, or greater than, and “less than or equal to” may mean less than, equal to, or less than.

[0275] In addition, the step numbers described in this document only illustrate a possible execution order between the steps. In some other embodiments, the above steps may not be executed in the order of the numbers, such as two steps with different numbers are executed at the same time, or two steps with different numbers are executed in the opposite order of the diagram. The embodiments of the present application are not limited to this.

[0276] Those skilled in the art will appreciate that in one or more of the above examples, the functions described in the embodiments of the present application can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any media that facilitates the transmission of computer programs from one place to another. The storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0277] The above description is merely an exemplary embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.< / mcc> < / mnc>

Claims

1. An information indication method, characterized in that, The method is executed by a first device, and the method includes: Receiving first information sent by a first core network element, where the first information is used to indicate at least one tracking area code (TAC) and / or at least one cell identifier that the first device is allowed or authorized to broadcast.

2. The method according to claim 1, characterized in that, The first information includes at least one of the following information: at least one TAC that the first device is allowed or authorized to broadcast, at least one cell identifier that the first device is allowed or authorized to broadcast, first network slice selection assistance information (S-NSSAI), first data network name (DNN), geographical location information; where the geographical location information includes at least one of the following: the TAC of the access network device to which the first device is connected, the cell identifier of the access network device to which the first device is connected, the longitude and latitude coordinates of the location where the first device is located.

3. The method according to claim 1 or 2, characterized in that, The first information is carried in a registration acceptance message corresponding to a registration request message, where the registration request message is sent by the first device and is used to request to initiate a registration process.

4. The method according to claim 1 or 2, characterized in that, The first information is carried in a downlink non-access stratum (NAS) transport message, and the downlink NAS transport message is used to indicate the policy data of the first device.

5. The method according to claim 1 or 2, characterized in that, The first information is carried in a PDU session establishment acceptance message, and the PDU session establishment acceptance message is used to indicate that the first core network element accepts the PDU session establishment request of the first device.

6. The method according to claim 5, wherein The first information is carried in a protocol configuration option (PCO); or, the first information is carried in a downlink NAS transport message.

7. The method according to any one of claims 1 to 6, characterized in that, After receiving the first information sent by the first core network element, the method further includes: Broadcasting the at least one TAC and / or the at least one cell identifier.

8. An information indication method, characterized in that, The method is executed by a first core network element, and the method includes: Sending first information to a first device, where the first information is used to indicate at least one tracking area code (TAC) and / or at least one cell identifier that the first device is allowed or authorized to broadcast.

9. The method according to claim 8, wherein The first information includes at least one of the following information: at least one TAC that the first device is allowed or authorized to broadcast, at least one cell identifier that the first device is allowed or authorized to broadcast, first network slice selection assistance information (S-NSSAI), first data network name (DNN), geographical location information; where the geographical location information includes at least one of the following: the TAC of the access network device to which the first device is connected, the cell identifier of the access network device to which the first device is connected, the longitude and latitude coordinates of the location where the first device is located.

10. The method according to claim 8 or 9, characterized in that, The first information is carried in a registration acceptance message corresponding to a registration request message, where the registration request message is sent by the first device and is used to request to initiate a registration process.

11. The method according to claim 10, wherein The method further includes: Receive a first message sent by a second core network element, where the first message is used to indicate policy information related to access and mobility management; the policy information related to access and mobility management includes at least one of the following: the TAC that the first device is permitted or authorized to broadcast, the cell identifier that the first device is permitted or authorized to broadcast, a first S-NSSAI, and a first DNN.

12. The method according to claim 11, wherein The first message is an access and mobility policy control creation response message.

13. The method according to claim 8 or 9, characterized in that, The first information is carried in a downlink non-access stratum (NAS) transport message, and the downlink NAS transport message is used to indicate the policy data of the first device.

14. The method according to claim 8 or 9, characterized in that, The first information is carried in a PDU session establishment acceptance message, and the PDU session establishment acceptance message is used to indicate that the first core network element accepts the PDU session establishment request of the first device.

15. The method according to claim 14, wherein The first information is carried in a protocol configuration option (PCO); or, the first information is carried in a downlink NAS transport message.

16. The method according to claim 14 or 15, characterized in that, The method further includes: Receive the PDU session establishment acceptance message sent by a third core network element; the PDU session establishment acceptance message includes at least one of the following: at least one TAC that the first device is permitted or authorized to broadcast, at least one cell identifier that the first device is permitted or authorized to broadcast, a first S-NSSAI, a first DNN, a PDU session identifier, a quality of service (QoS) flow identifier, QoS parameters, and QoS rules.

17. An information indicating device, characterized in that, The apparatus includes: A receiving module, configured to receive first information sent by a first core network element, where the first information is used to indicate at least one tracking area code (TAC) and / or at least one cell identifier that the first device is permitted or authorized to broadcast.

18. The device according to claim 17, characterized in that, The first information includes at least one of the following information: at least one TAC that the first device is permitted or authorized to broadcast, at least one cell identifier that the first device is permitted or authorized to broadcast, a first network slice selection assistance information (S-NSSAI), a first data network name (DNN), and geographical location information; where the geographical location information includes at least one of the following: the TAC of the access network device to which the first device is connected, the cell identifier of the access network device to which the first device is connected, and the longitude and latitude coordinates of the location where the first device is located.

19. The device according to claim 17 or 18, characterized in that, The first information is carried in a registration acceptance message corresponding to a registration request message, where the registration request message is sent by the first device and is used to request to initiate a registration process.

20. The device according to claim 17 or 18, characterized in that, The first information is carried in a downlink non-access stratum (NAS) transport message, and the downlink NAS transport message is used to indicate the policy data of the first device.

21. The device according to claim 17 or 18, characterized in that, The first information is carried in a PDU session establishment acceptance message, and the PDU session establishment acceptance message is used to indicate that the first core network element accepts the PDU session establishment request of the first device.

22. The device according to claim 21, characterized in that, The first information is carried in a protocol configuration option (PCO); or, the first information is carried in a downlink NAS transport message.

23. The device according to any one of claims 17 to 22, characterized in that, The apparatus further includes: A sending module, configured to broadcast the at least one TAC and / or the at least one cell identifier.

24. An information indicating device, characterized in that, The apparatus includes: A sending module, configured to send first information to a first device, where the first information is used to indicate at least one tracking area code (TAC) and / or at least one cell identifier that the first device is permitted or authorized to broadcast.

25. The device according to claim 24, characterized in that, The first information includes at least one of the following: at least one TAC that the first device is permitted or authorized to broadcast, at least one cell identifier that the first device is permitted or authorized to broadcast, first slice network selection assistance information (S-NSSAI), first data network name (DNN), geographical location information; where the geographical location information includes at least one of the following: the TAC of the access network device to which the first device is connected, the cell identifier of the access network device to which the first device is connected, the longitude and latitude coordinates of the location where the first device is located.

26. The device according to claim 24 or 25, characterized in that, The first information is carried in a registration acceptance message corresponding to a registration request message, where the registration request message is sent by the first device and is used to request to initiate a registration process.

27. The device according to claim 25, wherein The apparatus further includes: A receiving module, configured to receive a first message sent by a second core network element, where the first message is used to indicate policy information related to access and mobility management; the policy information related to access and mobility management includes at least one of the following: the TAC that the first device is permitted or authorized to broadcast, the cell identifier that the first device is permitted or authorized to broadcast, first S-NSSAI, first DNN.

28. The device according to claim 27, wherein The first message is an access and mobility policy control creation response message.

29. The device according to claim 24 or 25, characterized in that, The first information is carried in a downlink non-access stratum (NAS) transport message, and the downlink NAS transport message is used to indicate the policy data of the first device.

30. The device according to claim 24 or 25, characterized in that, The first information is carried in a PDU session establishment acceptance message, and the PDU session establishment acceptance message is used to indicate that the first core network element accepts the PDU session establishment request of the first device.

31. The device according to claim 30, characterized in that, The first information is carried in a protocol configuration option (PCO); or the first information is carried in a downlink NAS transport message.

32. The device according to claim 30 or 31, characterized in that, The apparatus further includes: A receiving module, configured to receive the PDU session establishment acceptance message sent by a third core network element; the PDU session establishment acceptance message includes at least one of the following: at least one TAC that the first device is permitted or authorized to broadcast, at least one cell identifier that the first device is permitted or authorized to broadcast, first S-NSSAI, first DNN, PDU session identifier, quality of service (QoS) flow identifier, QoS parameters, QoS rules.

33. A communication device, characterized in that, The communication device includes a processor and a memory, where a computer program is stored in the memory, and the processor executes the computer program to implement the method according to any one of claims 1 to 7, or to implement the method according to any one of claims 8 to 16.

34. A computer-readable storage medium, characterized in that, A computer program is stored in the storage medium, and the computer program is used to be executed by a processor to implement the method according to any one of claims 1 to 7, or to implement the method according to any one of claims 8 to 16.

35. A chip, characterized in that, The chip includes programmable logic circuits and / or program instructions, which are used to implement the method according to any one of claims 1 to 7 or the method according to any one of claims 8 to 16 when the chip runs.

36. A computer program product, characterized in that, The computer program product includes computer instructions stored in a computer-readable storage medium. The processor reads and executes the computer instructions from the computer-readable storage medium to implement the method according to any one of claims 1 to 7 or the method according to any one of claims 8 to 16.

Images